Buildroot Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Thomas Bonnefille via buildroot <buildroot@buildroot.org>
To: "Thomas Petazzoni" <thomas.petazzoni@bootlin.com>,
	"Thomas Bonnefille via buildroot" <buildroot@buildroot.org>
Cc: "Miquèl Raynal" <miquel.raynal@bootlin.com>,
	"Vicente Olivert Riera" <Vincent.Riera@imgtec.com>,
	"Bernd Kuhls" <bernd.kuhls@t-online.de>,
	"Peter Seiderer" <ps.report@gmx.net>,
	"Fabrice Fontaine" <fontaine.fabrice@gmail.com>
Subject: Re: [Buildroot] [PATCH] package/elfutils: bump to version 0.192
Date: Tue, 24 Dec 2024 11:50:09 +0100	[thread overview]
Message-ID: <D6JVFIFMR2JL.SOPHKL8DSYXP@bootlin.com> (raw)
In-Reply-To: <20241222162051.0a5b0956@windsurf>

Hello Thomas,
>
> On Sun, 22 Dec 2024 15:57:23 +0100
> Thomas Bonnefille via buildroot <buildroot@buildroot.org> wrote:
>
> > Fixes:
> >     https://autobuild.buildroot.org/results/29502fe97a15e4926de7cf129b641505697de9cd/
> > 
> > Signed-off-by: Thomas Bonnefille <thomas.bonnefille@bootlin.com>
>
> Thanks for the fix. However, we need to understand since when this
> problem started occurring so we can understand whether the fix needs to
> be backported to our stable 2024.02.x branch.

I did investigate a little deeper the issue, and it seems to occure when
using gcc14 and musl, as gcc14 isn't supported on 2024.02.x, I didn't
succeed to reproduce the error.

>
> Also, a 0.189 -> 0.192 bump brings quite a lot of other changes. Can we
> have a more minimal fix to backport? (And then do the version bump).

Indeed, a more minimal fix is to backport [this
patch](https://patchwork.sourceware.org/project/elfutils/patch/20231210202033.151578-1-raj.khem@gmail.com/#162118).
This is something that I did and can send in a follow up patch if
required.
>
> When fixing build issues, we're not only concerned about fixing the
> build issue, but also about understanding whether it needs to be fixed
> in 2024.02.x, which requires providing more details in the commit log
> *and* figuring out whether a more minimal solution than a bump is
> possible (sometimes the answer is "no", or "yes, but very complicated",
> and that's fine).

Thank you very much for thoses explanations, here the answer is yes
however as it can't be reproduced in the LTS and as a bump will be
required one day, is it necessary to first give a minimal solution ?

Thomas
_______________________________________________
buildroot mailing list
buildroot@buildroot.org
https://lists.buildroot.org/mailman/listinfo/buildroot

  reply	other threads:[~2024-12-24 10:50 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-12-22 14:57 [Buildroot] [PATCH] package/elfutils: bump to version 0.192 Thomas Bonnefille via buildroot
2024-12-22 15:20 ` Thomas Petazzoni via buildroot
2024-12-24 10:50   ` Thomas Bonnefille via buildroot [this message]
2025-02-05  8:51 ` Thomas Petazzoni via buildroot

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=D6JVFIFMR2JL.SOPHKL8DSYXP@bootlin.com \
    --to=buildroot@buildroot.org \
    --cc=Vincent.Riera@imgtec.com \
    --cc=bernd.kuhls@t-online.de \
    --cc=fontaine.fabrice@gmail.com \
    --cc=miquel.raynal@bootlin.com \
    --cc=ps.report@gmx.net \
    --cc=thomas.bonnefille@bootlin.com \
    --cc=thomas.petazzoni@bootlin.com \
    /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