From: Phil Blundell <pb@reciva.com>
To: openembedded-devel@lists.openembedded.org
Subject: Re: Revert "package bbclass: strip static libs as well"
Date: Fri, 23 Oct 2009 11:24:09 +0100 [thread overview]
Message-ID: <1256293449.4529.133.camel@mill.internal.reciva.com> (raw)
In-Reply-To: <200910231154.22284.holger+oe@freyther.de>
On Fri, 2009-10-23 at 11:54 +0200, Holger Hans Peter Freyther wrote:
> On Friday 23 October 2009 11:46:22 Koen Kooi wrote:
>
> > > and I would prefer to have debug symbols in there. you can always strip
> > > them out of the final binary but you can not add them when they are gone.
> >
> > Installing foo-dbg doesn't work?
>
> It will not. At least from my understanding of an .a archive. You will need to
> get the symbols into the binary when statically linking, this will not happen
> when they are in a .debug/liba.a.
>
> Does this sound correct?
Yes, that is correct. In theory it would be possible to splice the
debug data back into the binary, or to teach gdb how to read debug
symbols out of the individual .debug records for the archive components,
or indeed to teach g(o)ld to pull in debug data in the way that you
suggest during final link of a binary, but I don't think the existing
tools can do any of those things.
p.
next prev parent reply other threads:[~2009-10-23 10:25 UTC|newest]
Thread overview: 44+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-10-23 3:04 Revert "package bbclass: strip static libs as well" Holger Hans Peter Freyther
2009-10-23 7:23 ` Koen Kooi
2009-10-23 7:30 ` Holger Hans Peter Freyther
2009-10-23 7:58 ` Koen Kooi
2009-10-23 8:23 ` Holger Hans Peter Freyther
2009-10-23 8:36 ` Phil Blundell
2009-10-23 9:14 ` Koen Kooi
2009-10-23 9:33 ` Holger Hans Peter Freyther
2009-10-23 9:46 ` Koen Kooi
2009-10-23 9:54 ` Holger Hans Peter Freyther
2009-10-23 10:03 ` Koen Kooi
2009-10-23 10:24 ` Phil Blundell [this message]
2009-10-23 11:07 ` Stanislav Brabec
2009-10-23 11:34 ` Holger Hans Peter Freyther
2009-10-23 22:31 ` Stanislav Brabec
2009-10-24 0:29 ` Khem Raj
2009-10-24 8:48 ` Koen Kooi
2009-10-24 13:27 ` Stanislav Brabec
2009-10-24 14:13 ` Stanislav Brabec
2009-10-24 14:33 ` Phil Blundell
2009-10-24 14:57 ` Koen Kooi
2009-10-24 14:06 ` Phil Blundell
2009-10-24 15:18 ` Koen Kooi
2009-10-24 15:39 ` Stanislav Brabec
2009-10-24 18:45 ` Phil Blundell
2009-10-24 19:33 ` Stanislav Brabec
2009-10-23 12:11 ` Leon Woestenberg
2009-10-23 12:12 ` Phil Blundell
2009-10-23 12:28 ` Koen Kooi
2009-10-23 12:37 ` Phil Blundell
2009-10-23 12:42 ` Phil Blundell
2009-10-23 12:56 ` Koen Kooi
2009-10-24 2:32 ` Holger Hans Peter Freyther
2009-10-24 3:42 ` Denys Dmytriyenko
2009-10-24 8:40 ` Koen Kooi
2009-10-23 18:21 ` Denys Dmytriyenko
2009-10-23 18:36 ` Phil Blundell
2009-10-23 19:53 ` Khem Raj
2009-10-23 18:26 ` Denys Dmytriyenko
2009-10-27 9:38 ` Koen Kooi
2009-10-27 10:21 ` Phil Blundell
2009-10-27 10:29 ` Koen Kooi
2009-10-27 10:50 ` Holger Hans Peter Freyther
2009-10-27 11:24 ` Koen Kooi
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=1256293449.4529.133.camel@mill.internal.reciva.com \
--to=pb@reciva.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.