Re: Recent -CURRENT unable to build numerous ports

On 22 Oct 2016, at 06:47, Aryeh Friedman <aryeh.friedman_at_gmail.com> wrote:
> 
>> This was a side-effect of r307676, which added transformation rules for
>> .bco and .llo files (LLVM bytecode in binary and text representation).
>> 
>> Because .SUFFIXES was not updated to match, bmake was actually trying to
>> build a ".c.bco" file in the above case...
>> 
>> I committed a fix in r307754.
>> 
>> 
> Still doesn't work and still corrupts the base system (see output after
> portmaster failure) on a fresh from CD install of 11-STABLE (post svlite of
> /usr/src and make DESTDIR=/ world kernel):
> 
> root_at_lilith:/usr/src # uname -a
> FreeBSD lilith 10.3-STABLE FreeBSD 10.3-STABLE #0 r307759: Sat Oct 22
> 00:14:55 EDT 2016     aryehl_at_lilith:/usr/obj/usr/src/sys/GENERIC  amd64

You said that you have a fresh install of 11-STABLE, but this shows
10.3-STABLE?  What is it?


> ===>   Registering installation for gettext-runtime-0.19.8.1
> pkg-static: Unable to access file
> /usr/ports/devel/gettext-runtime/work/stage/usr/local/include/autosprintf.h:
> No such file or directory
> pkg-static: Unable to access file
> /usr/ports/devel/gettext-runtime/work/stage/usr/local/lib/libasprintf.a: No
> such file or directory
> pkg-static: Unable to access file
> /usr/ports/devel/gettext-runtime/work/stage/usr/local/lib/libasprintf.so:
> No such file or directory
> pkg-static: Unable to access file
> /usr/ports/devel/gettext-runtime/work/stage/usr/local/lib/libasprintf.so.0:
> No such file or directory
> pkg-static: Unable to access file
> /usr/ports/devel/gettext-runtime/work/stage/usr/local/lib/libasprintf.so.0.0.0:
> No such file or directory
> *** Error code 74

This has nothing to do with the fix I checked in.  It seems more like
packaging problem in the gettext port, or some problem on your system.

Maybe you can try cleaning the port, making sure the work directory is
gone, then build it again.



> root_at_lilith:/usr/ports # cd /usr/src
> root_at_lilith:/usr/src # make DESTDIR=/ world kernel;

Don't do this.  IMHO the "world" target should be removed, as it is too
easy to shoot yourself in the foot with it.

The correct way to do a source-based upgrade is:
* make buildworld
* make buildkernel
* make installkernel
* reboot in single user
* etcupdate -p
* make installworld
* etcupdate
* reboot


> --------------------------------------------------------------
>>>> stage 1.1: legacy release compatibility shims
> --------------------------------------------------------------
> cd /usr/src; MAKEOBJDIRPREFIX=/usr/obj/usr/src/tmp  INSTALL="sh
> /usr/src/tools/install.sh"
> PATH=/usr/obj/usr/src/tmp/legacy/usr/sbin:/usr/obj/usr/src/tmp/legacy/usr/bin:/usr/obj/usr/src/tmp/legacy/usr/games:/usr/obj/usr/src/tmp/legacy/bin:/sbin:/bin:/usr/sbin:/usr/bin
> WORLDTMP=/usr/obj/usr/src/tmp  VERSION="FreeBSD 10.3-STABLE amd64 1003509"

Here is the discrepancy again, if this is 11-STABLE, why does it show
10.3-STABLE here?


> c++  -O2 -pipe
> -I/usr/src/lib/clang/libllvmsupport/../../../contrib/llvm/include
> -I/usr/src/lib/clang/libllvmsupport/../../../contrib/llvm/tools/clang/include
> -I/usr/src/lib/clang/libllvmsupport/../../../contrib/llvm/lib/Support -I.
> -I/usr/src/lib/clang/libllvmsupport/../../../contrib/llvm/../../lib/clang/include
> -DLLVM_ON_UNIX -DLLVM_ON_FREEBSD -D__STDC_LIMIT_MACROS
> -D__STDC_CONSTANT_MACROS -DNDEBUG -fno-strict-aliasing
> -DLLVM_DEFAULT_TARGET_TRIPLE=\"x86_64-unknown-freebsd10.3\"
> -DLLVM_HOST_TRIPLE=\"x86_64-unknown-freebsd10.3\" -DDEFAULT_SYSROOT=\"\"

And here the target and host are both 10.3.  What gives?


> /usr/src/lib/clang/libllvmsupport/../../../contrib/llvm/include/llvm/Support/AlignOf.h:19:
> /usr/include/c++/v1/cstddef:58:30: error: redefinition of 'nullptr_t'
> struct _LIBCPP_TYPE_VIS_ONLY nullptr_t
>                             ^
> /usr/include/c++/v1/__nullptr:24:30: note: previous definition is here
> struct _LIBCPP_TYPE_VIS_ONLY nullptr_t
>                             ^

It looks like you might have partially installed an 11-STABLE userland,
and now are trying to build a 10-STABLE world?  I am not sure if that
is supposed to work.

If your system is rather hosed, as I think it is, it might be easier to
just reinstall directly from the 11.0-RELEASE ISOs.  Then you can try
building 11-STABLE again.

-Dimitry