All of lore.kernel.org
 help / color / mirror / Atom feed
From: Thomas Petazzoni via buildroot <buildroot@buildroot.org>
To: Grant Edwards <grant.b.edwards@gmail.com>
Cc: buildroot@busybox.net, buildroot@uclibc.org
Subject: Re: [Buildroot] How to control host gcc version?
Date: Tue, 10 Sep 2024 22:46:40 +0200	[thread overview]
Message-ID: <20240910224640.5f832e45@windsurf> (raw)
In-Reply-To: <vbq5j5$aai$1@ciao.gmane.io>

On Tue, 10 Sep 2024 19:10:29 -0000 (UTC)
Grant Edwards <grant.b.edwards@gmail.com> wrote:

> Ah, found it:
> 
>     8.6. Environment variables
> 
>     Buildroot also honors some environment variables, when they are
>     passed to make or set in the environment:
> 
>     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

and it will do the Buildroot build in our "reference" Debian bullseye
Docker container. If you're not happy with this container, you can do:

	IMAGE=<your-docker-image> ./utils/docker-run make

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:[~2024-09-10 20:51 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 [this message]
2024-09-10 21:16     ` Grant Edwards
2024-09-10 22:26     ` Grant Edwards

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=20240910224640.5f832e45@windsurf \
    --to=buildroot@buildroot.org \
    --cc=buildroot@busybox.net \
    --cc=buildroot@uclibc.org \
    --cc=grant.b.edwards@gmail.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.