llvm boostrap? Clang failures.
Jeffrey Bouquet
jbtakk at iherebuywisely.com
Fri Jul 10 19:13:02 UTC 2015
On Fri, 10 Jul 2015 14:50:22 +0200, Dimitry Andric <dim at FreeBSD.org> wrote:
> On 10 Jul 2015, at 03:54, Jeffrey Bouquet <jbtakk at iherebuywisely.com> wrote:
> >
> > The "update clang" messages in UPDATING seem to not fix...
> > ...llvm/include/llvm/ADT/StringRef.h: fatal error:
> > 'algorithm' file not found
> > make stopped in /usr/src/lib/clang/lib/libllvmsupport...
>
> Do you have the 'algorithm' file on your system, in /usr/include/c++/v1?
> And is the rest of libc++ correctly installed? You should have the
> following libraries:
>
> /usr/lib/libc++.a
> /usr/lib/libc++.so
> /usr/lib/libc++.so.1
> /usr/lib/libc++_p.a
Were missing.
>
>
> > The entire build fails similarly,
> > also in any subtree I try to start from (clang, lib/clang... etc etc)
> >
> > Previously, the system was upgraded from another successful installworld by rsync'ing the
> > /obj IIRC...
> > Also I've tried parameters such as CPP=/usr/local/bin/clang-cpp36 to no avail...
>
> Another possibility is that you are assigning to CFLAGS and/or CXXFLAGS
> incorrectly. Can you please post your make.conf and src.conf files?
>
> Last but not least, from which version of FreeBSD are you building? An
> older copy of -CURRENT, or some -STABLE branch?
>
> -Dimitry
make CC=/usr/local/bin/clang36 CXX=/usr/local/bin/clang++36 CPP=/usr/local/bin/clang-cpp36 -NO_PROFILE
-DALWAYS_CHECK_MAKE -DNOPROFILE buildworld...
Fails in the same way.
Aside from rsync'ing over from another CURRENT that buildworld works on, which may happen soon,
for an installworld, I wonder why some invocation of the above line, or one with gcc49, would not
suffice...
[ Tried several things in UPDATING and 'man build', but since even
/usr/bin/clang here is missing [1], things are not what they should be,
everything except buildworld works... ]
[1] I may be able to copy it over today using a thumbdrive, however...
Sorry to waste anyone's time. This problem is of low priority here... but thanks to
the replies, appears to be solvable sooner than later.
More information about the freebsd-current
mailing list