From: Keith Owens <kaos@ocs.com.au>
To: Richard Henderson <rth@twiddle.net>
Cc: linux-kernel@vger.kernel.org
Subject: Re: [RFC] /proc/ksyms change for IA64
Date: Tue, 21 Aug 2001 16:53:20 +1000 [thread overview]
Message-ID: <31011.998376800@kao2.melbourne.sgi.com> (raw)
In-Reply-To: Your message of "Sat, 18 Aug 2001 18:27:56 MST." <20010818182756.A29533@twiddle.net>
On Sat, 18 Aug 2001 18:27:56 -0700,
Richard Henderson <rth@twiddle.net> wrote:
>On Thu, Aug 02, 2001 at 01:22:40PM +1000, Keith Owens wrote:
>> Using BFD is the only way I can handle all
>> the relocation types, especially in cross compile mode.
>
>What the hell? You've got everything you need right there in
>the obj subdirectory. Please don't bring libbfd back to life
>in modutils.
Cross compile mode. Nothing in modutils works unless it is running on
the machine it was compiled for. As more modutil functions get pushed
back into kbuild time, this is getting to be a problem. I could do all
my own code for endianess and size differences between host and target,
but why bother when bfd already does it for me?
next prev parent reply other threads:[~2001-08-21 6:53 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 [this message]
2001-08-21 17:47 ` Richard Henderson
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=31011.998376800@kao2.melbourne.sgi.com \
--to=kaos@ocs.com.au \
--cc=linux-kernel@vger.kernel.org \
--cc=rth@twiddle.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).