From: f5ibh <f5ibh@db0bm.ampr.org>
To: adam@yggdrasil.com, linux-kernel@vger.kernel.org
Subject: Re: PATCH: linux-2.4.2-pre3/arch/i386/boot/Makefile breaks with binutils-2.10.1.0.7
Date: Fri, 16 Feb 2001 10:46:44 +0100 [thread overview]
Message-ID: <200102160946.KAA08821@db0bm.ampr.org> (raw)
> The "ld" program in binutils-2.10.1.0.7 and in binutils-2.10.91.0.2 now
> requires "--oformat" instead of "-oformat".
[root@debian-f5ibh] /usr/src/kernel-sources-2.4.2 # ld -v
GNU ld version 2.9.5 (with BFD 2.9.5.0.37)
[root@debian-f5ibh] /usr/src/kernel-sources-2.4.2 # ld --help
Usage: ld [options] file...
Options:
-a KEYWORD Shared library control for HP/UX compatibility
-A ARCH, --architecture ARCH
...
--noinhibit-exec Create an output file even if errors occur
--oformat TARGET Specify target of output file
-qmagic Ignored for Linux compatibility
...
So it seems that this option appears before binutils-2.10.1.0.7 and
binutils-2.10.91.0.2
The 2.4.2i-pre3 kernel minimal requirements are :
o binutils 2.9.1.0.25 # ld -v
It is the same for 2.4.1-ac15.
For 2.2.19-pre, the requirements are :
- Binutils 2.8.1.0.23 ; ld -v
I've not 2.8.1.0.23, s I don't know what is the option used.
I've compiled 2.4.2-pre, 2.4.1-acxx and 2.2.19-prexx with the same 'ls" program
without any adverse effect...
Maybe the best would be to apply the patch to 2.2.19pre, 2.4.x and ac releases.
This would allows havind only one "ld" on the system if using more than one
kernel.
----------
Regards
Jean-Luc
next reply other threads:[~2001-02-16 9:47 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-02-16 9:46 f5ibh [this message]
-- strict thread matches above, loose matches on Subject: below --
2001-02-16 7:08 Adam J. Richter
2001-02-16 10:07 ` Alan Cox
2001-02-16 10:30 ` alterity
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=200102160946.KAA08821@db0bm.ampr.org \
--to=f5ibh@db0bm.ampr.org \
--cc=adam@yggdrasil.com \
--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
all inboxes | Powered by JetHome®