From: Richard Henderson <rth@twiddle.net>
To: Keith Owens <kaos@ocs.com.au>
Cc: linux-kernel@vger.kernel.org
Subject: Re: [RFC] /proc/ksyms change for IA64
Date: Tue, 21 Aug 2001 10:47:04 -0700 [thread overview]
Message-ID: <20010821104704.A6190@twiddle.net> (raw)
In-Reply-To: <20010818182756.A29533@twiddle.net> <31011.998376800@kao2.melbourne.sgi.com>
In-Reply-To: <31011.998376800@kao2.melbourne.sgi.com>; from kaos@ocs.com.au on Tue, Aug 21, 2001 at 04:53:20PM +1000
On Tue, Aug 21, 2001 at 04:53:20PM +1000, Keith Owens wrote:
> ... but why bother when bfd already does it for me?
How about bfd is a bloated monstrosity. Right now libobj is
just over 10k; you'll be looking at a _minimum_ of 150k to
pull in only the linking code from libbfd.a.
How about bfd is an unmaintainable nightmare? If you've not
spent the last couple of years working on bfd, save your
sanity and don't start.
It would take only a day or three to fix up libobj to cross
compile. If you don't want to do it, let someone else.
r~
next prev parent reply other threads:[~2001-08-21 17:47 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-08-02 3:22 [RFC] /proc/ksyms change for IA64 Keith Owens
2001-08-05 5:44 ` Rusty Russell
2001-08-05 7:16 ` Keith Owens
2001-08-05 14:02 ` Rusty Russell
2001-08-05 14:51 ` Keith Owens
2001-08-05 9:29 ` PPC? (Was: Re: [RFC] /proc/ksyms change for IA64) Kai Henningsen
2001-08-05 19:41 ` Keith Owens
2001-08-05 20:26 ` Peter A. Castro
2001-08-06 3:05 ` Brad Boyer
2001-08-06 22:43 ` Rob Barris
2001-08-07 3:47 ` Anton Blanchard
2001-08-19 1:27 ` [RFC] /proc/ksyms change for IA64 Richard Henderson
2001-08-21 6:53 ` Keith Owens
2001-08-21 17:47 ` Richard Henderson [this message]
2001-08-02 12:42 [Linux-ia64] [RFC] /proc/ksyms change for IA64 (fwd) Jack Steiner
2001-08-02 13:25 ` [RFC] /proc/ksyms change for IA64 Keith Owens
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=20010821104704.A6190@twiddle.net \
--to=rth@twiddle.net \
--cc=kaos@ocs.com.au \
--cc=linux-kernel@vger.kernel.org \
/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).