Date: Tue, 28 Jun 2016 12:50:01 -0700 From: Bryan Drewery <bdrewery@FreeBSD.org> To: Jukka Ukkonen <jau789@gmail.com>, Justin Hibbits <jrh29@alumni.cwru.edu> Cc: FreeBSD PowerPC ML <freebsd-ppc@freebsd.org>, current@FreeBSD.org Subject: Re: Compiler dependent problems again on ppc64 Message-ID: <a050f381-175d-ef91-fcca-46726a390ffd@FreeBSD.org> In-Reply-To: <993E1F7C-F18B-42A7-BA08-9A815B1A7CD3@gmail.com> References: <3de3c40b-4edc-327e-f262-26230c7a3b12@gmail.com> <CAHSQbTAcPakERBjU=afc6Bx_6pzxG0zs24rWGwXR5YFO155icQ@mail.gmail.com> <993E1F7C-F18B-42A7-BA08-9A815B1A7CD3@gmail.com>
next in thread | previous in thread | raw e-mail | index | archive | help
This is an OpenPGP/MIME signed message (RFC 4880 and 3156) --gTgU3XgDplqJVwpBTuoDTkRdSXIbkbIbu Content-Type: multipart/mixed; boundary="tqFARMMNlA5nOUK8puqmmL71n6OP8FVBN" From: Bryan Drewery <bdrewery@FreeBSD.org> To: Jukka Ukkonen <jau789@gmail.com>, Justin Hibbits <jrh29@alumni.cwru.edu> Cc: FreeBSD PowerPC ML <freebsd-ppc@freebsd.org>, current@FreeBSD.org Message-ID: <a050f381-175d-ef91-fcca-46726a390ffd@FreeBSD.org> Subject: Re: Compiler dependent problems again on ppc64 References: <3de3c40b-4edc-327e-f262-26230c7a3b12@gmail.com> <CAHSQbTAcPakERBjU=afc6Bx_6pzxG0zs24rWGwXR5YFO155icQ@mail.gmail.com> <993E1F7C-F18B-42A7-BA08-9A815B1A7CD3@gmail.com> In-Reply-To: <993E1F7C-F18B-42A7-BA08-9A815B1A7CD3@gmail.com> --tqFARMMNlA5nOUK8puqmmL71n6OP8FVBN Content-Type: text/plain; charset=windows-1252 Content-Transfer-Encoding: quoted-printable It's probably the switch to WITH_SYSTEM_COMPILER, which is confusing the logic to think a newer external compiler is being used. This problem will likely creep up on any platform using GCC 4.2 in base that meets the WITH_SYSTEM_COMPILER test. Try this patch please: https://people.freebsd.org/~bdrewery/patches/ppc-system-compiler-std-c++1= 1.diff On 6/28/2016 12:43 PM, Jukka Ukkonen wrote: >=20 > The last version I tried was current pulled from svn today > only a few hours ago. I guess around 16:00 GMT today is > the best estimate I can give right now. The system on > which I did the test is already powered down. I can check > the exact svn release number tomorrow, though. > The latest successful rebuild I have done was on the 19th. > After that I tried a new rebuild only yesterday morning, and > then it suddenly failed. >=20 > --jau >=20 >=20 >> On 28 Jun 2016, at 21:14, Justin Hibbits <jrh29@alumni.cwru.edu> wrote= : >> >>> On Tue, Jun 28, 2016 at 12:34 PM, Jukka A. Ukkonen <jau789@gmail.com>= wrote: >>> >>> Hello all, >>> >>> It seems there is yet another compiler dependent problem on >>> ppc64. Most likely the same problem applies to all platforms >>> using the old gcc as the default compiler. >>> When trying to build gnu/lib/libstdc++ the compiler seems to >>> get the option -std=3Dc++11. The gcc complains about this and >>> the build gets invariably broken at that point. This has now >>> been going on for two days or so. This makes me believe nobody >>> is actively running rebuilds of the latest current on any gcc >>> based platform. >>> >>> --jau >> >> Which revision are you using? This should've been fixed a couple >> weeks ago. Adding Bryan Drewery, who made the fix. >> >> - Justin --=20 Regards, Bryan Drewery --tqFARMMNlA5nOUK8puqmmL71n6OP8FVBN-- --gTgU3XgDplqJVwpBTuoDTkRdSXIbkbIbu Content-Type: application/pgp-signature; name="signature.asc" Content-Description: OpenPGP digital signature Content-Disposition: attachment; filename="signature.asc" -----BEGIN PGP SIGNATURE----- Version: GnuPG v2 iQEcBAEBAgAGBQJXctTpAAoJEDXXcbtuRpfP7EUH/0u6aCnTkuvaWlaZh2XX+dZe hkogtMOI5wsP3IM0PeM+NLsQMiw0Ko09Nbuz+u53bUYDs+u09wRoKTlhyDL6rwuR Wdjupu1Z5cTCzhLVdDbazIXj9EE2tPyTGP0HXEMNTw6OMGZ1WvwDw+xvJ/Km0Pqc y8K5f/TJBEP3fJq/MWbSWLjCIy9c9ZJi2Q0rA9WqfBILHFa0RhBcXPS9AAdDwjTz 7oYMRJXyvMaFmM3dsWNTiazAsxCHKVdkyCmmHe8IP0VkZuPSRxiQydMYPXHitfhT 56RvAb0JtCpW6xHxemp/jjwLDcIHZMsdYFK/M8e5HgimCStSVUoUZjxSVzJJpeU= =9ReS -----END PGP SIGNATURE----- --gTgU3XgDplqJVwpBTuoDTkRdSXIbkbIbu--
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?a050f381-175d-ef91-fcca-46726a390ffd>