From: Grant Edwards <grant.b.edwards@gmail.com>
To: buildroot@busybox.net
Cc: buildroot@uclibc.org
Subject: Re: [Buildroot] How to control host gcc version?
Date: Tue, 10 Sep 2024 22:26:34 -0000 (UTC) [thread overview]
Message-ID: <vbqh2p$2jk$1@ciao.gmane.io> (raw)
In-Reply-To: 20240910224640.5f832e45@windsurf
On 2024-09-10, Thomas Petazzoni via buildroot <buildroot@buildroot.org> wrote:
> On Tue, 10 Sep 2024 19:10:29 -0000 (UTC)
> Grant Edwards <grant.b.edwards@gmail.com> wrote:
>> [...]
>>
>> HOSTCXX, the host C++ compiler to use
>> HOSTCC, the host C compiler to use
>
> Indeed. But in your case, what you probably should do is use a Docker
> container. You can use the utils/docker-run script to easily run the
> build in a docker container.
>
> Basically do:
>
> ./utils/docker-run make
It looks like 2020.02.7 doesn't have a docker-run.
It turns out it's not the gcc version that's "too new", it's the glibc
version that's "too new", and Gentoo doesn't support having multiple
versions of that installed. :)
I'm going to have to manually upgrade buildroot's m4 package from 4.18
to 4.19.
Once I get the vendor "supported" buildroot configuration built and
running, I'll look into upgrading to a newer version of buildroot --
perhaps one with a refrence docker image for building it.
--
Grant
_______________________________________________
buildroot mailing list
buildroot@buildroot.org
https://lists.buildroot.org/mailman/listinfo/buildroot
prev parent reply other threads:[~2024-09-10 22:26 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-09-10 19:01 [Buildroot] How to control host gcc version? Grant Edwards
2024-09-10 19:10 ` Grant Edwards
2024-09-10 20:46 ` Thomas Petazzoni via buildroot
2024-09-10 21:16 ` Grant Edwards
2024-09-10 22:26 ` Grant Edwards [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='vbqh2p$2jk$1@ciao.gmane.io' \
--to=grant.b.edwards@gmail.com \
--cc=buildroot@busybox.net \
--cc=buildroot@uclibc.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