From: Arnout Vandecappelle <arnout@mind.be>
To: James Hilliard <james.hilliard1@gmail.com>,
Romain Naour <romain.naour@smile.fr>
Cc: Joseph Kogut <joseph.kogut@gmail.com>,
Thomas Petazzoni <thomas.petazzoni@bootlin.com>,
buildroot <buildroot@buildroot.org>,
Romain Naour <romain.naour@gmail.com>,
Matthew Weber <matthew.weber@collins.com>,
Valentin Korenblit <valentinkorenblit@gmail.com>
Subject: Re: [Buildroot] [PATCH 1/1] package:{clang, lld, llvm}: bump to version 11.1.0
Date: Sat, 12 Feb 2022 13:55:17 +0100 [thread overview]
Message-ID: <6b5d3b43-fe50-0dd2-2903-e404ee7792b9@mind.be> (raw)
In-Reply-To: <CADvTj4q9ea12wJk3FfpRdwKVhvLDGrBa9HW89rA2tfPQhX+NRg@mail.gmail.com>
On 02/02/2022 20:39, James Hilliard wrote:
> On Mon, Jan 31, 2022 at 4:36 AM Romain Naour <romain.naour@smile.fr> wrote:
>>
>> Hello James, Thomas, All,
>>
>> Le 31/01/2022 à 10:45, Thomas Petazzoni via buildroot a écrit :
>>> On Sun, 30 Jan 2022 18:59:37 -0700
>>> James Hilliard <james.hilliard1@gmail.com> wrote:
>>>
>>>> This appears to be the latest version that has a working lld build.
>>>>
>>>> Version 12.0.0 and newer have broken lld stand-alone builds:
>>>> https://bugs.llvm.org/show_bug.cgi?id=49228
>>>>
>>>> Signed-off-by: James Hilliard <james.hilliard1@gmail.com>
>>>
>>> Is this really enough? I remember seeing patches a long time ago doing
>>> bumps on LLVM/Clang and that was much more involved, which I think
>>> explains why we're still at version 9.x.
>>>
>>> Romain, any comments on this?
>>
>> Adding Matt in Cc:
>>
>> IIRC, there is an issue with libclc package which is part of the llvm project.
>>
>> Due to the gap between the two version, all CMake options must be reviewed (long
>> and boring task I agree).
>
> Oh, I guess there was already a series here with more changes:
> https://patchwork.ozlabs.org/project/buildroot/list/?series=233431&submitter=&state=*&q=&archive=both&delegate=
Given the discussion in both these threads, I've marked the patch as Changes
Requested.
Regards,
Arnout
_______________________________________________
buildroot mailing list
buildroot@buildroot.org
https://lists.buildroot.org/mailman/listinfo/buildroot
next prev parent reply other threads:[~2022-02-12 12:55 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-01-31 1:59 [Buildroot] [PATCH 1/1] package:{clang, lld, llvm}: bump to version 11.1.0 James Hilliard
2022-01-31 9:45 ` Thomas Petazzoni via buildroot
2022-01-31 11:36 ` Romain Naour
2022-02-02 19:39 ` James Hilliard
2022-02-12 12:55 ` Arnout Vandecappelle [this message]
2022-03-24 4:30 ` James Hilliard
2022-03-28 20:29 ` [Buildroot] [External] " Weber, Matthew L Collins 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=6b5d3b43-fe50-0dd2-2903-e404ee7792b9@mind.be \
--to=arnout@mind.be \
--cc=buildroot@buildroot.org \
--cc=james.hilliard1@gmail.com \
--cc=joseph.kogut@gmail.com \
--cc=matthew.weber@collins.com \
--cc=romain.naour@gmail.com \
--cc=romain.naour@smile.fr \
--cc=thomas.petazzoni@bootlin.com \
--cc=valentinkorenblit@gmail.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.