From: Olaf Hering <olaf@aepfle.de>
To: Peter Maydell <peter.maydell@linaro.org>
Cc: Paolo Bonzini <pbonzini@redhat.com>,
Michael Tokarev <mjt@tls.msk.ru>,
QEMU Developers <qemu-devel@nongnu.org>,
Stefan Hajnoczi <stefanha@redhat.com>,
Stefan Weil <sw@weilnetz.de>
Subject: Re: [Qemu-devel] [PATCH] build: preserve debug symbols with --enable-debug-info
Date: Thu, 25 Sep 2014 12:47:37 +0200 [thread overview]
Message-ID: <20140925104737.GA14304@aepfle.de> (raw)
In-Reply-To: <CAFEAcA-E2qX7ZT3i6_q8qjaofLuBL3Rdz9OX8nRb-vdgNJbGrg@mail.gmail.com>
On Thu, Sep 25, Peter Maydell wrote:
> On 25 September 2014 09:06, Olaf Hering <olaf@aepfle.de> wrote:
> > During code review for xen I noticed that --enable-debug-info would
> > still strip the binaries because strip_opt= defaults to yes.
> > If --enable-debug-info is passed to configure it has to be assumed
> > that not only the compiled binaries have debugsymbols, also the
> > installed binaries should keep the symbols. The requirement to pass
> > also --disable-strip looks odd.
>
> I think defaulting to build with debug but strip on install
> makes sense. It follows for example how Debian recommend
> building things:
> https://www.debian.org/doc/debian-policy/ch-files.html
> and means that your installed binaries don't have the
> extraneous debug info but you can keep the build tree
> to make sense of backtraces etc later.
make install DESTIDIR=$RPM_BUILD_ROOT will also remove debug symbols,
even if the rpmbuild helper scripts would be able to extract them into a
separate -debuginfo package.
So will --disable-strip remain for ever? Can I depend on that?
Olaf
next prev parent reply other threads:[~2014-09-25 10:47 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-09-25 8:06 [Qemu-devel] [PATCH] build: preserve debug symbols with --enable-debug-info Olaf Hering
2014-09-25 10:36 ` Peter Maydell
2014-09-25 10:47 ` Olaf Hering [this message]
2014-09-25 10:51 ` Peter Maydell
2014-09-25 10:49 ` Stefan Hajnoczi
2014-09-25 10:55 ` Olaf Hering
2014-09-25 11:05 ` Michael Tokarev
2014-09-25 13:51 ` Paolo Bonzini
2014-10-02 15:39 ` Stefan Hajnoczi
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=20140925104737.GA14304@aepfle.de \
--to=olaf@aepfle.de \
--cc=mjt@tls.msk.ru \
--cc=pbonzini@redhat.com \
--cc=peter.maydell@linaro.org \
--cc=qemu-devel@nongnu.org \
--cc=stefanha@redhat.com \
--cc=sw@weilnetz.de \
/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.