Openembedded Core Discussions
 help / color / mirror / Atom feed
From: Richard Purdie <richard.purdie@linuxfoundation.org>
To: Denys Dmytriyenko <denis@denix.org>
Cc: openembedded-core@lists.openembedded.org
Subject: Re: [OE-core] [PATCH v3 1/2] gcc: remove paths to sysroot from configargs.h and checksum-options for gcc-cross-canadian
Date: Mon, 22 Jul 2024 22:23:16 +0100	[thread overview]
Message-ID: <d2f84b88c3f12c1844c3c0fbefe4973dc27d06f5.camel@linuxfoundation.org> (raw)
In-Reply-To: <20240722211816.GS17572@denix.org>

On Mon, 2024-07-22 at 17:18 -0400, Denys Dmytriyenko wrote:
> On Mon, Jul 22, 2024 at 09:51:51PM +0100, Richard Purdie wrote:
> > On Mon, 2024-07-22 at 01:34 -0400, Denys Dmytriyenko via
> > lists.openembedded.org wrote:
> > > From: Oleksandr Hnatiuk <ohnatiuk@cisco.com>
> > > 
> > > Apply fixes from gcc-cross (84a78f46d594 and 0ead8cbdfb96) to
> > > gcc-cross-canadian.
> > > This will improve (but not fix) reproducibility of gcc-cross-
> > > canadian.
> > > Also move this code to functions to avoid code duplication.
> > > 
> > > Signed-off-by: Oleksandr Hnatiuk <ohnatiuk@cisco.com>
> > > Signed-off-by: Denys Dmytriyenko <denys@konsulko.com>
> > > ---
> > > v3 - add common functions to gcc-common.inc instead of gcc-
> > > configure-common.h
> > > 
> > >  meta/recipes-devtools/gcc/gcc-common.inc      | 19
> > > +++++++++++++++++++
> > >  .../gcc/gcc-configure-common.inc              |  1 -
> > >  .../gcc/gcc-cross-canadian.inc                |  3 +++
> > >  meta/recipes-devtools/gcc/gcc-cross.inc       | 15 ++-----------
> > > --
> > >  meta/recipes-devtools/gcc/gcc-target.inc      | 16 ++-----------
> > > ---
> > >  5 files changed, 26 insertions(+), 28 deletions(-)
> > 
> > I ran a test build with this series and there is still a
> > reproducibility issue:
> > 
> > https://autobuilder.yoctoproject.org/typhoon/#/builders/117/builds/5097
> > 
> > http://autobuilder.yocto.io/pub/repro-fail/oe-reproducible-20240722-tr5vb5sa/packages/
> > 
> > the key difference appearing to start in gcc-src.
> 
> Thanks. What's the simplest way to reproduce it locally?

Build the affected recipes in two different build paths and compare the
packages in question.

You could narrow down the selftest to that recipe and then "oe-selftest
-r reproducible.ReproducibleTests.test_reproducible_builds" too. 

Change targets in meta/lib/oeqa/selftest/cases/reproducible.py to be
the recipe in question rather than the default of:
'core-image-minimal', 'core-image-sato', 'core-image-full-cmdline',
'core-image-weston', 'world', 'virtual/librpc', 'virtual/libsdl2',
'virtual/crypt' to narrow it down and make it faster.

You can likely use most things from sstate too rather than rebuilding
most of one of the builds.

Cheers,

Richard


      reply	other threads:[~2024-07-22 21:23 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-07-22  5:34 [PATCH v3 1/2] gcc: remove paths to sysroot from configargs.h and checksum-options for gcc-cross-canadian Denys Dmytriyenko
2024-07-22  5:34 ` [PATCH 2/2] gcc: unify cleanup of include-fixed, apply to cross-canadian Denys Dmytriyenko
2024-07-22 20:51 ` [OE-core] [PATCH v3 1/2] gcc: remove paths to sysroot from configargs.h and checksum-options for gcc-cross-canadian Richard Purdie
2024-07-22 21:18   ` Denys Dmytriyenko
2024-07-22 21:23     ` Richard Purdie [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=d2f84b88c3f12c1844c3c0fbefe4973dc27d06f5.camel@linuxfoundation.org \
    --to=richard.purdie@linuxfoundation.org \
    --cc=denis@denix.org \
    --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