Will do. Thanks.
On 11/28/2022 15:26, Alexander Kanavin wrote:
Ok then you need to place all of this and the bug link into the commit
message, and then you can run the reproducibility test locally, no?
Alex
On Mon, 28 Nov 2022 at 22:22, Denys Dmytriyenko wrote:
On Mon, Nov 28, 2022 at 09
Ok then you need to place all of this and the bug link into the commit
message, and then you can run the reproducibility test locally, no?
Alex
On Mon, 28 Nov 2022 at 22:22, Denys Dmytriyenko wrote:
>
> On Mon, Nov 28, 2022 at 09:58:43PM +0100, Alexander Kanavin wrote:
> > What build errors is t
On Mon, Nov 28, 2022 at 09:58:43PM +0100, Alexander Kanavin wrote:
> What build errors is this addressing and how can they be observed?
https://bugzilla.yoctoproject.org/show_bug.cgi?id=14976
> On Mon, 28 Nov 2022 at 21:46, Ryan Eatmon via lists.openembedded.org
> wrote:
> >
> > The previous ve
Apologies. I'll happily submit a patch v2 that further explains it if
we want to move forward with this patch.
There was a discussion back in September related to some of the TI
machines and the riscv64 machine failing with a panic on recipes in
meta-virtualization that use go.
https://list
What build errors is this addressing and how can they be observed?
Alex
On Mon, 28 Nov 2022 at 21:46, Ryan Eatmon via lists.openembedded.org
wrote:
>
> The previous version of this patch was a little too zealous in
> cleaning up the envvironment. Some of the variable impacted
> by the filerComp
The previous version of this patch was a little too zealous in
cleaning up the envvironment. Some of the variable impacted
by the filerCompilerFlags() function require at least one
value to remain in the array. In this case, the values for
ccExe, cxxExe, and fcExe require a value or it results in
