Date: Mon, 7 Nov 2016 07:06:52 +0100 From: Ed Schouten <ed@nuxi.nl> To: Andrew Reilly <areilly@bigpond.net.au> Cc: svn-src-head@freebsd.org, "ed@FreeBSD.org" <ed@freebsd.org> Subject: Re: svn commit: r307227 - in head: include lib/libc/stdlib lib/libc/tests/stdlib Message-ID: <CABh_MKn%2BJNtwDLDL1mv5qXZSxLAFuPnWWcnjn80QKvXGoqUfdw@mail.gmail.com> In-Reply-To: <4F77ED5A-6B71-4AA5-BEC9-752A8BA349CE@bigpond.net.au> References: <B5ED025A-9F83-43A9-A379-639A4C013225@bigpond.net.au> <CABh_MKn4sYGM%2BZ5Td5-ZeAa4ckhwx_Ls9Sb6aBS=uO2kM8JDuQ@mail.gmail.com> <4F77ED5A-6B71-4AA5-BEC9-752A8BA349CE@bigpond.net.au>
next in thread | previous in thread | raw e-mail | index | archive | help
Hi Andrew, 2016-11-07 0:54 GMT+01:00 Andrew Reilly <areilly@bigpond.net.au>: > Thanks for pointing me back to src.conf. I added this when I was an =E2= =80=9Cearly adopter=E2=80=9D of clang, and it was necessary. I suspect tha= t now that we are all-clang all the time, this is redundant. Would this ha= ve overridden the system build process? > > my /etc/src.conf: > CC=3Dclang > CXX=3Dclang++ > CPP=3Dclang-cpp > WITH_LIBCPLUSPLUS=3Dyes That may very likely be the culprit, as it probably means you used the compiler binary of the host installation that uses /usr/include as its include path. Thanks for confirming! --=20 Ed Schouten <ed@nuxi.nl> Nuxi, 's-Hertogenbosch, the Netherlands KvK-nr.: 62051717
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?CABh_MKn%2BJNtwDLDL1mv5qXZSxLAFuPnWWcnjn80QKvXGoqUfdw>