From: David Laight <David.Laight@ACULAB.COM>
To: 'Nick Desaulniers' <ndesaulniers@google.com>,
Peter Zijlstra <peterz@infradead.org>
Cc: Nathan Chancellor <nathan@kernel.org>,
Masahiro Yamada <masahiroy@kernel.org>,
Michal Marek <michal.lkml@markovi.net>, X86 ML <x86@kernel.org>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
Linux Kbuild mailing list <linux-kbuild@vger.kernel.org>,
"llvm@lists.linux.dev" <llvm@lists.linux.dev>
Subject: RE: [PATCH] kbuild: Support clang-$ver builds
Date: Fri, 29 Oct 2021 08:56:32 +0000 [thread overview]
Message-ID: <65a89f36d36443af9b13c1b121731ef1@AcuMS.aculab.com> (raw)
In-Reply-To: <CAKwvOd=x9E=7WcCiieso-CDiiU-wMFcXL4W3V5j8dq7BL5QT+w@mail.gmail.com>
From: Nick Desaulniers
> Sent: 29 October 2021 00:28
...
> > > 2. Update the documentation to describe using the
> > >
> > > $ PATH=/usr/lib/llvm-#/bin:$PATH make LLVM=1 ...
> > >
> > > trick. This has been the preferred method for using different
> > > versions of LLVM but it has never been documented anywhere. This
> > > would allow us to keep the current build infrastructure while giving
> > > people clear instructions for how to handle different versions of
> > > clang. As Peter has noted, this would require people who are not
> > > familiar with building with LLVM to be constantly looking at the
> > > documentation to remember the command to invoke, whereas with
> > > LLVM=-#, it is easy to remember.
> >
> > Right, this is no more than a crude hack and is super unfriendly. It
> > should never have been accepted.
>
> Lots of tools modify PATH in your `.bashrc` or `.zshrc` etc. I don't
> see how that's any different, other than one off commands in which you
> actually intend to use a specific version.
Nothing should be modifying the default $PATH, either by hacking
my .bashrc or any system default files that get run first.
It is as horrid and broken as setting LD_LIBRARY_PATH.
Even ldconfig is pretty much a broken idea.
David
-
Registered Address Lakeside, Bramley Road, Mount Farm, Milton Keynes, MK1 1PT, UK
Registration No: 1397386 (Wales)
prev parent reply other threads:[~2021-10-29 8:56 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-10-28 13:43 Peter Zijlstra
2021-10-28 14:07 ` Masahiro Yamada
2021-10-28 14:15 ` Peter Zijlstra
2021-10-28 14:22 ` Peter Zijlstra
2021-10-28 15:03 ` Peter Zijlstra
2021-10-28 17:44 ` Nathan Chancellor
2021-10-28 20:48 ` Peter Zijlstra
2021-10-28 23:27 ` Nick Desaulniers
2021-10-29 8:54 ` Peter Zijlstra
2021-10-30 14:33 ` Peter Zijlstra
2021-10-31 1:18 ` Sedat Dilek
2021-10-31 12:38 ` Peter Zijlstra
2021-10-29 8:56 ` David Laight [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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=65a89f36d36443af9b13c1b121731ef1@AcuMS.aculab.com \
--to=david.laight@aculab.com \
--cc=linux-kbuild@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=llvm@lists.linux.dev \
--cc=masahiroy@kernel.org \
--cc=michal.lkml@markovi.net \
--cc=nathan@kernel.org \
--cc=ndesaulniers@google.com \
--cc=peterz@infradead.org \
--cc=x86@kernel.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
all inboxes | Powered by JetHome®