From: Thomas Petazzoni via buildroot <buildroot@buildroot.org>
To: James Hilliard <james.hilliard1@gmail.com>
Cc: Joseph Kogut <joseph.kogut@gmail.com>,
Romain Naour <romain.naour@gmail.com>,
Valentin Korenblit <valentinkorenblit@gmail.com>,
buildroot@buildroot.org
Subject: Re: [Buildroot] [PATCH 1/1] package:{clang, lld, llvm}: bump to version 11.1.0
Date: Mon, 31 Jan 2022 10:45:53 +0100 [thread overview]
Message-ID: <20220131104553.715b97ce@windsurf> (raw)
In-Reply-To: <20220131015937.4113728-1-james.hilliard1@gmail.com>
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?
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
next prev parent reply other threads:[~2022-01-31 9:46 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 [this message]
2022-01-31 11:36 ` Romain Naour
2022-02-02 19:39 ` James Hilliard
2022-02-12 12:55 ` Arnout Vandecappelle
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=20220131104553.715b97ce@windsurf \
--to=buildroot@buildroot.org \
--cc=james.hilliard1@gmail.com \
--cc=joseph.kogut@gmail.com \
--cc=romain.naour@gmail.com \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox