1467153 - Builds with GCC 7 toolchain fail

Status: RESOLVED WONTFIX

(Firefox Build System :: General, enhancement)

Description

[Marco Castelluccio [:marco]]

Currently they fail at:
> [task 2018-06-06T14:43:20.864Z] 14:43:20     INFO -  TEST-UNEXPECTED-FAIL | check_stdcxx | We do not want these libstdc++ symbol versions to be used:
> [task 2018-06-06T14:43:20.864Z] 14:43:20     INFO -    _ZNSsC1ERKSsmRKSaIcE@GLIBCXX_3.4.23

Comment 1

[Nathan Froyd [:froydnj]]

That is:

std::basic_string<char, std::char_traits<char>, std::allocator<char> >::basic_string(std::basic_string<char, std::char_traits<char>, std::allocator<char> > const&, unsigned long, std::allocator<char> const&)

Which is a little weird, this constructor shouldn't normally be a problem.  Unless we can no longer use the old-abi basic_string?  Or is somebody using the new-abi one inadvertently?

Comment 2

[Marco Castelluccio [:marco]]

Maybe :glandium can help?

Comment 3

[Mike Hommey [:glandium] OoO until Jun 18]

Need something like what was removed in https://hg.mozilla.org/mozilla-central/rev/6803c5e3f34b , but for that function. That won't get you much further, though, because the resulting binaries will have a dependency on the GCC_7_0 symbol version from libgcc... that one I haven't looked into yet.

Comment 4

[Marco Castelluccio [:marco]]

We don't care about this anymore for code coverage builds, should we wontfix or do you want to keep this open?

Comment 5

[Mike Hommey [:glandium] OoO until Jun 18]

I guess we don't care anymore, since we're shipping with clang, and use libstdc++ 4.9. We might need to care if we end up using a more recent libstdc++ with clang, but until then...