From: Pavel Zholkover <paulzhol@gmail.com>
To: Fans of the OS Plan 9 from Bell Labs <9fans@9fans.net>
Subject: Re: [9fans] plan9 go output faults on 9vx but ok on cpu
Date: Sat, 15 Jan 2011 11:58:03 +0200 [thread overview]
Message-ID: <AANLkTikyubYNPjnrqi-DwPJJKm=fJ5NQiXV+L4nwnxa_@mail.gmail.com> (raw)
In-Reply-To: <c6ada854ccd40d32eb53c6dd8ea6a46b@proxima.alt.za>
On Sat, Jan 15, 2011 at 11:30 AM, <lucio@proxima.alt.za> wrote:
> In a nutshell, I actually took a very recent release of Go and tried
> to build a Plan 9 version:
>
> cd $GOROOT/src
> GOOS=plan9 ./make.bash
>
> I was not surprised that it did not build correctly on my Ubuntu
> workstation. Fixing it did not seem a trivial task and a cursory web
> search did not reveal any encouraging help.
If you try applying http://codereview.appspot.com/3816043/ you can get
pretty far..
you need to
cd src/pkg
make clean
GOOS=plan9 make -k install
You'll get os, syscall, fmt and a bunch of other portable go libraries.
> Right now, I have a few days in which to resurrect work I did
> initially that concluded with a "working" version of the Hello World
> "C" program compiled and executed on Plan 9/386 using modifed Go
> sources to compile and build the "C" development toolchain under Plan
> 9. It is daunting how much effort I estimate I will need to do to get
> that far, specially with a view to propagate the rather extensive
> changes to the Go source release. On the positive side, I had
> invested no effort in the Go aspects of the project and I'm grateful
> to those who have added the Go features for Plan 9 to the Go release.
>
I think that you can produce a "C" hello world pretty easily if you
provide stubs for 8l (like morestack and etc.) and use GOOS=plan9 8l
-s to link you stuff together.
Pavel
next prev parent reply other threads:[~2011-01-15 9:58 UTC|newest]
Thread overview: 36+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-01-11 7:54 Skip Tavakkolian
2011-01-11 14:11 ` erik quanstrom
2011-01-11 15:06 ` Devon H. O'Dell
2011-01-11 17:03 ` Charles Forsyth
2011-01-11 17:51 ` ron minnich
2011-01-11 19:35 ` Pavel Zholkover
2011-01-11 23:58 ` Charles Forsyth
2011-01-11 16:25 ` ron minnich
2011-01-12 8:32 ` Skip Tavakkolian
2011-01-12 16:12 ` andrey mirtchovski
2011-01-12 22:03 ` ron minnich
2011-01-13 5:54 ` ron minnich
2011-01-14 17:32 ` Pavel Zholkover
2011-01-15 2:00 ` Anthony Martin
2011-01-15 9:47 ` Pavel Zholkover
2011-01-15 9:01 ` kokamoto
2011-01-15 9:19 ` Pavel Zholkover
2011-01-15 9:30 ` lucio
2011-01-15 9:58 ` Pavel Zholkover [this message]
2011-01-15 10:29 ` lucio
2011-01-15 10:40 ` lucio
2011-01-15 11:25 ` Pavel Zholkover
2011-01-16 1:51 ` kokamoto
2011-01-16 2:04 ` kokamoto
2011-01-16 6:21 ` kokamoto
2011-01-17 12:03 ` kokamoto
2011-01-17 15:20 ` [9fans] how to make hardware work? sergey.kish
2011-01-16 2:06 ` [9fans] plan9 go output faults on 9vx but ok on cpu Skip Tavakkolian
2011-01-11 17:03 ` Pavel Zholkover
2011-01-11 18:55 ` Anthony Martin
2011-01-11 19:06 ` Anthony Martin
2011-01-11 22:58 ` ron minnich
2011-01-12 22:31 ` Anthony Martin
2011-01-12 22:36 ` erik quanstrom
2011-01-12 23:28 ` Pavel Zholkover
2011-01-12 23:29 ` Charles Forsyth
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to='AANLkTikyubYNPjnrqi-DwPJJKm=fJ5NQiXV+L4nwnxa_@mail.gmail.com' \
--to=paulzhol@gmail.com \
--cc=9fans@9fans.net \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).