Buildroot Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Thomas Petazzoni via buildroot <buildroot@buildroot.org>
To: Arnout Vandecappelle <arnout@mind.be>
Cc: "Romain Naour" <romain.naour@gmail.com>,
	"Ignacy Gawędzki" <ignacy.gawedzki@green-communications.fr>,
	buildroot@buildroot.org
Subject: Re: [Buildroot] [PATCH] package/elfutils: enable building with musl-based toolchains
Date: Mon, 17 Jul 2023 22:09:31 +0200	[thread overview]
Message-ID: <20230717220931.20b397c0@windsurf> (raw)
In-Reply-To: <bc55ba52-133a-d350-a935-432e852f19f6@mind.be>

On Mon, 17 Jul 2023 17:31:19 +0200
Arnout Vandecappelle <arnout@mind.be> wrote:

>   Yeah, we have version checking for GCC and kernel headers, but not for libc. 
> It's fairly rare that a version dependency is needed on libc. So we basically 
> just assume that libc is up to date.
> 
>   What we sometimes do in such a case it to add an exception in the 
> genrandconfig script, to make sure that that combination isn't tried.
> 
>   Ideally, though, that toolchain configuration should just be replaced with the 
> equivalent bootlin toolchain. Only, there is no bootlin toolchain for 
> mips64-n64. Any idea why not, Thomas?

Because I'm not super familiar with MIPS, so I don't know which
toolchain variants make the most sense, and I never got any request for
mips64-n64. I can probably add this toolchain variant in
toolchains.bootlin.com for the next rebuild.

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-07-17 20:09 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-07-14  9:08 [Buildroot] [PATCH] package/elfutils: enable building with musl-based toolchains Ignacy Gawędzki
2023-07-14 10:18 ` Thomas Petazzoni via buildroot
2023-07-17 14:09   ` Ignacy Gawędzki
2023-07-17 15:31     ` Arnout Vandecappelle via buildroot
2023-07-17 20:09       ` Thomas Petazzoni via buildroot [this message]
2023-07-17 20:11     ` 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=20230717220931.20b397c0@windsurf \
    --to=buildroot@buildroot.org \
    --cc=arnout@mind.be \
    --cc=ignacy.gawedzki@green-communications.fr \
    --cc=romain.naour@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox