From: erik quanstrom <quanstro@quanstro.net>
To: lucio@proxima.alt.za, 9fans@9fans.net
Subject: Re: [9fans] Format for relocatable objects
Date: Tue, 6 Jan 2009 15:09:09 -0500 [thread overview]
Message-ID: <2fc401599e85863b21a812d333614fd4@quanstro.net> (raw)
In-Reply-To: <6b0f1fed7f15c8b2e72ad8370f87c09f@proxima.alt.za>
> It would be a shame (but no disaster) if Binutil's "nm" and other
> tools could not at least display native Plan 9 intermediate files. I
> need to know or decide how far to take this exercise.
why would that be advantagous on plan 9? if you teach
gcc to output, e.g., 8.out, then what is gained by having
gnu binutils version of nm?
- erik
next prev parent reply other threads:[~2009-01-06 20:09 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <6b1edbf6593b4f3ad0b0c6211180e565@terzarima.net>
2009-01-06 20:04 ` lucio
2009-01-06 20:09 ` erik quanstrom [this message]
2009-01-06 22:47 ` Roman V. Shaposhnik
2009-01-06 22:54 ` erik quanstrom
2009-01-06 23:07 ` Roman V. Shaposhnik
2009-01-07 3:45 ` lucio
2009-01-07 3:40 ` lucio
2009-01-06 21:12 ` Charles Forsyth
2009-01-06 18:47 lucio
2009-01-06 20:11 ` 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=2fc401599e85863b21a812d333614fd4@quanstro.net \
--to=quanstro@quanstro.net \
--cc=9fans@9fans.net \
--cc=lucio@proxima.alt.za \
/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).