On 2012-03-24 16:52, Super Bisquit wrote:
> On Sat, Mar 24, 2012 at 10:08 AM, Dimitry Andric <d...@freebsd.org> wrote:
>> As of r233419 in head, you should now be able to build world and the
>> GENERIC kernel using clang, and without the need to place NO_WERROR=
>> and/or WERROR= in your src.conf file.
...
> Are the defaults for clang, llvm, and the related tools now in /usr/bin
> instead of /usr/local/bin?

I was talking about clang in base, not the port.  The port will
obviously keep on installing under /usr/local, or wherever your
LOCALBASE setting points to.

The default for base is to only build clang, clang-tblgen and tblgen,
and install those in /usr/bin.  If you want the additional tools such as
llc, opt, and others, you can use the WITH_CLANG_EXTRAS setting in
src.conf(5).  Currently, we don't install shared libraries for llvm and
clang.


> Are the versions at 3.x?

The version in head and stable/9 is currently the 3.0 release, with a
few small backports of post-3.0 fixes.

I will import a newer snapshot of the clang trunk into head soonish, but
I don't have an exact ETA yet.  This most likely will not be merged to
stable/9.


> Will building clang in /usr/src result in a 3.x build or will I need to
> edit the clang/Makefile and llvm/Makefile to install everything in /usr/bin
> without causing an error?

There's no need to edit, just building and installing world will do the
right thing.


> I've already reported the error to brooke@ but obviously:
> 1) Being on PowerPC it doesn't seem to get any responses.
> 2) Because the email was from me, it was ignored.

I assume you were talking about the port?  If so, the ports mailing list
is a better place to discuss it.

Also, clang on PowerPC is not yet ready for production.  Any help there
is appreciated, but it is better to go to the LLVM mailing lists and
Bugzilla directly.
_______________________________________________
freebsd-current@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-current
To unsubscribe, send any mail to "freebsd-current-unsubscr...@freebsd.org"

Reply via email to