Is running a buildworld harder these days?

Juan Ramón Molina Menor listjm at club-internet.fr
Mon Mar 30 12:18:34 UTC 2015


 >
 > 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 at 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>
 > >          ^

There is a problem report for this issue:
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=194899


More information about the freebsd-questions mailing list