Upgrade messed up - cannot make buildworld from 11.0-RELEASE

Eduardo Lemos de Sa eduardo.lemosdesa at gmail.com
Mon Jul 9 20:14:44 UTC 2018


Dear Jon

On Mon, Jul 9, 2018 at 9:11 AM Jon Theil Nielsen <jontheil at gmail.com> wrote:

> Somehow I messed up an upgrade from 11.1-RELEASE to 11.2-RELEASE.
>
> I can only boot into an old 11.0 kernel in single user mode. uname -a:
>
> FreeBSD  11.0-RELEASE-p8 FreeBSD 11.0-RELEASE-p8 #0: Wed Feb 22 06:12:04
> UTC 2017
>
> I'm not able to run make buildworld from a 11.1-RELEASE source tree. The
> first error was a missing include/__undef_min_max which I had to copy
> manyally:
>
> cp /usr/src/contrib/libc++/include/__undef_min_max /usr/include/c++/v1/
>
> Now I'm getting new errors like
>
> /usr/include/c++/v1/__split_buffer:13:1: error: unknown type name
> '_LIBCPP_PUSH_MACROS'
>
> and
>
> sr/include/c++/v1/__split_buffer:17:1: error: expected unqualified-id.
>
> Can anyone suggest a solution?
>
> Thanks in advance
>
> Jon Theil Nielsen
> --
> Jon Theil Nielsen
>
> I am sorry to cannot help you: I experienced the same problems you
described: I tried to upgrade from 11-Release-p11 to 11.2 doing:

svn co svn://svn.FreeBSD.org/base/releng/11.2  /usr/src > & system-11.2.log
or
svn co svn://svn.FreeBSD.org/base/stable/11  /usr/src > & system-stable.log

or

svnlite up /usr/src

After 3 tries, I could have the system compiled (if I use maje -j 6
directive to compile, I got error: this worked only in a serial 1-proc
process)

but there was a kernel panic followed of cycling reboot process.

I work around removing the whole /usr/src and /usr/obj, recreating them,
and fetching 11.1 sources:

svnlite up /usr/src

I did not need to start in a single-user mode: I just pressed 5 (to load a
non-default kernel) and chose old-kernel. Booting using old-kernel (11.1) I
could rebuild the userland. After this, I gave up to run 11.2-RELEASE.

In time, my uname -a returns:
FreeBSD matata 11.1-RELEASE-p11 FreeBSD 11.1-RELEASE-p11 #0 r335864: Mon
Jul  2 14:44:51 -03 2018     root at matata:/usr/obj/usr/src/sys/GENERIC  amd64

I was thinking that this problem happened only with me, but now I see other
people that can have the situition

Cheers

Eduardo




-- 
Eduardo Lemos de Sa
Professor Titular
Dep. Quimica da Universidade Federal do Paraná
fone: +55(41)3361-3300
fax:   +55(41)3361-3186


More information about the freebsd-questions mailing list