From: Kalle Valo <kvalo@kernel.org>
To: Nathan Chancellor <nathan@kernel.org>
Cc: Linus Torvalds <torvalds@linux-foundation.org>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
David Airlie <airlied@gmail.com>,
Daniel Vetter <daniel@ffwll.ch>,
dri-devel@lists.freedesktop.org,
linux-toolchains@vger.kernel.org, llvm@lists.linux.dev
Subject: Re: Linux 6.3-rc3
Date: Fri, 24 Mar 2023 17:23:12 +0200 [thread overview]
Message-ID: <87o7oicgwv.fsf@kernel.org> (raw)
In-Reply-To: <20230324151150.GC428955@dev-arch.thelio-3990X> (Nathan Chancellor's message of "Fri, 24 Mar 2023 08:11:50 -0700")
Nathan Chancellor <nathan@kernel.org> writes:
>> This is nitpicking but it would be nice if the tarball contents wouldn't
>> conflict with each other. Now both llvm-16.0.0-aarch64.tar.gz and
>> llvm-16.0.0-x86_64.tar extract to the same directory llvm-16.0.0 with
>> same binary names. It would be much better if they would extract to
>> llvm-16.0.0-aarch64 and llvm-16.0.0-x86_64, respectively.
>>
>> For example, Arnd's crosstool packages don't conflict with each other:
>>
>> https://mirrors.edge.kernel.org/pub/tools/crosstool/
>
> I could certainly do that but what is the use case for extracting both?
> You cannot run the aarch64 version on an x86_64 host and vice versa, so
> why bother extracting them?
Ah, I didn't realise that. I assumed llvm-16.0.0-aarch64.tar.gz was a
cross compiler. I'm sure you documented that in the page but hey who
reads the documentation ;)
> I had figured the architecture would be irrelevant once installed on
> the host, so I opted only to include it in the tarball name. Perhaps I
> should make it clearer that these are the host architectures, not the
> target architectures (because clang is multi-targeted, unlike GCC)?
Makes sense now. But I still think it's good style that a tarball named
llvm-16.0.0-aarch64.tar.gz extracts to llvm-16.0.0-aarch64.
>> And maybe request a similar llvm directory under pub/tools to make it
>> more official? :)
>
> Yes, I was talking that over with Nick recently, as having it under a
> group on kernel.org would make taking over maintainership easier should
> something happen to me :)
Yeah, sharing the load is always good.
--
https://patchwork.kernel.org/project/linux-wireless/list/
https://wireless.wiki.kernel.org/en/developers/documentation/submittingpatches
next prev parent reply other threads:[~2023-03-24 15:23 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <CAHk-=wiPd8R8-zSqTOtJ9KYeZLBByHug7ny3rgP-ZqzpP_KELg@mail.gmail.com>
[not found] ` <20230320180501.GA598084@dev-arch.thelio-3990X>
[not found] ` <CAHk-=wgSqpdkeJBb92M37JNTdRQJRnRUApraHKE8uGHTqQuu2Q@mail.gmail.com>
2023-03-20 18:53 ` Linux 6.3-rc3 Nathan Chancellor
2023-03-20 19:22 ` Nathan Chancellor
2023-03-22 12:44 ` Kalle Valo
2023-03-22 16:36 ` Nathan Chancellor
2023-03-22 20:36 ` Nathan Chancellor
2023-03-24 10:54 ` Kalle Valo
2023-03-24 15:11 ` Nathan Chancellor
2023-03-24 15:23 ` Kalle Valo [this message]
2023-03-28 19:07 ` Nathan Chancellor
2023-03-29 8:39 ` Kalle Valo
2023-03-22 16:40 ` Sedat Dilek
2023-03-22 16:55 ` Linus Torvalds
2023-03-22 18:17 ` Nick Desaulniers
2023-03-24 17:16 ` Masahiro Yamada
2023-03-27 16:12 ` Jani Nikula
2023-03-27 17:03 ` Kalle Valo
[not found] ` <4adbed5a-6f73-42ac-b7be-e12c764ae808@roeck-us.net>
[not found] ` <CAHk-=wgyJREUR1WgfFmie5XVJnBLr1VPVbSibh1+Cq57Bh4Tag@mail.gmail.com>
2023-03-20 22:06 ` Nathan Chancellor
2023-03-20 22:48 ` Segher Boessenkool
2023-03-20 23:41 ` Linus Torvalds
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=87o7oicgwv.fsf@kernel.org \
--to=kvalo@kernel.org \
--cc=airlied@gmail.com \
--cc=daniel@ffwll.ch \
--cc=dri-devel@lists.freedesktop.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-toolchains@vger.kernel.org \
--cc=llvm@lists.linux.dev \
--cc=nathan@kernel.org \
--cc=torvalds@linux-foundation.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 NNTP newsgroup(s).