From owner-freebsd-questions@FreeBSD.ORG Mon Mar 30 13:50:58 2015 Return-Path: Delivered-To: freebsd-questions@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [8.8.178.115]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id EFEC83C4 for ; Mon, 30 Mar 2015 13:50:58 +0000 (UTC) Received: from oslo.ath.cx (oslo.ath.cx [IPv6:2a01:4f8:200:42e4::1]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client CN "oslo.ath.cx", Issuer "oslo.ath.cx" (not verified)) by mx1.freebsd.org (Postfix) with ESMTPS id 571C82FD for ; Mon, 30 Mar 2015 13:50:57 +0000 (UTC) Received: by oslo.ath.cx (OpenSMTPD) with ESMTP id 78018f3e; Mon, 30 Mar 2015 15:50:55 +0200 (CEST) Date: Mon, 30 Mar 2015 15:50:55 +0200 From: "Herbert J. Skuhra" To: krad Subject: Re: Is running a buildworld harder these days? Message-ID: <20150330135055.GB38612@oslo.ath.cx> References: MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: User-Agent: Mutt/1.5.23 (2014-03-12) Cc: freebsd-questions@freebsd.org X-BeenThere: freebsd-questions@freebsd.org X-Mailman-Version: 2.1.18-1 Precedence: list List-Id: User questions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 30 Mar 2015 13:50:59 -0000 On Mon, Mar 30, 2015 at 12:07:28PM +0100, krad 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 > ^ > 1 error generated. > /usr/src/lib/libc/../../sys/kern/subr_capability.c:45:10: fatal error: > 'sys/capsicum.h' file not found > #include > ^ > > [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++ Try 'make buildworld SRCCONF=/dev/null __MAKE_CONF=/dev/null' or without setting CC/CXX! -- Herbert