From mboxrd@z Thu Jan 1 00:00:00 1970 Message-ID: <18b46cd6fb7df6e8c6a996369fda6a09@proxima.alt.za> To: 9fans@9fans.net From: Lucio De Re Date: Mon, 1 Aug 2011 21:56:28 +0200 In-Reply-To: MIME-Version: 1.0 Content-Type: multipart/mixed; boundary="upas-nsagrquupqjisqjoiltkoqzyke" Subject: Re: [9fans] Status of port of Go to Plan 9 Topicbox-Message-UUID: 09b47600-ead7-11e9-9d60-3106f5b1d025 This is a multi-part message in MIME format. --upas-nsagrquupqjisqjoiltkoqzyke Content-Disposition: inline Content-Type: text/plain; charset="US-ASCII" Content-Transfer-Encoding: 7bit There's a recipe in src/cmd/mkone (../mkone)? I hope I haven't overlooked any of the mkfiles, it's been a bit of a swamp for a while. Have a look at each mkfile's first few lines, you can change ROOT there or mk ROOT=$home/go but I'm not always propagating (ever?) MKFLAGS. Let me know, I'll be back in the (local) morning. Off the cuff, I don't think you're doing anything wrong, it looks like a context issue I have not taken into consideration. But I can't put my finger on it. ++L --upas-nsagrquupqjisqjoiltkoqzyke Content-Type: message/rfc822 Content-Disposition: inline Return-Path: <9fans-bounces@9fans.net> Received: from mail.9fans.net (mail.9fans.net [67.207.142.3]) by mumble.proxima.alt.za (8.14.3/8.14.3) with ESMTP id p71I6mIm006518 (version=TLSv1/SSLv3 cipher=AES256-SHA bits=256 verify=NO) for ; Mon, 1 Aug 2011 20:06:50 +0200 (SAST) Received: from localhost ([127.0.0.1] helo=[67.207.142.3]) by mail.9fans.net with esmtp (Exim 4.71) (envelope-from <9fans-bounces@9fans.net>) id 1QnxL2-0000lc-EX; Mon, 01 Aug 2011 18:35:40 +0000 Received: from mail-pz0-f43.google.com ([209.85.210.43]) by mail.9fans.net with esmtp (Exim 4.71) (envelope-from ) id 1QnxL1-0000lV-D6 for 9fans@9fans.net; Mon, 01 Aug 2011 18:35:39 +0000 Received: by pzk1 with SMTP id 1so11775469pzk.16 for <9fans@9fans.net>; Mon, 01 Aug 2011 11:06:10 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :content-type:content-transfer-encoding; bh=nnNYXNUq2nxzqjgipPHVqQAyKoZEr65TcgE8bvL190k=; b=PcOcnSBUq0ycD6UbVcStPV2UES+UN0a8BbAOk2Kq2o6agshgzaxwA8vYVBCDJvWVKb 1gLgq3b465g2eZWaQjKCCpN7aOXNLdx1gwjmd1qF1+UPbwU7VBsK/F8JJBRQEHKrbwV6 ItB3jTT3F+G2DOgdLC2CAEqqBUOUT2mmfu5JQ= MIME-Version: 1.0 Received: by 10.68.19.3 with SMTP id a3mr7018801pbe.331.1312221951265; Mon, 01 Aug 2011 11:05:51 -0700 (PDT) Received: by 10.68.48.234 with HTTP; Mon, 1 Aug 2011 11:05:51 -0700 (PDT) In-Reply-To: <0f2b11fb7c8a3e66e8e3d71242be7037@proxima.alt.za> References: <0f2b11fb7c8a3e66e8e3d71242be7037@proxima.alt.za> Date: Mon, 1 Aug 2011 11:05:51 -0700 Message-ID: From: Skip Tavakkolian To: lucio@proxima.alt.za, Fans of the OS Plan 9 from Bell Labs <9fans@9fans.net> Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable Subject: Re: [9fans] Status of port of Go to Plan 9 X-BeenThere: 9fans@9fans.net X-Mailman-Version: 2.1.13 Precedence: list Reply-To: Fans of the OS Plan 9 from Bell Labs <9fans@9fans.net> List-Id: Fans of the OS Plan 9 from Bell Labs <9fans.9fans.net> List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Sender: 9fans-bounces@9fans.net Errors-To: 9fans-bounces@9fans.net X-Greylist: Sender passed SPF test, not delayed by milter-greylist-4.2.6 (mumble.proxima.alt.za [192.96.32.140]); Mon, 01 Aug 2011 20:06:50 +0200 (SAST) X-Filter: OK <9fans-bounces@9fans.net> Thanks! what's a good recipe for making goose? :) bigtop% mk # bind -b /go/$objtype/include /$objtype/include for(i in 8l 8a cc 8c gc 8g) @{ cd $i echo mk in $i mk $MKFLAGS } mk in 8l 8c -I/go/include -I/go/386/include -FTVw asm.c 8c -I/go/include -I/go/386/include -FTVw ../ld/data.c mk: no recipe to make 'goos.8' in directory /go/src/cmd/8l mk: # bind -b ... : exit status=3Drc 308216: rc 308218: mk 308220: error fyi, instead of /go, i've copied it to $home/go and: aux/stub -d /go bind -c $home/go /go -Skip On Mon, Aug 1, 2011 at 2:04 AM, Lucio De Re wrote: > On /n/sources/contrib/lucio/go there is a fresh version of my efforts. > It is a bit ahead of my submissions to the Go Authors and could > benefit from inspection from the Plan 9 perspective. =A0Also, this > inevitably means that there will be changes required by the code > reviewers. > > At this point, it ought to be possible to build the assemblers, C and > Go compilers and linkers for all three architectures (386, amd64 and > arm) for local use on a Plan 9/386 platform. =A0The only build option I > have tested is the default in src/cmd/mkfile: > > =A0 =A0 =A0 =A0% 9fs sources > =A0 =A0 =A0 =A0% disk/mkfs -a -s /n/sources/contrib/lucio/go /n/sources/c= ontrib/lucio/go/devproto | disk/mkext -v -d /go > =A0 =A0 =A0 =A0% cd /go/src/cmd > =A0 =A0 =A0 =A0% mk > > Actual installation should be left until the above succeeds. =A0Where I > am, multiple downloads are expensive and time consuming, so I can't > test this repetitively, please let me know if the above procedure > needs adjusting: > > =A0 =A0 =A0 =A0% mk install > > This ought to copy the 8a, 8c, 8g and 8l executables (not in that > sequence) to /go/386/bin. > > I have arranged for the amd64 and arm versions to work as well. > Change to the appropriate directories and the mkfile will provide the > necessary instructions, including installing to /go/386/bin. > > Nothing above is properly tested. =A0Until I get the runtime properly > constructed, I'm not sure how best to go about testing, so any > contribution or suggestions here is welcome. > > ++L > > > --upas-nsagrquupqjisqjoiltkoqzyke--