All of lore.kernel.org
 help / color / mirror / Atom feed
From: Pavel Roskin <proski@gnu.org>
To: The development of GRUB 2 <grub-devel@gnu.org>
Subject: Re: [PATCH] Preserve build IDs
Date: Tue, 15 Apr 2008 15:04:26 -0400	[thread overview]
Message-ID: <1208286266.23118.6.camel@dv> (raw)
In-Reply-To: <20080415133501.GF21548@thorin>


On Tue, 2008-04-15 at 15:35 +0200, Robert Millan wrote:
> On Tue, Apr 15, 2008 at 12:41:50AM +0200, Lubomir Kundrak wrote:
> > This will make Fedora packagers have good sleep. I think we discussed
> > this already on the list. Rationale behind disabling build-ids
> > completely was that it caused images to grow a lot. Correct solution is
> > to disable it from images only and let it exists in elf files for
> > debugging purposes.
> > 
> > 2008-04-15  Lubomir Kundrak  <lkundrak@redhat.com>
> > 
> > 	* aclocal.m4 (grub_PROG_OBJCOPY_ABSOLUTE): take only .text
> > 	section into account, newer toolchains generate unique build ids
> > 	* configure.ac: remove the test for --build-id=none acceptance,
> > 	we want build ids to bre preserved
> > 	* genmk.rb: add -R .note.gnu.build-id to objcopy, so build id
> > 	far from other sections don't cause the raw binary images grow
> > 	size
> 
> Looks good to me.  Pavel will probably know better though.

Looks good to me too.  There is a bug in objcopy if it's used without
stripping the build ID.  But if we are stripping it, there should be no
problem with it.

-- 
Regards,
Pavel Roskin



  reply	other threads:[~2008-04-15 19:04 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-04-14 22:41 [PATCH] Preserve build IDs Lubomir Kundrak
2008-04-15 13:35 ` Robert Millan
2008-04-15 19:04   ` Pavel Roskin [this message]
2008-04-17 11:51     ` Lubomir Kundrak
2008-04-17 19:14       ` Pavel Roskin
2008-04-17 14:14     ` 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=1208286266.23118.6.camel@dv \
    --to=proski@gnu.org \
    --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.