All of lore.kernel.org
 help / color / mirror / Atom feed
From: Khem Raj <raj.khem@gmail.com>
To: openembedded-devel@lists.openembedded.org
Subject: Re: [PATCH] package.bbclass: introduce KEEP_GNU_DEBUGLINK
Date: Fri, 17 Jul 2009 11:49:48 -0700	[thread overview]
Message-ID: <20090717184948.GA8252@gmail.com> (raw)
In-Reply-To: <200907172150.28360.khimov@altell.ru>

On (17/07/09 21:50), Roman I Khimov wrote:
> On Пятница 17 июля 2009 18:58:37 Khem Raj wrote:
> > On (17/07/09 15:20), Roman I Khimov wrote:
> > > Currently we're keeping .gnu_debuglink section in files after stripping
> > > them. It makes binaries from successive builds a bit different, which is
> > > not good in situations where you want them to be exactly the same
> > > (identical checksums).
> > >
> > > So, introducing KEEP_GNU_DEBUGLINK which can be set to zero to disable
> > > this behavior and get identical result on successive builds for most of
> > > the packages.
> >
> > you lose debugging these binaries if you remove this section. 
> 
> Yep.
> 
> > So may be
> > there should be options like DEBUG_STRIP, STRIP and NO_STRIP and only one
> > of which could be used.
> 
> As of now, we have INHIBIT_PACKAGE_STRIP that switches stripping, but it has 
> strong on/off semantics, so I don't think we can change that. We can replace 
> it with some common PACKAGE_STRIP setting that would work like this:
> 
> # No stripping
> PACKAGE_STRIP=no
> # Strip but leave .gnu_debuglink for debugging
> PACKAGE_STRIP=debug
> # Strip everything
> PACKAGE_STRIP=full
> 
> But that's more intrusive and will force distro and local config updates. I 
> can do it if everyone is OK with such change.

go for it

> 
> And, BTW, we also have DEBUG_BUILD setting, although that just switches 
> compile flags from what I see.
> 
> _______________________________________________
> Openembedded-devel mailing list
> Openembedded-devel@lists.openembedded.org
> http://lists.linuxtogo.org/cgi-bin/mailman/listinfo/openembedded-devel



      reply	other threads:[~2009-07-17 19:03 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-07-17 11:20 [PATCH] package.bbclass: introduce KEEP_GNU_DEBUGLINK Roman I Khimov
2009-07-17 12:22 ` Andrea Adami
2009-07-17 14:58 ` Khem Raj
2009-07-17 17:50   ` Roman I Khimov
2009-07-17 18:49     ` Khem Raj [this message]

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=20090717184948.GA8252@gmail.com \
    --to=raj.khem@gmail.com \
    --cc=openembedded-devel@lists.openembedded.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.