All of lore.kernel.org
 help / color / mirror / Atom feed
From: wenzong fan <wenzong.fan@windriver.com>
To: Khem Raj <raj.khem@gmail.com>
Cc: OE-core <openembedded-core@lists.openembedded.org>
Subject: Re: [PATCH] bjam-native: inhibit sysroot strip
Date: Mon, 10 Aug 2015 14:14:46 +0800	[thread overview]
Message-ID: <55C84156.8090609@windriver.com> (raw)
In-Reply-To: <4FCE2229-1F6C-42A3-B74A-9906A61A64AE@gmail.com>

On 08/09/2015 07:52 AM, Khem Raj wrote:
>
>> On Jul 30, 2015, at 12:40 AM, wenzong fan <wenzong.fan@windriver.com> wrote:
>>
>> On 07/29/2015 06:19 PM, Burton, Ross wrote:
>>>
>>> On 29 July 2015 at 08:34, <wenzong.fan@windriver.com
>>> <mailto:wenzong.fan@windriver.com>> wrote:
>>>
>>>     +# bjam is already stripped, don't strip it again
>>>     +INHIBIT_SYSROOT_STRIP = "1"
>>>
>>>
>>> In case it's even needed to debug bjam-native, how hard would it be to
>>> stop bjam from being stripped in the first place?
>>
>> By default, a release version is stripped, we could build & install the debug version for bjam.
>>
>> For specific changes, we only need to append "--debug" to build.sh, then update do_install() to select the unstripped version.
>>
>> Do you think this is the right ways?
>
>
> export INSTALL=“install” or something like that might do it. usually folks use install -s by default during install step which cause such issues.

The bjam is stripped while compiling via gcc options '-s'. There are 
three build types defined in build.jam:

...
     [ opt --release : [ opt --symbols : -g : -s ] -O3 ]
     [ opt --debug : -g -O0 -fno-inline ]
     [ opt --profile : -O3 -g -pg ]
...

Build & install "debug" version would provide unstripped bjam for 
further stripping. I have sent V2 patch:

[OE-core] [PATCH v2] bjam-native: build and install bjam.debug

Thanks
Wenzong

>
>> Thanks
>> Wenzong
>>
>>>
>>> Ross
>> --
>> _______________________________________________
>> Openembedded-core mailing list
>> Openembedded-core@lists.openembedded.org
>> http://lists.openembedded.org/mailman/listinfo/openembedded-core
>


      reply	other threads:[~2015-08-10  6:14 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-07-29  7:34 [PATCH] bjam-native: inhibit sysroot strip wenzong.fan
2015-07-29 10:19 ` Burton, Ross
2015-07-30  7:40   ` wenzong fan
2015-08-08 23:52     ` Khem Raj
2015-08-10  6:14       ` wenzong fan [this message]

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=55C84156.8090609@windriver.com \
    --to=wenzong.fan@windriver.com \
    --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.