Date: Mon, 05 Mar 2012 19:43:13 +0100 From: "O. Hartmann" <ohartman@zedat.fu-berlin.de> To: Dimitry Andric <dim@FreeBSD.org> Cc: Pegasus Mc Cleaft <ken@mthelicon.com>, freebsd-current@freebsd.org Subject: Re: CLANG buildworld failure: lint: cannot exec /usr/obj/usr/src/tmp/usr/bin/cc: No such file or directory Message-ID: <4F550941.6030102@zedat.fu-berlin.de> In-Reply-To: <4F546F37.70404@FreeBSD.org> References: <4F536D41.1030302@zedat.fu-berlin.de> <201203041628.q24GS12l088270@pozo.com> <201203041751.02531.ken@mthelicon.com> <4F53D1D3.2010607@zedat.fu-berlin.de> <4F53E2C3.7090102@FreeBSD.org> <4F53FD57.303@zedat.fu-berlin.de> <4F546F37.70404@FreeBSD.org>
next in thread | previous in thread | raw e-mail | index | archive | help
This is an OpenPGP/MIME signed message (RFC 2440 and 3156) --------------enigB569EEE18D25ADE3ED4D2879 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable On 03/05/12 08:45, Dimitry Andric wrote: > On 2012-03-05 00:40, O. Hartmann wrote: > ... >> All right, my /etc/src.conf looks like this now (as it does before): >> >> WITH_CLANG=3D YES >> WITH_CLANG_EXTRAS=3D YES >> # >> WITH_BIND_LIBS=3D YES >> WITH_BIND_SIGCHASE=3D YES >> WITH_BIND_LARGE_FILE=3D YES >> # >> WITH_IDEA=3D YES >> WITH_HESIOD=3D YES >> # >> #WITH_ICONV=3D YES >> #WITH_BSD_GREP=3D YES >> # >> WITH_LIBCPLUSPLUS=3D YES >> # >> #WITH_OFED=3D YES >> >> When cc is now clang, c++ is now clang++, what effect do have >> CFLAGS.cc=3D"blablabla" and CFLAGS.clang=3D"blabla"? >=20 > None. These variables are not part of the build system. They are just= > a suggestion posted by people on the mailing list. You must still use = a > statement somewhere that adds one of the variables to the "real" CFLAGS= , > and that statement will need knowledge about what "cc" is. >=20 > Note, I would suggest using the names CFLAGS.gcc and CFLAGS.clang > instead. Ah, I see. Sorry for the noise. I picked up the thread and thought this might be a fact by now. NAd yes, I'd rather follow your suggestion, it makes things more clear. >=20 >=20 >> If the binary "cc" after this treatment is in reality "clang", then >> logic implies that equality exists: >> CFLAGS.cc =3D CFLAGS.clang =3D "blabla" >=20 > See above. >=20 >=20 >> What should /etc/make.conf contain not to confuse settings in >> /etc/src.conf? >=20 > I'm not sure what you mean with "confuse"? The settings in make.conf > are read earlier than those in src.conf, so the latter can override the= > former. >=20 > Also, the settings in make.conf are *always* read, even if you are usin= g > a non-BSD Makefile (one that doesn't contain .include <bsd.prog.mk> or > similar at the end). >=20 >=20 > ... >>>> clang: warning: argument unused during compilation: '-std=3Dgnu99' >>>> strfile.o: In function `main': >>>> /usr/src/games/fortune/strfile/strfile.c:(.text+0x2e0): undefined >>>> reference to `_ThreadRuneLocale' >>> >>> This is unrelated to the 'cc' problem, but I suggest deleting /usr/ob= j/* >>> and starting the build from scratch. >>> >> >> >> Before I start "make buildworld", I always delete the content of >> /usr/obj/*, so there are never remains aof anything left behinf from >> earlier compiles. >> >> You're right, this is at the first sight unrelated to the cc issue and= >> should be treated separetely. >=20 > I have compiled multiple worlds now from the latest trunk, with both gc= c > and clang, but I have not been able to reproduce your errors yet. Since yesterday/today's night, I'm also able to compile again the system.= The solution is obscure and a kind of "hoodovoodo" (at least for me). I "updated" backwards the sources via "svn -r 232496 update", then again a simple "make update" in /usr/src. After this procedure the problem vanished. I have no idea what's wrong. Since I thought I might have destroyed my OS by accidentaly interrupting the installation of libc once, were a similar error occured but in another context, I think I'm rather better deleting the /usr/src and doing again an checkout. Something seems very fishy ... Regards, Oliver --------------enigB569EEE18D25ADE3ED4D2879 Content-Type: application/pgp-signature; name="signature.asc" Content-Description: OpenPGP digital signature Content-Disposition: attachment; filename="signature.asc" -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.18 (FreeBSD) iQEcBAEBAgAGBQJPVQlHAAoJEOgBcD7A/5N8YqQH/jBkL+W0ru7MG32QviXp0vAz sSIts+Toezg5x1/rf+2UuLWna8pWNBhfDLdzdZOyj2Dy4lIsPq2IKsHj/1g+D0h5 si0D5rHb33HNhtWMMcB8vFsr1okKvbLFpr9Qkh7TYo5EQ5F/YHR+NSUISLCUDRQ2 N6QHNZa4FuKcDWGCHSnO5m3dHOQtsa6B62nKSG/U4EIU1jXkD/lycqUnZxVzKlFL iF2YX13pKavE+Zjlr0YUgO7HU/KUdFxBwGlPzXMMP4GgFkjjxnpR24i904kfoq1Z I1w1kisadCEnTZyTbK15zqZQyFkvGFfIspifnh9ZToz6e2Kki5jBDU2Ky4HZ6rw= =qA6Q -----END PGP SIGNATURE----- --------------enigB569EEE18D25ADE3ED4D2879--
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?4F550941.6030102>