https://gcc.gnu.org/bugzilla/show_bug.cgi?id=90050
Matthias Klose changed:
What|Removed |Added
CC||doko at debian dot org
--- Comment #8
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=90050
--- Comment #7 from Jonathan Wakely ---
See https://bugs.launchpad.net/ubuntu/+source/gcc-8/+bug/1824721 where I said:
"for now the short answer is "C++17 support in GCC 8 is experimental, the onus
is on you to link correctly"
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=90050
--- Comment #6 from Mihai Preda ---
OK, thanks.
So if on Ubuntu 19.04, the default compiler produces without errors/warnings,
from valid source code, an executable that crashes, that's programmer error?!
I understand the explanation, but there
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=90050
--- Comment #5 from Jonathan Wakely ---
Although if you link with -lstdc++fs then it should work OK, because the
incompatible std::filesystem symbols in libstdc++.so.6.0.26 won't be used.
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=90050
Jonathan Wakely changed:
What|Removed |Added
Status|UNCONFIRMED |RESOLVED
Resolution|---
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=90050
Frédéric Bron changed:
What|Removed |Added
CC||ufospoke at gmail dot com
--- Comment
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=90050
--- Comment #2 from Mihai Preda ---
Adding -lstdc++fs fixes the problem with g++ 8.3
g++-9 does not segfault even without -lstdc++fs
g++-9 --version
g++-9 (Ubuntu 9-20190402-1ubuntu1) 9.0.1 20190402 (experimental) [trunk
revision 270074]
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=90050
--- Comment #1 from Mihai Preda ---
I would hope somebody would take a look and reject this issues as invalid for
some reason, because otherwise it's rather severe.
