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 07:58:37 -0700 [thread overview]
Message-ID: <20090717145837.GA567@gmail.com> (raw)
In-Reply-To: <1247829612-9310-1-git-send-email-khimov@altell.ru>
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. So may be
there should be options like DEBUG_STRIP, STRIP and NO_STRIP and only one of
which could be used.
Thx
-Khem
next prev parent reply other threads:[~2009-07-17 15:12 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 [this message]
2009-07-17 17:50 ` Roman I Khimov
2009-07-17 18:49 ` Khem Raj
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=20090717145837.GA567@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.