From: Richard Purdie <richard.purdie@linuxfoundation.org>
To: mingli.yu@windriver.com, alexander.kanavin@linux.intel.com,
openembedded-core@lists.openembedded.org
Subject: Re: [PATCH] boost: Improve reproducibility
Date: Thu, 31 May 2018 14:13:24 +0100 [thread overview]
Message-ID: <1527772404.16911.155.camel@linuxfoundation.org> (raw)
In-Reply-To: <20180531062031.40334-1-mingli.yu@windriver.com>
On Wed, 2018-05-30 at 23:20 -0700, mingli.yu@windriver.com wrote:
> From: Mingli Yu <mingli.yu@windriver.com>
>
> boost_context includes some assembly source
> files and will export the assembly object file
> make_x86_64_sysv_elf_gas.o which contains host
> path as below:
> $ readelf --wide --symbols /my-build/boost/1.67.0-
> r0/boost_1_67_0/x86_64-poky-
> linux/boost/bin.v2/libs/context/build/aca09349fdb84d131321425f6c3a38e
> d/libboost_context.so.1.67
> 42: 0000000000000000 0 FILE LOCAL DEFAULT ABS /my-build/boost/1.67.0-
> r0/boost_1_67_0/x86_64-poky-
> linux/boost/bin.v2/libs/context/build/aca09349fdb84d131321425f6c3a38e
> d/asm/make_x86_64_sysv_elf_gas.o
>
> Enable stirp for boost_context to hidden the
> symbols
>
> [YOCTO #12708]
>
> Signed-off-by: Mingli Yu <mingli.yu@windriver.com>
This looks very unlikely to ever make it upstream. Rather than carrying
a patch to boost forever would we want to just strip the file in
question with a custom command?
Alternatively, can we stop this path being injected into the binary in
the first place?
Cheers,
Richard
next prev parent reply other threads:[~2018-05-31 13:13 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-05-31 6:20 [PATCH] boost: Improve reproducibility mingli.yu
2018-05-31 13:13 ` Richard Purdie [this message]
2018-06-01 1:39 ` Yu, Mingli
2018-06-01 5:08 ` Alexander Kanavin
2018-06-01 5:38 ` Yu, Mingli
2018-06-01 8:36 ` Alexander Kanavin
2018-06-05 2:44 ` Yu, Mingli
2018-06-01 17:07 ` Khem Raj
2018-06-01 17:56 ` Alexander Kanavin
2018-06-01 18:33 ` Khem Raj
2018-06-01 19:34 ` Alexander Kanavin
2018-06-15 6:44 ` Khem Raj
2018-06-15 6:54 ` Alexander Kanavin
2018-06-15 7:31 ` Yu, Mingli
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=1527772404.16911.155.camel@linuxfoundation.org \
--to=richard.purdie@linuxfoundation.org \
--cc=alexander.kanavin@linux.intel.com \
--cc=mingli.yu@windriver.com \
--cc=openembedded-core@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox