You are not logged in.
chaonaut, then they may have been created by a .install file .
Disliking systemd intensely, but not satisfied with alternatives so focusing on taming systemd.
(A works at time B) && (time C > time B ) ≠ (A works at time C)
Offline
anyway, they're in place now, and gcc5 can build with LTO yet more packages (in my system) than gcc-4.9.
— love is the law, love under wheel, — said aleister crowley and typed in his terminal:
usermod -a -G wheel love
Offline
--with-default-libstdcxx-abi=c++98 will be dropped in a couple of weeks (assuming no big issues with the compiler are found) and then we will do a rebuild.
Is the change to the new ABI still planned?
Offline
Disliking systemd intensely, but not satisfied with alternatives so focusing on taming systemd.
(A works at time B) && (time C > time B ) ≠ (A works at time C)
Offline
Thanks for the link !
Offline
Sakura:-
Mobo: MSI MAG X570S TORPEDO MAX // Processor: AMD Ryzen 9 5950X @4.9GHz // GFX: AMD Radeon RX 5700 XT // RAM: 32GB (4x 8GB) Corsair DDR4 (@ 3000MHz) // Storage: 1x 3TB HDD, 6x 1TB SSD, 2x 120GB SSD, 1x 275GB M2 SSD
Making lemonade from lemons since 2015.
Offline
Fedora and Ubuntu seem to go with the new ABI too though, are they not affected by this issue?
Offline
WorMzy wrote:Fedora and Ubuntu seem to go with the new ABI too though, are they not affected by this issue?
Yes they are. Note neither of them are actually using hte new ABI yet.
Offline
We are now switching the ABI. So we won't wast any more time on waiting for LLVM?
https://llvm.org/bugs/show_bug.cgi?id=23529
Offline
It is patched in our repos - same as Fedora.
Offline
Thanks! I'm glad to see it
Our little poor patch policy *patpatpat*
The patch is hosted on (review).llvm.org
Last edited by hoschi (2015-12-10 12:21:19)
Offline
Well, it only took ten months to happen. As the original poster I honestly thought it would've happened sooner.
Offline
Well, it only took ten months to happen. As the original poster I honestly thought it would've happened sooner.
LLVM/clang++ still is not patched to work with the new ABI upstream. We have pulled a patch from their review tracker (which is also used by Fedora 23), but I see reports it still is not actually fully fixed...
Offline
This morning I updated my system with the rebuilt packages. I was about to rebuild all my stuff (not Arch packages but just my local C++ projects) when I decided to give them a try before rebuilding everything. To my surprise, all the executables and libraries built with gcc 5.2 are still working. I tested just a few of them but none have crashed or misbehaved up to now. So I'm confused since as far as I understood binaries compiled against the old ABI should crash when using the new libstdc++. Since Arch rebuilt everything I thought it was necessary also for me to rebuild all my software otherwise it would crash, but it seems it's not the case (at least not always) so I'm undecided about rebuilding all my stuff or not. Can anyone please shed some light on this situation? Thanks.
Offline
If your projects don't link to any other (rebuilt) libraries they should continue to work, since libstdc++ itself contains both ABIs. Only if you use other libraries and they are linked against the new ABI you might run into symbol lookup errors
Last edited by V1del (2015-12-11 09:29:43)
Online
@V1del: some executables of mine link libQtGui and other Qt libraries and they don't crash. But I'd guess they should given your words; am I correct?
Offline
It depends which parts of C++ use use - many are the same across the two ABIs.
Offline
@Allan: thanks for the clarification. I started a full rebuild anyway since I got compiler errors related to the new ABI when compiling my code this morning after some modifications.
Offline