From: Tristan Gingold <gingold@adacore.com>
To: Mike Frysinger <vapier@gentoo.org>, Alan Modra <amodra@gmail.com>
Cc: binutils@sourceware.org
Subject: Re: Release 2.21.1 ?
Date: Wed, 16 Mar 2011 08:49:00 -0000 [thread overview]
Message-ID: <7ADF65FE-7C5F-4DE2-829E-8A82DA51502C@adacore.com> (raw)
In-Reply-To: <201103160003.07690.vapier@gentoo.org>
On Mar 16, 2011, at 5:03 AM, Mike Frysinger wrote:
> On Tuesday, March 15, 2011 04:21:37 Tristan Gingold wrote:
>> [ I think that not all patches have been back-ported, so do not hesitate to
>> ping me ]
>
> my understanding is that binutils-2.21 does not build a relocatable x86
> kernel, but this commit from master fixes it:
> http://sourceware.org/git/?p=binutils.git;a=commit;h=5daebc6a6606a30e60716f5bdee3d2018b560e8e
>
> so that'd be a good one to backport if a new release is done
This patch is supposed to be in 2.21:
2010-12-20 Alan Modra <amodra@gmail.com>
PR ld/12327
* ld.texinfo (Expression Section): Describe treatment of numbers
and absolute symbols.
* ldemul.c (after_open_default): Look up __ld_compatibility.
* ldexp.c (fold_name): Convert absolute symbols to numbers when
inside output section definitions, or when __ld_compatibility >= 221.
(exp_fold_tree_1): Convert numbers to absolute when not in output
section definition and __ld_compatibility < 221. Don't always
convert values outside an output section definition to absolute.
* ldexp.h (uses_defined): Comment.
* ldlang.c (ld_compatibility): New variable.
* ldlang.h (ld_compatibility): Declare.
* emultempl/aix.em, * emultempl/armcoff.em, * emultempl/beos.em,
* emultempl/elf32.em, * emultempl/genelf.em, * emultempl/lnk960.em,
* emultempl/m68kcoff.em, * emultempl/mmo.em, * emultempl/pe.em,
* emultempl/pep.em, * emultempl/sunos.em, * emultempl/z80.em: Call
after_open_default from after_open function.
But it looks like it was only partially backported (chunks still apply to ldlang.[ch] and ldemul.c)
Alan ?
Tristan.
next prev parent reply other threads:[~2011-03-16 8:49 UTC|newest]
Thread overview: 30+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-03-15 8:21 Tristan Gingold
2011-03-15 13:24 ` Ian Lance Taylor
2011-03-15 17:28 ` Jakub Jelinek
2011-03-15 17:30 ` Matthias Klose
2011-03-15 17:51 ` Dave Korn
2011-03-16 7:52 ` Tristan Gingold
2011-03-16 4:03 ` Mike Frysinger
2011-03-16 8:49 ` Tristan Gingold [this message]
2011-03-16 12:19 ` Alan Modra
2011-03-17 12:21 ` Alan Modra
2011-03-17 12:39 ` Tristan Gingold
2011-03-20 21:41 ` Mike Frysinger
2011-03-23 16:00 ` Tristan Gingold
2011-05-16 7:47 ` Andreas Krebbel
2011-05-16 7:53 ` Tristan Gingold
2011-05-17 17:31 ` Andreas Krebbel
2011-05-18 7:03 ` Tristan Gingold
2011-05-16 10:05 ` Marek Polacek
2011-05-26 7:54 ` Release 2.21.1 [again] Tristan Gingold
2011-05-29 7:57 ` Alan Modra
2011-05-29 17:18 ` Alan Modra
2011-05-29 17:26 ` Alan Modra
2011-05-29 20:55 ` Alan Modra
2011-03-16 6:44 Release 2.21.1 ? Sedat Dilek
2011-03-16 8:50 ` Tristan Gingold
2011-03-16 9:37 ` Sedat Dilek
2011-03-16 15:34 ` Sedat Dilek
2011-03-16 12:17 ` Alan Modra
2011-03-16 12:44 ` H.J. Lu
2011-03-16 12:47 ` Tristan Gingold
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=7ADF65FE-7C5F-4DE2-829E-8A82DA51502C@adacore.com \
--to=gingold@adacore.com \
--cc=amodra@gmail.com \
--cc=binutils@sourceware.org \
--cc=vapier@gentoo.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 read-only IMAP folder(s) and NNTP newsgroup(s).