From: Lubomir Kundrak <lkundrak@redhat.com>
To: The development of GRUB 2 <grub-devel@gnu.org>
Subject: Re: [PATCH] Fix for linker build ID in Fedora 8
Date: Mon, 26 Nov 2007 11:28:44 +0100 [thread overview]
Message-ID: <1196072924.26555.13.camel@localhost.localdomain> (raw)
In-Reply-To: <1196029564.26555.9.camel@localhost.localdomain>
On Sun, 2007-11-25 at 23:26 +0100, Lubomir Kundrak wrote:
> Hi,
>
> Thanks for the patch!
>
> On Fri, 2007-11-23 at 22:07 -0500, Pavel Roskin wrote:
> > Hello!
> > 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.
> I attach the patch I use. The first hunk is basically the same as yours,
> the second one is self-explanatory.
Actually, the first hunk should better look like this:
http://lists.gnu.org/archive/html/grub-devel/2007-11/msg00187.html
--
Lubomir Kundrak (Red Hat Security Response Team)
next prev parent reply other threads:[~2007-11-26 10:28 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-11-24 3:07 [PATCH] Fix for linker build ID in Fedora 8 Pavel Roskin
2007-11-25 22:26 ` Lubomir Kundrak
2007-11-26 10:28 ` Lubomir Kundrak [this message]
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
-- strict thread matches above, loose matches on Subject: below --
2007-11-14 7:39 Pavel Roskin
2007-11-18 6:50 ` Robert Millan
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=1196072924.26555.13.camel@localhost.localdomain \
--to=lkundrak@redhat.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.