Skip site navigation (1)Skip section navigation (2)
Date:      Mon, 30 Mar 2015 12:33:54 +0100
From:      krad <kraduk@gmail.com>
To:        FreeBSD Questions <freebsd-questions@freebsd.org>
Subject:   Re: Is running a buildworld harder these days?
Message-ID:  <CALfReydNn1ZpZwL%2BRXBXLLabcMXYWR6ooqoSNUGA8ggfsfhT8Q@mail.gmail.com>
In-Reply-To: <CALfReyeicMgXqwV753v0jYiAxxQbZjkY5RQUmYQveR%2BES18zhQ@mail.gmail.com>
References:  <CALfReyeicMgXqwV753v0jYiAxxQbZjkY5RQUmYQveR%2BES18zhQ@mail.gmail.com>

next in thread | previous in thread | raw e-mail | index | archive | help
hmm dropping the CC and CXX lines from my make file seems to have cured the
problem. Does running clang as "clang" vs "cc" make a difference to how it
works are is it a simple case of the command line getting to long ?

On 30 March 2015 at 12:07, krad <kraduk@gmail.com> wrote:

> Over the past 18 months or so I have had so many build issues when
> compiling world, which in the previous 10 years I didnt get unless I did
> something stupid. They are never the same, but mainly linking issues,
> or missing .h files. They also also seem to randomly clear themselves up.
>
> Currently I'm running the builds in a jail built from the 10.1 base
> tarball, with just bash and svnup installed, and no nullfs bits so pretty
> clean.
>
> Today I get the following with a make -j5 buildworld
>
> /usr/src/lib/libc/gen/cap_sandboxed.c:33:10: fatal error: 'sys/capsicum.h'
> file not found
> #include <sys/capsicum.h>
>          ^
> 1 error generated.
> /usr/src/lib/libc/../../sys/kern/subr_capability.c:45:10: fatal error:
> 'sys/capsicum.h' file not found
> #include <sys/capsicum.h>
>          ^
>
> [root@stable /usr/src]# find /usr/src/ -name capsicum.h -ls -exec sha256
> {} \;
>  74503       33 -rw-r--r--    1 root                             wheel
>                           15587 Mar 30 08:38 /usr/src/sys/sys/capsicum.h
> SHA256 (/usr/src/sys/sys/capsicum.h) =
> 39be88c0bb614f09fc3c517293cef339186611affbde3b0190d81a05ab7851c4
>
> I get the same with a straight "make buildworld"
>
>
> Is clang more picky than gcc? This has happened on multiple installs,
> including ones I have tried to keep as clean as possible
>
>
>
> # cat /etc/make.conf
> USA_RESIDENT=NO
> SVN_UPDATE=YES
> XFREE8pro_VERSION=      4
> KERNCONF=me
> KERNCONFDIR=/etc/kernel
> BOOT_COMCONSOLE_SPEED="115200"
> FETCH_BEFORE_ARGS=-p
>
> #DEBUG=-g
> LOADER_TFTP_SUPPORT=YES"
> LOADER_ZFS_SUPPORT=yes
> FTP_PASSIVE_MODE=1
>
> #MAKE_JOBS_NUMBER=5
> #MAKE_JOBS_NUMBER?=8
> WITH_CTF=1
> STRIP=
>
> CC=/usr/local/bin/clang35
> CXX=/usr/local/bin/clang++35
> CC=/usr/bin/clang
> CXX=/usr/bin/clang++
> #CC="/usr/local/libexec/ccache/world/cc"
> #CXX="/usr/local/libexec/ccache/world/c++"
> CCACHE_LOGFILE=/root/.ccache/log
>
> WITH_PKGNG=     yes
> PF_ENABLE_FILTER_RULES=yes
>
>
> # cat /etc/make.conf
> USA_RESIDENT=NO
> SVN_UPDATE=YES
> XFREE8pro_VERSION=      4
> KERNCONF=me
> KERNCONFDIR=/etc/kernel
> BOOT_COMCONSOLE_SPEED="115200"
> FETCH_BEFORE_ARGS=-p
>
> #DEBUG=-g
> LOADER_TFTP_SUPPORT=YES"
> LOADER_ZFS_SUPPORT=yes
> FTP_PASSIVE_MODE=1
>
> #MAKE_JOBS_NUMBER=5
> #MAKE_JOBS_NUMBER?=8
> WITH_CTF=1
> STRIP=
>
> CC=/usr/local/bin/clang35
> CXX=/usr/local/bin/clang++35
> CC=/usr/bin/clang
> CXX=/usr/bin/clang++
> #CC="/usr/local/libexec/ccache/world/cc"
> #CXX="/usr/local/libexec/ccache/world/c++"
> CCACHE_LOGFILE=/root/.ccache/log
>
> WITH_PKGNG=     yes
> PF_ENABLE_FILTER_RULES=yes
> [root@stable /usr/src]# cat /etc/src.conf
> WITHOUT_FREEBSD_UPDATE="yes"
> WITHOUT_GAMES="yes"
> WITHOUT_HTML="yes"
> WITHOUT_IPFILTER="yes"
> WITHOUT_IPFW="yes"
> WITHOUT_IPX="yes"
> WITHOUT_LIB32="YES"
> WITHOUT_PORTSNAP="YES"
> WITHOUT_ATM="YES"
> WITHOUT_BLUETOOTH=YES
> WITHOUT_BSNMP="YES"
> WITHOUT_SENDMAIL=YES
> WITHOUT_INFO=yes
> WITHOUT_AMD=yes
> WITH_UNBOUND=yes
>
>
> Is it just me, or are others seeing this?
>
>



Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?CALfReydNn1ZpZwL%2BRXBXLLabcMXYWR6ooqoSNUGA8ggfsfhT8Q>