From: Matt Turner <mattst88@gentoo.org>
To: gentoo-dev@lists.gentoo.org
Subject: Re: [gentoo-dev] Multiple LLVM versions with single sys-devel/lld. How to match runtime?
Date: Sat, 29 Oct 2022 15:01:10 -0400 [thread overview]
Message-ID: <CAEdQ38EmU3YgR+MYZ57wWah3acf8DLMt2CfcnUDcGq4TCAjQcw@mail.gmail.com> (raw)
In-Reply-To: <d7105903-e67b-1729-d518-a52f49c76dda@gentoo.org>
On Sat, Oct 29, 2022 at 12:53 PM Piotr Karbowski <slashbeast@gentoo.org> wrote:
>
> On 29/10/2022 18.22, Matt Turner wrote:
> > Have you seen these commits?
>
> I did not, thanks. Seems like the solution. Is there a reason why llvm:N
> do not pull in lld:N in that case?
lld isn't a dependency of llvm; it's the same reason why llvm:N
doesn't depend on clang:N.
next prev parent reply other threads:[~2022-10-29 19:01 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-10-29 16:00 [gentoo-dev] Multiple LLVM versions with single sys-devel/lld. How to match runtime? Piotr Karbowski
2022-10-29 16:22 ` Matt Turner
2022-10-29 16:52 ` Piotr Karbowski
2022-10-29 19:01 ` Matt Turner [this message]
2022-10-29 20:35 ` Piotr Karbowski
2022-10-29 20:38 ` Piotr Karbowski
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=CAEdQ38EmU3YgR+MYZ57wWah3acf8DLMt2CfcnUDcGq4TCAjQcw@mail.gmail.com \
--to=mattst88@gentoo.org \
--cc=gentoo-dev@lists.gentoo.org \
/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