libstdc++-5-dev:amd64 5.5.0-1ubuntu1 configured without _GLIBCXX_USE_C99

[Andrew Paxie]

Test program compiled on Artful Aardvark Ubuntu 17.10.

$ which g++-5
/usr/bin/g++-5

$ /usr/bin/g++-5 --version
g++-5 (Ubuntu 5.5.0-1ubuntu1) 5.4.1 20171010
Copyright (C) 2015 Free Software Foundation, Inc.
This is free software; see the source for copying conditions. There is NO
warranty; not even for MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE.

$ /usr/bin/g++-5 -std=c++11 -x c++ - <<EOF
#include <iostream>
#include <string>
int main()
{
  std::cout << std::to_string(0) << '\n';
  return 0;
}
EOF

Expected result

compile without errors, output 0

Actual result

<stdin>: In function ‘int main()’:
<stdin>:5:16: error: ‘to_string’ is not a member of ‘std’

Supposed cause

_GLIBCXX_USE_C99 is not set in
/usr/include/x86_64-linux-gnu/c++/5/bits/c++config.h
in package libstdc++-5-dev:amd64 5.5.0-1ubuntu1

Further information

Test program compiles and runs on Zesty Zapus with package
libstdc++-5-dev:amd64 (5.4.1-8ubuntu1).

[Launchpad Janitor (janitor)]

Status changed to 'Confirmed' because the bug affects multiple users.

[Dimitri John Ledkov (xnox)]

huh, one should not use libstdc++5 at all ever. One should only use libstdc++6. libstdc++5 is pre-historic ABI from the 90s no?

[Dimitri John Ledkov (xnox)]

Or i am confused.

[Dimitri John Ledkov (xnox)]

I think i am confused.

[Matthias Klose (doko)]

won't fix for GCC 5, fixed in 6 and 7

[Andrew Paxie (andrewpaxie)]

Will this situation remain the same on the next LTS, 18.04?

I now have to invent a migration strategy for a user of g++-5/libstdc++-v3 on Xenial,
which has no g++-6 or g++-7. I guess it has to be via Zesty, skipping Artful.

[Andrew Paxie (andrewpaxie)]

Ok, gcc-5 is in the universe repository for artful, meaning "community supported,"
not officially supported by Canonical.

[Matthias Klose (doko)]

yes, in general, you should use the default GCC version. Older versions might just be removed.

[Richard Huber (richaustin)]

This is a big problem for the community because NVCC from NVidia for Cuda 8 only works with Gcc-5. Probably why there is so much traffic on this issue right now. Nothing works with Cuda on GCC-5 with 17.10, which affects a ton of users.

[hami (zr-zz-alp)]

This is a big problem. I am using https://github.com/NetSys/bess. BESS relies on gRPC. gRPC fails to compile under gcc 5 due to the to_string not declared error. gRPC does compile under gcc 6 or 7 but it breaks BESS.

[David Welch (davidwelch158)]

This bug is related to https://bugs.launchpad.net/ubuntu/+source/glibc/+bug/1725869 (and https://sourceware.org/bugzilla/show_bug.cgi?id=22296). If gcc-5 is rebuilt with a version of glibc with that bug fixed then this one is fixed too.