On 29 June 2015 at 17:11, Sebastiaan Couwenberg <sebas...@xs4all.nl> wrote: >> Control: reopen -1 >> Control: severity -1 important >> >> On 06/28/2015 12:51 AM, Debian Bug Tracking System wrote: >>> Using -D_GLIBCXX_USE_CXX11_ABI=0 allows liblas to build with GCC 5 >>> indeed. >> >> the goal should be to build everything using the new ABI, especially if >> this is >> a library package. > > So now what? > > As far as I understand, libLAS isn't affected, boost is. Because boost is > not rebuilt with GCC 5, libLAS fails to build. > > But your reopening of this issue probably means my undestanding is incorrect. > > So I must conclude that I don't understand what I need to do to resolve > this issue in libLAS, so please advice. >
Iyay, can we please take things slow?! We have two transitions in parallel (i) change compiler to a new version & (ii) change libstdc++ ABI. In unstable - there is g++5 (i), but there isn't libstdc++ that provides C++11 ABI (ii). Boost is compiled with the default compiler & the default ABI. And boost will be only rebuild, once the default compiler (i) and libstdc++ ABI (ii) change in unstable. So far I didn't yet had to rebuild boost with libstdc++ C++11 ABI (ii) in experimental, to successfully build & link libraries and apps with g++5 (i) and libstdc++ C++11 (ii). To avoid any ambiguity, please provide full build-log with specific details about the version of gcc-defaults, boost-defaults, libboost1.5*-dev and libstdc++6 packages in use. As currently in experimental: gcc-defaults 141, boost-defaults (from sid), boost1.55 (from sid, compiled with 98 abi), libstdc++6 (5.1.1-21, with new C++11 abi) liblas compiles correctly without a hitch, see the attached buildlog. I'm happy to look into bug-reports about build-failures between these set of packages, but note that a matching libstdc++6 must be used with a matching g++ at compile time, otherwise one will see link errors if any of the inline namespace dual-abi symbols are used (e.g. std::__cxx11::string and etc). Also please study the attached successful build log in experimental, and let me know if there are any issues with it. -- Regards, Dimitri.
_______________________________________________ Pkg-grass-devel mailing list Pkgemail@example.com http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/pkg-grass-devel