From: James Tomaschke <james@orcasystems.com>
To: Fans of the OS Plan 9 from Bell Labs <9fans@9fans.net>
Subject: Re: [9fans] More on the GO toolchain
Date: Fri, 8 Jan 2010 13:09:02 -0800 [thread overview]
Message-ID: <4B479EEE.5030607@orcasystems.com> (raw)
In-Reply-To: <536ceb1c6c20a0fe16e9c2c3feab15a2@proxima.alt.za>
lucio@proxima.alt.za wrote:
> One of the issue I need to fix, further, is that the 386 linker (at
> least) demands to access the runtime module (runtime.a - I am not yet
> ready to build this library) and I wonder if there are any suggestions
> here on how best to eliminate this mandatory requirements without
> jeopardising compatibility between the GO toolchain and its ability to
> "replace" the native Plan 9 toolchain - which is my primary objective
> at this point.
Perhaps the go 8l is not honoring the "-l " option? I just tried to
create a mbr from assembly and it reported the same runtime
requirements. A diff between the various sources might be useful since
they are similar.
next prev parent reply other threads:[~2010-01-08 21:09 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-01-08 4:17 lucio
2010-01-08 21:09 ` James Tomaschke [this message]
2010-01-08 21:49 ` erik quanstrom
2010-01-09 0:10 ` James Tomaschke
2010-01-09 3:55 ` lucio
2010-01-09 3:59 ` erik quanstrom
2010-01-09 3:42 ` lucio
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=4B479EEE.5030607@orcasystems.com \
--to=james@orcasystems.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).