Buildroot Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Thomas Petazzoni via buildroot <buildroot@buildroot.org>
To: Arnout Vandecappelle via buildroot <buildroot@buildroot.org>
Cc: "Yann E. MORIN" <yann.morin.1998@free.fr>,
	Vincent Fazio <vfazio@xes-inc.com>
Subject: Re: [Buildroot] [PATCH] support/bootlin-toolchains: don't depend on non-existent gcc version
Date: Wed, 8 Nov 2023 23:05:13 +0100	[thread overview]
Message-ID: <20231108230513.6c99d8dc@windsurf> (raw)
In-Reply-To: <f53be617-ff47-0675-edc8-ae5a36a67716@mind.be>

On Sun, 8 Oct 2023 11:32:38 +0200
Arnout Vandecappelle via buildroot <buildroot@buildroot.org> wrote:

> > However, when the toolchain is using the latest gcc version currently
> > known to Buildroot, this generates a dependency on a non-existing gcc
> > version. For example, a toolchain using gcc 13, the most recent version
> > currently known to Buildroot, this would generate a dependency against
> > BR2_ARCH_NEEDS_GCC_AT_LEAST_14, which does not exist yet.  
> 
>   That means, however, that if we add GCC 14, we need to remember to add the 
> condition to the Bootlin toolchains again... Of course, that can easily be 
> solved by regenerating them, but we don't currently do that when adding a new 
> GCC version.
> 
>   So really, I would feel more comfortable just adding the symbols for GCC 14 
> support already.

Yes, I think I agree too. Otherwise, we will never remember that we
need to re-generate the Bootlin toolchain files when the next
BR2_ARCH_NEEDS_GCC_AT_LEAST_xyz. And actually, it kind of makes sense
to have the BR2_ARCH_NEEDS_GCC_AT_LEAST_14 option available early on:
gcc 13.x toolchains should indeed say that they are not relevant if the
arch needs gcc 14. gcc 14.x may not exist yet, but the gcc 13.x
toolchain exists, and should say "I'm not good if your arch is so new
that it needs a new compiler than the one I provide".

Best regards,

Thomas
-- 
Thomas Petazzoni, co-owner and CEO, Bootlin
Embedded Linux and Kernel engineering and training
https://bootlin.com
_______________________________________________
buildroot mailing list
buildroot@buildroot.org
https://lists.buildroot.org/mailman/listinfo/buildroot

      reply	other threads:[~2023-11-08 22:05 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-10-07 20:57 [Buildroot] [PATCH] support/bootlin-toolchains: don't depend on non-existent gcc version Yann E. MORIN
2023-10-08  9:32 ` Arnout Vandecappelle via buildroot
2023-11-08 22:05   ` Thomas Petazzoni via buildroot [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=20231108230513.6c99d8dc@windsurf \
    --to=buildroot@buildroot.org \
    --cc=thomas.petazzoni@bootlin.com \
    --cc=vfazio@xes-inc.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