Buildroot Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Gwenhael Goavec-Merou <gwenj@trabucayre.com>
To: Bagas Sanjaya <bagasdotme@gmail.com>
Cc: Gwenhael Goavec-Merou <gwenhael.goavec-merou@trabucayre.com>,
	"Yann E. MORIN" <yann.morin.1998@free.fr>,
	Thomas Petazzoni <thomas.petazzoni@bootlin.com>,
	buildroot@buildroot.org
Subject: Re: [Buildroot] Specific toolchain components version support (was Re: [PATCH v2] package/gnuradio: restrict gcc to >= 9.3.0)
Date: Sat, 10 Dec 2022 17:28:36 +0100	[thread overview]
Message-ID: <20221210172836.0e872e46@x230_1.trabucayre.com> (raw)
In-Reply-To: <07221b04-b25b-1f24-6ad2-872c66a086e7@gmail.com>

Hi all,

On Sat, 10 Dec 2022 17:02:37 +0700
Bagas Sanjaya <bagasdotme@gmail.com> wrote:

> On 12/10/22 05:30, Thomas Petazzoni via buildroot wrote:
> > In any case, we need to patch out, because we can't express a
> > dependency on >= 9.3.0 in Buildroot, we can only express a dependency
> > on >= 9.x.
> >   
> 
> If we go down to x.y requirement of toolchain components, we also need
> to be able to select specific x.y (minor release) components version
> when building the Buildroot toolchain. For example, someone targetting
> Raspberry Pi 4 may require GCC 10.2.0, Binutils 2.35.2, and glibc 2.31
> (these are versions used in Debian/Raspberry Pi OS 11). Linux kernel
> headers are unaffected, since even custom tarball containing exact
> kernel version can be specified.
> 
It's my fault: not a closer look to when std::filesystem was introduce and followed
gnuradio's commit instead of checking gcc releases.

Sorry for the noise...

Gwen


> Cc'ing Yann and Arnout to help sorting this out.
> 
> Thanks.
> 
> -- 
> An old man doll... just what I always wanted! - Clara
> 
_______________________________________________
buildroot mailing list
buildroot@buildroot.org
https://lists.buildroot.org/mailman/listinfo/buildroot

      reply	other threads:[~2022-12-10 16:27 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-12-09 14:43 [Buildroot] [PATCH v2] package/gnuradio: restrict gcc to >= 9.3.0 Gwenhael Goavec-Merou
2022-12-09 15:27 ` Thomas Petazzoni via buildroot
2022-12-09 15:32   ` Gwenhael Goavec-Merou
     [not found]     ` <20221209163756.118bd1d5@x230_1.trabucayre.com>
2022-12-09 16:10       ` Thomas Petazzoni via buildroot
2022-12-10  4:38         ` Bagas Sanjaya
2022-12-09 22:30 ` Thomas Petazzoni via buildroot
2022-12-10 10:02   ` [Buildroot] Specific toolchain components version support (was Re: [PATCH v2] package/gnuradio: restrict gcc to >= 9.3.0) Bagas Sanjaya
2022-12-10 16:28     ` Gwenhael Goavec-Merou [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=20221210172836.0e872e46@x230_1.trabucayre.com \
    --to=gwenj@trabucayre.com \
    --cc=bagasdotme@gmail.com \
    --cc=buildroot@buildroot.org \
    --cc=gwenhael.goavec-merou@trabucayre.com \
    --cc=thomas.petazzoni@bootlin.com \
    --cc=yann.morin.1998@free.fr \
    /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