From: "Khem Raj" <raj.khem@gmail.com>
To: Alexander Kanavin <alex.kanavin@gmail.com>
Cc: Patches and discussions about the oe-core layer
<openembedded-core@lists.openembedded.org>
Subject: Re: [OE-core] [PATCH 04/11] ruby: fix reproducibility
Date: Thu, 3 Dec 2020 11:52:16 -0800 [thread overview]
Message-ID: <CAMKF1soyXa8g9WyGL357BYkS+JK4PwYxz3wjqgZ9vFxGQUwGyw@mail.gmail.com> (raw)
In-Reply-To: <CANNYZj-fDQdkXVN=hjqb7u=bqPZhXfidO_cT+Buv6gB4gAN_ew@mail.gmail.com>
On Thu, Dec 3, 2020 at 11:20 AM Alexander Kanavin
<alex.kanavin@gmail.com> wrote:
>
> On Thu, 3 Dec 2020 at 20:16, Khem Raj <raj.khem@gmail.com> wrote:
>>
>>
>> where is this template used ? is it used on target ? is it possible to
>> just all bare compiler name then since it will still work on target
>> although not as important as if it was needed during cross builds.
>
>
> I don't think it is used on target, as harcoded host items would surely not have worked. Again, the goal here is not to ensure that target toolchain and target tests work (a large and not necessarily useful task), but merely to avoid host paths leaking into target packages.
>
I see that, I just want to ensure that deferring the problems does not
make them harder to detect in the future at the same time. It's easy
to fix them in the context than to revisit later.
> Alex
next prev parent reply other threads:[~2020-12-03 19:52 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-12-03 13:37 [PATCH 01/11] meta/lib/oe/reproducible.py: gitsm:// works just as fine as git:// for timestamps Alexander Kanavin
2020-12-03 13:37 ` [PATCH 02/11] kea: fix reproducibility Alexander Kanavin
2020-12-03 19:07 ` [OE-core] " Khem Raj
2020-12-03 19:12 ` Alexander Kanavin
2020-12-03 19:18 ` Khem Raj
2020-12-03 19:22 ` Alexander Kanavin
2020-12-03 20:33 ` Khem Raj
2020-12-03 13:37 ` [PATCH 03/11] llvm: " Alexander Kanavin
2020-12-03 13:37 ` [PATCH 04/11] ruby: " Alexander Kanavin
2020-12-03 19:15 ` [OE-core] " Khem Raj
2020-12-03 19:20 ` Alexander Kanavin
2020-12-03 19:52 ` Khem Raj [this message]
2020-12-03 13:37 ` [PATCH 05/11] webkitgtk: " Alexander Kanavin
2020-12-03 13:37 ` [PATCH 06/11] ffmpeg: " Alexander Kanavin
2020-12-03 13:37 ` [PATCH 07/11] piglit: " Alexander Kanavin
2020-12-03 13:37 ` [PATCH 08/11] serf: do not install the static library Alexander Kanavin
2020-12-03 19:29 ` [OE-core] " Khem Raj
2020-12-03 19:51 ` Alexander Kanavin
2020-12-03 13:37 ` [PATCH 09/11] llvm: sort the lists in generated source reproducibibly Alexander Kanavin
2020-12-03 19:45 ` [OE-core] " Khem Raj
2020-12-03 13:37 ` [PATCH 10/11] selftest/reproducible: enable world reproducibility test Alexander Kanavin
2020-12-03 13:37 ` [PATCH 11/11] selftest/reproducible: add an exclusion list for items that are not yet reproducible Alexander Kanavin
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=CAMKF1soyXa8g9WyGL357BYkS+JK4PwYxz3wjqgZ9vFxGQUwGyw@mail.gmail.com \
--to=raj.khem@gmail.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 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.