From: "Matt Staveley-Taylor" <matt.stav.taylor@gmail.com>
To: "Thomas Petazzoni" <thomas.petazzoni@bootlin.com>
Cc: buildroot@buildroot.org
Subject: Re: [Buildroot] [PATCH 0/2] Add bcachefs-tools package
Date: Thu, 11 Apr 2024 23:51:57 +0100 [thread overview]
Message-ID: <D0HNU5GTK85W.1677VO1E2EDIS@gmail.com> (raw)
In-Reply-To: <20240411144804.03fed97d@windsurf>
On Thu Apr 11, 2024 at 1:48 PM BST, Thomas Petazzoni wrote:
> It seems that
> https://github.com/llvm/llvm-project/releases/tag/llvmorg-18.1.1 has
> pre-built binaries, but not for the very common x86-64 linux host
> platform, which seems odd? Apparently, those binaries are made by
> volunteers. Not sure how much we want to use those binaries.
Yeah, agreed. Perhaps there is some Buildroot infrastructure we can
leverage for building these ourselves?
Failing that -- is there actually a problem with merging the patch
as-is? I can see a couple of other packages that already depend on
host-clang.
Matt
_______________________________________________
buildroot mailing list
buildroot@buildroot.org
https://lists.buildroot.org/mailman/listinfo/buildroot
prev parent reply other threads:[~2024-04-11 22:52 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-04-08 1:38 [Buildroot] [PATCH 0/2] Add bcachefs-tools package Matt Staveley-Taylor
2024-04-08 1:38 ` [Buildroot] [PATCH 1/2] package: add support for extracting zstd archives Matt Staveley-Taylor
2024-07-14 20:48 ` Thomas Petazzoni via buildroot
2024-04-08 1:38 ` [Buildroot] [PATCH 2/2] package/bcachefs-tools: new package Matt Staveley-Taylor
2024-07-14 20:56 ` Thomas Petazzoni via buildroot
2024-04-08 20:54 ` [Buildroot] [PATCH 0/2] Add bcachefs-tools package Thomas Petazzoni via buildroot
2024-04-09 22:43 ` Matt Staveley-Taylor
2024-04-10 9:30 ` Thomas Petazzoni via buildroot
2024-04-11 1:32 ` Matt Staveley-Taylor
2024-04-11 12:48 ` Thomas Petazzoni via buildroot
2024-04-11 22:51 ` Matt Staveley-Taylor [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=D0HNU5GTK85W.1677VO1E2EDIS@gmail.com \
--to=matt.stav.taylor@gmail.com \
--cc=buildroot@buildroot.org \
--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