From: Bryan Hundven <bryanhundven@gmail.com>
To: Thomas De Schampheleire <patrickdepinguin@gmail.com>
Cc: crossgcc maillist <crossgcc@sourceware.org>,
"Yann E. MORIN" <yann.morin.1998@free.fr>
Subject: Re: Building toolchain libraries with debugging symbols
Date: Thu, 03 Mar 2016 23:26:00 -0000 [thread overview]
Message-ID: <D878249D-EDDB-4BA1-AF66-1E64DF600D00@gmail.com> (raw)
In-Reply-To: <CAAXf6LUB-qzOfKaQg-cG4_Ls-6fvU3HXAKZ5JWRGc+f5o61mXw@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 1067 bytes --]
> On Mar 3, 2016, at 11:26 AM, Thomas De Schampheleire <patrickdepinguin@gmail.com> wrote:
>
> On Mon, Feb 8, 2016 at 10:40 AM, Thomas De Schampheleire
> <patrickdepinguin@gmail.com> wrote:
>> Hello,
>>
>> What is the 'correct' way to make sure that the libraries of the
>> toolchain (most importantly libc but possibly others) contain
>> debugging symbols, so that debugging an application linked to these
>> libraries works as expected?
>>
>> Toolchains provided by external vendors are configured as such, but it
>> seems that crosstool-ng by default does not.
>>
>> We did not find a global setting for this. As a workaround we applied
>> the following:
>>
>> CT_LIBC_GLIBC_EXTRA_CFLAGS="-g"
>>
>> but it is unclear if this is the 'correct' way or not.
>>
>
> ping?
Thomas,
Sorry for the delay, I just saw this email. I’m not sure why I didn’t see the earlier email.
I need to do a little research, but I’ve CC’d Yann E. Morin in case he knows off hand.
If not, I’ll have a response soon.
Cheers,
-Bryan
[-- Attachment #2: Message signed with OpenPGP using GPGMail --]
[-- Type: application/pgp-signature, Size: 496 bytes --]
next prev parent reply other threads:[~2016-03-03 23:26 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-02-08 9:41 Thomas De Schampheleire
2016-03-03 19:26 ` Thomas De Schampheleire
2016-03-03 23:26 ` Bryan Hundven [this message]
2016-03-04 1:03 ` Bryan Hundven
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=D878249D-EDDB-4BA1-AF66-1E64DF600D00@gmail.com \
--to=bryanhundven@gmail.com \
--cc=crossgcc@sourceware.org \
--cc=patrickdepinguin@gmail.com \
--cc=yann.morin.1998@free.fr \
/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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).