From: Richard Purdie <richard.purdie@linuxfoundation.org>
To: Khem Raj <raj.khem@gmail.com>
Cc: openembedded-core@lists.openembedded.org
Subject: Re: [PATCH 0/4] base/bbclass: use target path to replace build ones in debugging info
Date: Wed, 27 Jan 2016 22:13:18 +0000 [thread overview]
Message-ID: <1453932798.10340.11.camel@linuxfoundation.org> (raw)
In-Reply-To: <F43BB7C8-5982-46B5-90B1-D11128DEA616@gmail.com>
On Wed, 2016-01-27 at 14:34 -0500, Khem Raj wrote:
> > On Jan 27, 2016, at 5:16 AM, Richard Purdie <
> > richard.purdie@linuxfoundation.org> wrote:
> >
> > I like the idea of this a lot, I think it makes sense however why
> > not
> > just:
> >
> > diff --git a/meta/conf/bitbake.conf b/meta/conf/bitbake.conf
> > index e80ee18..284f7fb 100644
> > --- a/meta/conf/bitbake.conf
> > +++ b/meta/conf/bitbake.conf
> > @@ -546,7 +546,14 @@ EXTRA_OEMAKE_prepend_task-install =
> > "${PARALLEL_MAKEINST} "
> > ##################################################################
> > # Optimization flags.
> > ##################################################################
> > -DEBUG_FLAGS ?= "-g -feliminate-unused-debug-types"
> > +DEBUG_FLAGS ?= "-g \
> > + -feliminate-unused-debug-types \
> > + -fdebug-prefix-map=${B}=/usr/src/${BPN} \
> > + -fdebug-prefix-map=${S}=/usr/src/${BPN}
> > + -gno-record-gcc-switches \
>
> can we leave the switches in ?
Is there a way we can do some path substitutions on the switches?
I think part of the desire here is that the end resulting binaries
shouldn't depend upon the path in which they were built and leaving
these in is causing a problem there.
Cheers,
Richard
> > + -fdebug-prefix-map=${STAGING_DIR_NATIVE}= \
> > + -fdebug-prefix-map=${STAGING_DIR_HOST}= \
> > +"
> > # Disabled until the option works properly -feliminate-dwarf2-dups
> > FULL_OPTIMIZATION = "-O2 -pipe ${DEBUG_FLAGS}"
> > DEBUG_OPTIMIZATION = "-O -fno-omit-frame-pointer ${DEBUG_FLAGS}
> > -pipe"
> >
> > ?
> >
> > Cheers,
> >
> > Richard
> > --
> > _______________________________________________
> > Openembedded-core mailing list
> > Openembedded-core@lists.openembedded.org
> > http://lists.openembedded.org/mailman/listinfo/openembedded-core
>
next prev parent reply other threads:[~2016-01-27 22:13 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-01-27 8:45 [PATCH 0/4] base/bbclass: use target path to replace build ones in debugging info Hongxu Jia
2016-01-27 8:45 ` [PATCH 1/4] base/bbclass: use target path as compile dir " Hongxu Jia
2016-01-27 8:45 ` [PATCH 2/4] base/bbclass: disallow appending the compile options " Hongxu Jia
2016-01-27 19:20 ` Khem Raj
2016-01-27 8:45 ` [PATCH 3/4] base/bbclass: use target path as include dir " Hongxu Jia
2016-01-27 8:45 ` [PATCH 4/4] base/bbclass: fix missing to replace build " Hongxu Jia
2016-01-27 10:16 ` [PATCH 0/4] base/bbclass: use target path to replace build ones " Richard Purdie
2016-01-27 19:34 ` Khem Raj
2016-01-27 22:13 ` Richard Purdie [this message]
2016-01-28 2:58 ` Hongxu Jia
2016-01-28 17:04 ` Richard Purdie
2016-01-29 3:39 ` Hongxu Jia
2016-01-29 6:40 ` Richard Purdie
2016-01-29 6:58 ` Hongxu Jia
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=1453932798.10340.11.camel@linuxfoundation.org \
--to=richard.purdie@linuxfoundation.org \
--cc=openembedded-core@lists.openembedded.org \
--cc=raj.khem@gmail.com \
/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.