From: Josua Stingelin <josuast@hotmail.com>
To: Carlo Zancanaro <carlo@zancanaro.id.au>
Cc: help-guix@gnu.org
Subject: Re: clang-12 doesn't contain clang-extra-tools
Date: Tue, 10 Aug 2021 13:59:32 +0200 [thread overview]
Message-ID: <DB9PR06MB7657924E1E8996CF0138AE63AAF79@DB9PR06MB7657.eurprd06.prod.outlook.com> (raw)
In-Reply-To: <87k0ktd14e.fsf@zancanaro.id.au>
[-- Attachment #1: Type: text/plain, Size: 428 bytes --]
> On Tue, Aug 10 2021, Josua Stingelin wrote:>
> > As far as I understand, if tools-extra is defined these get installed
> > when installing the 'out'-output of the package.
>
> This is where you're running into problems. The clangd binary is actually
> installed into the "extra" output of the package. That's what the move
> procedure is doing in the snippet you quoted.
Aww snap. Obviously.
Thank for the hint!
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 488 bytes --]
prev parent reply other threads:[~2021-08-10 11:59 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-08-10 10:00 clang-12 doesn't contain clang-extra-tools Josua Stingelin
2021-08-10 10:50 ` Carlo Zancanaro
2021-08-10 11:59 ` Josua Stingelin [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
List information: https://guix.gnu.org/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=DB9PR06MB7657924E1E8996CF0138AE63AAF79@DB9PR06MB7657.eurprd06.prod.outlook.com \
--to=josuast@hotmail.com \
--cc=carlo@zancanaro.id.au \
--cc=help-guix@gnu.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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).