From: lucio@proxima.alt.za
To: 9fans@9fans.net
Subject: Re: [9fans] More on the GO toolchain
Date: Sat, 9 Jan 2010 05:42:42 +0200 [thread overview]
Message-ID: <cebd98e13923e7aef60a1e761f8a9dea@proxima.alt.za> (raw)
In-Reply-To: <4B479EEE.5030607@orcasystems.com>
> 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.
It was easy enough to turn that off, I'm not sure how to do it
selectively and at the same time retain portability across both
architectures and target purposes (Plan 9, GO and also Inferno - this
last I have not given any attention to yet).
++L
prev parent reply other threads:[~2010-01-09 3:42 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
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 [this message]
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=cebd98e13923e7aef60a1e761f8a9dea@proxima.alt.za \
--to=lucio@proxima.alt.za \
--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).