[Bug libstdc++/86513] ostringstream default constructor missing from libstdc++
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=86513 Jonathan Wakely changed: What|Removed |Added CC||burnus at gcc dot gnu.org --- Comment #7 from Jonathan Wakely --- *** Bug 86643 has been marked as a duplicate of this bug. ***
[Bug libstdc++/86513] ostringstream default constructor missing from libstdc++
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=86513 --- Comment #6 from Jonathan Wakely --- OK, I was just going by what you said: (In reply to Csaba Ráduly from comment #3) > [...] my usual "svn up && make bootstrap && make install" [...]
[Bug libstdc++/86513] ostringstream default constructor missing from libstdc++
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=86513 --- Comment #5 from Csaba Ráduly --- BTW, I wasn't building in the source directory.
[Bug libstdc++/86513] ostringstream default constructor missing from libstdc++
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=86513 Jonathan Wakely changed: What|Removed |Added Status|WAITING |RESOLVED Resolution|--- |INVALID --- Comment #4 from Jonathan Wakely --- (In reply to Csaba Ráduly from comment #3) > I don't get this. ostringstream isn't even supposed to have a default > constructor, only the openmode, string and openmode, and the move > constructor (if I'm reading [ostringstream.cons] in N4659 right). That draft is no longer current, see https://wg21.link/p0935r0 > In the meantime it fixed itself at revision 262687 (mybe my usual "svn up && > make bootstrap && make install" triggered the necessary rebuild). Nothing changed, you just needed a rebuild. Next time please do a clean build and double check before reporting a bug. Incremental builds are not supported on trunk, if you live on the bleeding edge you need to deal with it. Even "make clean" isn't always enough, you might need a completely new build in an empty directory. Building in the source directory is also not supported, see https://gcc.gnu.org/wiki/FAQ#configure (building in a separate directory has the advantage that you can just remove the entire build dir and start again, and the sources are unaffected because they're in a different directory).
[Bug libstdc++/86513] ostringstream default constructor missing from libstdc++
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=86513 --- Comment #3 from Csaba Ráduly --- I don't get this. ostringstream isn't even supposed to have a default constructor, only the openmode, string and openmode, and the move constructor (if I'm reading [ostringstream.cons] in N4659 right). In the meantime it fixed itself at revision 262687 (mybe my usual "svn up && make bootstrap && make install" triggered the necessary rebuild). $ nm /usr/local/lib/gcc/x86_64-pc-linux-gnu/9.0.0/libstdc++.a | grep _ZNSt7__cxx1119basic_ostringstreamIcSt11char_traitsIcESaIcEEC1E | c++filt W std::__cxx11::basic_ostringstream, std::allocator >::basic_ostringstream(std::__cxx11::basic_ostringstream, std::allocator >&&) W std::__cxx11::basic_ostringstream, std::allocator >::basic_ostringstream(std::__cxx11::basic_string, std::allocator > const&, std::_Ios_Openmode) W std::__cxx11::basic_ostringstream, std::allocator >::basic_ostringstream(std::_Ios_Openmode) W std::__cxx11::basic_ostringstream, std::allocator >::basic_ostringstream()
[Bug libstdc++/86513] ostringstream default constructor missing from libstdc++
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=86513 --- Comment #2 from Csaba Ráduly --- I don't get this. ostringstream isn't even supposed to have a default constructor, only the openmode, string and openmode, and the move constructor (if I'm reading [ostringstream.cons] in N4659 right).
[Bug libstdc++/86513] ostringstream default constructor missing from libstdc++
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=86513 Jonathan Wakely changed: What|Removed |Added Status|UNCONFIRMED |WAITING Last reconfirmed||2018-07-14 Ever confirmed|0 |1 --- Comment #1 from Jonathan Wakely --- Have you done a clean build? Those symbols were added last week, but if you are doing an incremental build in an existing build tree you need to do 'make clean' in the libstdc++-v3 build directory and then build again. If you're using the subversion trunk you need to be prepared to do such things.