Re: command line environment and port to equal CURRENT clang?

From: Jeffrey Bouquet <jbtakk_at_iherebuywisely.com>
Date: Mon, 23 Jan 2017 17:02:45 -0800 (PST)
On Mon, 23 Jan 2017 20:18:18 +0100, Dimitry Andric <dim_at_FreeBSD.org> wrote:

> On 23 Jan 2017, at 05:32, Jeffrey Bouquet <jbtakk_at_iherebuywisely.com> wrote:
> > 
> > ... that may work in /usr/src/sbin for example?
> > make clang=[/usr/ports/lang/??]clang-foo clang+ depend;   make;   # so that a buildworld is not needed?
> > or that would have to be created as a feature..
> 
> The following appears to work:
> 
> pkg install llvm39
> export CC=/usr/local/bin/clang39
> export CXX=/usr/local/bin/clang++39
> export CPP=/usr/local/bin/clang-cpp
> cd /usr/src/sbin
> make obj
> make depend
> make
> 
> Note that this may pick up the wrong versions of libraries, so do not
> be amazed if stuff blows up.
> 
> Also note that clang in base has a few patches which might not be in the
> port, so you could also run into unexpected bugs in the port.
> 
> -Dimitry

Works! on 9 out of ten binaries at least. [1] Even so good from here that someone
may wish to put it in /usr/src/UPDATING but with an additional reference to how
to find the most likely llvm since that may change over time...

Tested in /usr/src/bin, sbin, usr.sbin, usr.bin...

[1] some build but do not install 'no such file or directory' so maybe did not build...

Made it into a .sh or .zsh that placed in another location and then run from the
location that is being reinstalled, /fsck_ffs/ for example... with the latter
as the $1 coded into the script, as the full path on the command line as a
parameter.  May need improvement... or more coding...
Received on Tue Jan 24 2017 - 00:02:49 UTC

This archive was generated by hypermail 2.4.0 : Wed May 19 2021 - 11:41:09 UTC