From: Robert Millan <rmh@aybabtu.com>
To: The development of GRUB 2 <grub-devel@gnu.org>
Subject: Re: [PATCH] Fix for linker build ID in Fedora 8
Date: Sun, 18 Nov 2007 07:50:51 +0100 [thread overview]
Message-ID: <20071118065051.GE20719@thorin> (raw)
In-Reply-To: <1195025942.22086.11.camel@dv>
On Wed, Nov 14, 2007 at 02:39:02AM -0500, Pavel Roskin wrote:
> Hello!
>
> [Sorry for not replying earlier. All messages from my gnu.org account
> were getting lost. Anyway, I'll need to retire that address due to
> massive spam.]
>
> Here's an alternate patch for the issue that appeared on Fedora 8. The
> linker adds a "build ID" (.not.gnu.build-id) by default. That section
> makes objcopy create output files about 128M long when asked to use
> binary format. Needless to say, they are not suitable as grub images.
> Also, the build ID section breaks the test for objcopy in the configure
> script.
>
> This patch is less intrusive than the one I posted earlier, so I hope it
> will be accepted.
>
> 2007-10-29 Pavel Roskin <proski-grub@xemaps.com>
>
> * configure.ac: Test if '--build-id=none' is supported by the
> linker. Add it to TARGET_LDFLAGS if possible. Build ID
> interferes with objcopy.
> * aclocal.m4 (grub_PROG_OBJCOPY_ABSOLUTE): Use LDFLAGS when
> linking, so that build ID doesn't break the test.
Looks fine to me. Seeing that there were no objections after a few days, I
suggest you check it in.
--
Robert Millan
<GPLv2> I know my rights; I want my phone call!
<DRM> What use is a phone call, if you are unable to speak?
(as seen on /.)
next prev parent reply other threads:[~2007-11-18 6:51 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-11-14 7:39 [PATCH] Fix for linker build ID in Fedora 8 Pavel Roskin
2007-11-18 6:50 ` Robert Millan [this message]
-- strict thread matches above, loose matches on Subject: below --
2007-11-24 3:07 Pavel Roskin
2007-11-25 22:26 ` Lubomir Kundrak
2007-11-26 10:28 ` Lubomir Kundrak
2007-11-26 12:35 ` Pavel Roskin
2007-11-26 12:54 ` Lubomir Kundrak
2007-11-26 13:06 ` Pavel Roskin
2007-12-12 15:45 ` Robert Millan
2007-12-14 4:33 ` Pavel Roskin
2007-12-14 5:45 ` Pavel Roskin
2007-12-14 6:10 ` Bean
2007-12-14 6:47 ` Pavel Roskin
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=20071118065051.GE20719@thorin \
--to=rmh@aybabtu.com \
--cc=grub-devel@gnu.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.