Skip site navigation (1)Skip section navigation (2)
Date:      Mon, 26 Sep 2016 21:38:51 -0700
From:      Mark Millard <markmi@dsl-only.net>
To:        svn-ports-head@freebsd.org, Steve Wills <swills@freebsd.org>
Subject:   Re: svn commit: r421598 - head/devel/powerpc64-gcc [breaks buildworld crossbuild for stable/11 -r306344]
Message-ID:  <BA31688D-E087-44A7-AE7E-A7C454F08DBD@dsl-only.net>

next in thread | raw e-mail | index | archive | help
I've submitted bugzilla report 213014 for -r421598 blocking buildworld =
via powerpc-gcc for stable/11 -r306344 and that reverting to =
devel/powerpc64-gcc -r413189 not having the problem.

[The submittal is basically the material that I sent to some lists =
first.]

The actual error that the -r421598 based buildworld stops with is:

> iostream.cpp:(.text.startup+0x1c): call to =
`std::__1::ios_base::Init::Init()' lacks nop, can't restore toc; =
recompile with -fPIC

Not exactly obvious what is going on or why libc++ use would make such a =
difference.



Note: This was an amd64 -> powerpc64 cross build. [It will be a while =
before I've access to the powerpc64's again so I've no native test of =
this issue.]

Note: This was my first use of -r421598 after updating /usr/ports to =
pick it up and I've not tried any other specific FreeBSD variants for =
buildworld/buildkernel. The problem is not likely to be -r306344 of =
stable/11 specific but it is what I tested.

Note: I'd separately reverted devel/binutils and =
devel/powerpc64-binutils to avoid 2.27 --which fails to produce useful =
file according to a couple of folks reports for targeting powerpc64 with =
them mixed with various gcc/g++ versions not working.

=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?BA31688D-E087-44A7-AE7E-A7C454F08DBD>