[Bug target/89203] Linux S/390: Unable to build GCC 8.2.0 on Red Hat Enterprise Linux Server release 6.9

2019-02-27 Thread m.marko08154711 at gmail dot com
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=89203

Martin Marko  changed:

   What|Removed |Added

 Status|NEW |RESOLVED
 Resolution|--- |DUPLICATE

--- Comment #4 from Martin Marko  ---
Awesome!

This patch was indeed solving this issue of building.

Just an additional note: we do not use the DTS version as we apply some custom
patches as well.

I changing the issue state to resolved/duplicate in favor to #89361, which is
more specific.

Thank you so much for your help on this one.

*** This bug has been marked as a duplicate of bug 89361 ***

[Bug target/89203] Linux S/390: Unable to build GCC 8.2.0 on Red Hat Enterprise Linux Server release 6.9

2019-02-27 Thread krebbel at gcc dot gnu.org
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=89203

Andreas Krebbel  changed:

   What|Removed |Added

 Status|UNCONFIRMED |NEW
   Last reconfirmed||2019-02-27
 Ever confirmed|0   |1

--- Comment #3 from Andreas Krebbel  ---
I can confirm that this is caused by PR89361 as Jakub mentioned. With the fix
libgomp configures successfully with GCC 8 branch.

Would it be possible for you to just use GCC 8 from DTS?

Jakub: Could you please apply the patch also to GCC 8 branch?

[Bug target/89203] Linux S/390: Unable to build GCC 8.2.0 on Red Hat Enterprise Linux Server release 6.9

2019-02-27 Thread jakub at gcc dot gnu.org
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=89203

Jakub Jelinek  changed:

   What|Removed |Added

 CC||jakub at gcc dot gnu.org

--- Comment #2 from Jakub Jelinek  ---
This is likely PR89361.  As a workaround, just build a recent binutils first
(or use one from DTS) and build against that.

[Bug target/89203] Linux S/390: Unable to build GCC 8.2.0 on Red Hat Enterprise Linux Server release 6.9

2019-02-27 Thread m.marko08154711 at gmail dot com
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=89203

Martin Marko  changed:

   What|Removed |Added

Version|8.2.0   |8.3.0

--- Comment #1 from Martin Marko  ---
Tried it again with GCC 8.3.0, still the same error.
Sry for pushing but is it possible to get a patch/workaround in the near future
as this is currently blocking us to update to C++17?
Thanks a lot for any help.