From: "Yu, Mingli" <mingli.yu@windriver.com>
To: Alexander Kanavin <alex.kanavin@gmail.com>
Cc: openembedded-core@lists.openembedded.org
Subject: Re: [PATCH] boost: Improve reproducibility
Date: Fri, 1 Jun 2018 13:38:45 +0800 [thread overview]
Message-ID: <5B10DBE5.5050603@windriver.com> (raw)
In-Reply-To: <CANNYZj_3y_uP4a188SREALPvpBL=xnu=QZAW9s7V9iSG2a-t9Q@mail.gmail.com>
On 2018年06月01日 13:08, Alexander Kanavin wrote:
> 2018-06-01 4:39 GMT+03:00 Yu, Mingli <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?
>>
>>
>> Thanks very much Richard for your respond!
>> I did try to strip only file which in question, but not find out the
>> solution and then turn to strip the context library.
>>
>> Alex,
>> Do you have any suggestion?
>
> Yes - as RP said, please investigate how the path gets into this
> specific file (but not other files) in the first place, and whether we
> can disable or make it not happen, rather than strip the path after
> the fact.
Hi Alex,
Thanks for your respond!
I did investigate the path a lot before send out the patch, but didn't
figure out why it introduce the path for make_x86_64_sysv_elf_gas.o
whose source file is make_x86_64_sysv_elf_gas.S.
Anyway, I will try to dig more.
If you have any ideas, welcome to help provide some hint.
Thanks,
>
> Alex
>
next prev parent reply other threads:[~2018-06-01 5:43 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
2018-06-01 1:39 ` Yu, Mingli
2018-06-01 5:08 ` Alexander Kanavin
2018-06-01 5:38 ` Yu, Mingli [this message]
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=5B10DBE5.5050603@windriver.com \
--to=mingli.yu@windriver.com \
--cc=alex.kanavin@gmail.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