From: "David S. Miller" <davem@redhat.com>
To: torvalds@transmeta.com
Cc: alan@lxorguk.ukuu.org.uk, viro@math.psu.edu,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH] Re: 2.5.7-pre2 -- kernel.o(.data+0x300): undefined reference
Date: Sun, 17 Mar 2002 19:20:01 -0800 (PST) [thread overview]
Message-ID: <20020317.192001.103236436.davem@redhat.com> (raw)
In-Reply-To: <Pine.LNX.4.33.0203161011150.31850-100000@penguin.transmeta.com>
In-Reply-To: <E16mI91-0006mI-00@the-village.bc.nu> <Pine.LNX.4.33.0203161011150.31850-100000@penguin.transmeta.com>
From: Linus Torvalds <torvalds@transmeta.com>
Date: Sat, 16 Mar 2002 10:15:33 -0800 (PST)
On Sat, 16 Mar 2002, Alan Cox wrote:
> This is what Linus threw out before - when David wanted to use it
> to remove all the intermodule crap.
>
> It doesn't work with some architecture binutils
How true is that these days, though?
It is still true, you will break the sparc64 link if you put that
stuff in again. It isn't COFF or a.out, it is elf but there are
bugs in the tools. And these are the only tools I happen to trust
for getting reliable kernels built.
next prev parent reply other threads:[~2002-03-18 3:23 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-03-16 8:02 2.5.7-pre2 -- kernel.o(.data+0x300): undefined reference to `sys_nfsservctl' Miles Lane
2002-03-16 8:53 ` Alexander Viro
2002-03-16 10:16 ` [PATCH] " Alexander Viro
2002-03-16 17:39 ` [PATCH] Re: 2.5.7-pre2 -- kernel.o(.data+0x300): undefined reference Alan Cox
2002-03-16 17:39 ` Alexander Viro
2002-03-16 18:01 ` [PATCH] Re: 2.5.7-pre2 -- kernel.o(.data+0x300): undefined Alan Cox
2002-03-16 18:15 ` [PATCH] Re: 2.5.7-pre2 -- kernel.o(.data+0x300): undefined reference Linus Torvalds
2002-03-18 3:20 ` David S. Miller [this message]
2002-03-16 19:18 ` Daniel Jacobowitz
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=20020317.192001.103236436.davem@redhat.com \
--to=davem@redhat.com \
--cc=alan@lxorguk.ukuu.org.uk \
--cc=linux-kernel@vger.kernel.org \
--cc=torvalds@transmeta.com \
--cc=viro@math.psu.edu \
/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