svn commit: r232074 - head/sys/cam/ctl

[Pawel Worach]

On Feb 24, 2012, at 12:09, Dimitry Andric wrote:
> On 2012-02-24 10:38, Alexander Best wrote:
>> is the clang version in base able to do complete universe builds for i386 and
>> amd64 without the need for NO_WERROR= and WERROR= now?
> 
> "universe" means all arches, and all kernel configs, so no.  The status
> for head with clang is as follows:
> 
> - buildworld with default options, e.g. no WITH_XXX or WITHOUT_XXX
>  settings, will complete without any (fatal) warnings.
> - buildkernel of the default GENERIC config still has one warning left,
>  in sys/dev/mps/mps_sas.c.  It should be simple to fix, but I'm
>  checking it with Ken first.
> - The LINT kernel configs probably have many warnings left.  I haven't
>  tested those extensively.
> 
> As soon as world & kernel compile without warnings, I'd like to have a
> tinderbox that continually builds with clang.  So head won't be
> regressing any more. :)
> 
> 
>> ps: are there any plans to add support for compiling kernel+userland with clang
>> tot? maybe this can be accomplished by doing something like
>> 
>> echo "WITH_CLANG_TOT=yes" >> /etc/src.conf
> 
> I'm not working on this at the moment.  Pawel Worach (CC'd) has a
> buildbot setup that builds FreeBSD daily with clang ToT.  Apparently
> just a few patches are needed.

You will find all the patches and hacks to build FreeBSD with llvm/clang trunk here:
http://llvm-amd64.freebsd.your.org/patches/

clang-*.diff contains the FreeBSD local changes, -fformat-extensions and worldtmp prefix stuff.
freebsd-*.diff contains the patches for FreeBSD to fix/disable -Werror warnings found by clang trunk
and needed hacks to the build infrastructure to use an out-of-tree compiler.

Just set CC and CXX to the *full path* of your custom version of clang.

>> which will turn all -Wformat-invalid-specifier and -Wformat-extra-args errors
>> into warnings (because clang tot doesn't support -fformat-extensions)?
> 
> It would be better to push our format extensions upstream, I think.
> Though the option should probably be renamed to something else, e.g.
> -ffreebsd-extensions, or such.

-- 
Pawel