Skip site navigation (1)Skip section navigation (2)
Date:      Fri, 27 May 2016 14:56:15 -0700
From:      Mark Millard <markmi@dsl-only.net>
To:        Dimitry Andric <dim@FreeBSD.org>
Cc:        FreeBSD Toolchain <freebsd-toolchain@freebsd.org>, FreeBSD PowerPC ML <freebsd-ppc@freebsd.org>, freebsd-ports@freebsd.org
Subject:   Re: 11.0-CURRENT -r300770 libc++ update vs. lang/powerpc64-xtoolchain-gcc: no go [self hosted powerpc64 context]
Message-ID:  <C5678741-F12B-4234-A194-AC2F0B0CDAB4@dsl-only.net>
In-Reply-To: <8FAD594D-4349-4EA7-A712-D3792537FB1D@FreeBSD.org>
References:  <95E2A9D6-8E1A-46FB-84FF-60927A6F1CE4@dsl-only.net> <8FAD594D-4349-4EA7-A712-D3792537FB1D@FreeBSD.org>

next in thread | previous in thread | raw e-mail | index | archive | help
On 2016-May-27, at 1:50 PM, Dimitry Andric <dim at FreeBSD.org> wrote:
>=20
> On 27 May 2016, at 01:53, Mark Millard <markmi at dsl-only.net> wrote:
>>=20
>> I do buildworld/buildkernel on a powerpc64 targeting itself via =
lang/powerpc64-xtoolchain-gcc (a.k.a. lang/powerpc64-gcc for the most =
part). [Getting that lang/powerpc64-gcc installed for self-hosted use =
does take some work-around activity.] I have buildworld build clang (but =
not use it). [I've been doing this with 11.0-CURRENT for a long time.]
>>=20
>> Actually I use lang/gcc49 as the "system compiler" and =
lang/powerpc64-gcc as the self-hosting so-called "cross compiler". (I =
later list the src.conf content.) gcc4.2.1 is not installed.
>>=20
>> Trying to go from:
>>=20
>>> # uname -apKU
>>> FreeBSD FBSDG5C0 11.0-CURRENT FreeBSD 11.0-CURRENT #36 r300531M: Mon =
May 23 20:13:52 PDT 2016     =
root@FBSDG5C0:/usr/obj/xtoolchain/powerpc.powerpc64/usr/src/sys/GENERIC64v=
tsc-NODEBUG  powerpc powerpc64 1100111 1100111
>>=20
>> (for which -r300531 built and installed fine this way) to -r300777 =
now fails with errors such as:
>>=20
>>> --- lib/libc++__L ---
>>> In file included from =
/usr/src/lib/libc++/../../contrib/libc++/include/iterator:346:0,
>>>                from =
/usr/src/lib/libc++/../../contrib/libc++/include/memory:606,
>>>                from =
/usr/src/lib/libc++/../../contrib/libc++/include/algorithm:628,
>>>                from =
/usr/src/lib/libc++/../../contrib/libc++/src/algorithm.cpp:10:
>>> /usr/src/lib/libc++/../../contrib/libc++/include/iosfwd:176:14: =
error: 'mbstate_t' was not declared in this scope
>>> typedef fpos<mbstate_t>    streampos;
>>>             ^
>=20
> This is hopefully fixed by r300873 now.  Can you please verify?
>=20
> -Dimitry

buildworld/buildkernel started, based on -r300875 for powerpc64 under/on =
powerpc64 FreeBSD via lang/powerpc-xtoolchain-gcc as the so-called =
"cross compiler". If it completes successfully it takes about 8 hours =
for what I normally include in such builds.

I've also started a clang-based buildworld for powerpc (non-64) under =
powerpc FreeBSD as a cross check. (This environment involves work =
arounds, such as changes to signal delivery to avoid clang's code =
generation ABI violations in its stack handling. A clang based =
buildkernel would not complete so I would use a separate gcc 4.2.1 =
kernel build to get an overall system.)

=3D=3D=3D
Mark Millard
markmi at dsl-only.net




Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?C5678741-F12B-4234-A194-AC2F0B0CDAB4>