Re: Building world with clang ToT

On 2012-09-13 11:27, Edward Meewis wrote:
...
> FWIW: The clang build finished too, but with two hick-ups:
> 1. - kdump: build reports 4 errors:
>
> ===> usr.bin/kdump (depend)
> sh /usr/home/emeewis/contrib/FreeBSD-HEAD/usr.bin/kdump/mksubr
> /usr/obj/usr/home/emeewis/contrib/FreeBSD-HEAD/tmp/usr/include >kdump_subr.c
> env MACHINE=amd64 CPP="cpp"  sh
> /usr/home/emeewis/contrib/FreeBSD-HEAD/usr.bin/kdump/mkioctls print
> /usr/obj/usr/home/emeewis/contrib/FreeBSD-HEAD/tmp/usr/include > ioctl.c
> <stdin>:8:31: error: cam/scsi/scsi_enc.h: No such file or directory
> <stdin>:17:33: error: dev/filemon/filemon.h: No such file or directory
> <stdin>:35:33: error: fs/nandfs/nandfs_fs.h: No such file or directory
> <stdin>:46:24: error: net/netmap.h: No such file or directory
>
> (As a consequence ?) clang doesn't pick up 2 symbols: MFI_CMD32 and
> MFIIO_PASSTHRU32 which are defined if COMPAT_FREEBSD32 is set in
> sys/dev/mfi/mfi_ioctl.h

I don't think this has anything to do with clang, since you can see
CPP="cpp" in that command line, which usually is GNU cpp.  For clang,
you should set CPP=clang-cpp instead.

What seems to be happening is that certain headers it expects are not
install in ${DESTDIR}, which should be ${WORLDTMP} during buildworld.

It is possible that due to all the WITHOUT_ options you have defined,
some of those headers may not be installed.


> 2. lint calls tmp/usr/cc directly:
>
> buildworld-clang.log:===> usr.bin/xlint/llib (all)
> buildworld-clang.log:lint -cghapbx -Cposix
> /usr/home/emeewis/contrib/FreeBSD-HEAD/usr.bin/xlint/llib/llib-lposix
> buildworld-clang.log:lint: cannot exec
> /usr/obj/usr/home/emeewis/contrib/FreeBSD-HEAD/tmp/usr/bin/cc: No such
> file or directory
> buildworld-clang.log:Stop in
> /usr/home/emeewis/contrib/FreeBSD-HEAD/usr.bin/xlint/llib.
>
> A link from cc to clang in the same directory fixes that.

Yes, that is a known problem in lint, but I have no great urge to fix
it.  IMHO lint should be axed, the program is simply obsolete.