Re: preparing for GCC 5, especially libstdc++6

2015-07-15 Thread Matthias Klose
On 07/03/2015 03:24 PM, Matthias Klose wrote: On 07/02/2015 06:45 PM, Emilio Pozuelo Monfort wrote: On 01/07/15 14:39, Matthias Klose wrote: On 06/26/2015 03:01 AM, Emilio Pozuelo Monfort wrote: On 25/06/15 17:44, Matthias Klose wrote: On 06/25/2015 01:20 PM, Matthias Klose wrote: On

Re: preparing for GCC 5, especially libstdc++6

2015-07-07 Thread Martin Michlmayr
* Matthias Klose d...@debian.org [2015-06-16 23:37]: it's time to prepare for GCC 5 as the default compiler in unstable. FWIW, I compiled the entire archive on arm64 and I didn't find any obvious compiler bugs (i.e. internal compiler errors and similar). I found some more build failures with

Re: preparing for GCC 5, especially libstdc++6

2015-07-03 Thread Matthias Klose
On 07/02/2015 06:45 PM, Emilio Pozuelo Monfort wrote: On 01/07/15 14:39, Matthias Klose wrote: On 06/26/2015 03:01 AM, Emilio Pozuelo Monfort wrote: On 25/06/15 17:44, Matthias Klose wrote: On 06/25/2015 01:20 PM, Matthias Klose wrote: On 06/25/2015 11:23 AM, Emilio Pozuelo Monfort wrote: -

Re: preparing for GCC 5, especially libstdc++6

2015-07-03 Thread Sven Joachim
On 2015-07-04 03:17 +0200, Michael Biebl wrote: I just tried to g++/gcc 5 in chroot, this wanted to pull an additional 400MB: Is this expected? Are those binaries unstripped or how does it come that they are so huge? https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=783876 Cheers,

Re: preparing for GCC 5, especially libstdc++6

2015-07-03 Thread Michael Biebl
Am 03.07.2015 um 15:24 schrieb Matthias Klose: Now filed as https://bugs.debian.org/cgi-bin/pkgreport.cgi?tag=libstdc%2B%2B-cxx11;users=debian-...@lists.debian.org I just tried to g++/gcc 5 in chroot, this wanted to pull an additional 400MB: # apt-get install -t experimental gcc g++ Reading

Re: preparing for GCC 5, especially libstdc++6

2015-07-02 Thread Emilio Pozuelo Monfort
On 01/07/15 14:39, Matthias Klose wrote: On 06/26/2015 03:01 AM, Emilio Pozuelo Monfort wrote: On 25/06/15 17:44, Matthias Klose wrote: On 06/25/2015 01:20 PM, Matthias Klose wrote: On 06/25/2015 11:23 AM, Emilio Pozuelo Monfort wrote: - You suggest that some libraries may need to be renamed

Re: preparing for GCC 5, especially libstdc++6

2015-07-01 Thread Matthias Klose
On 06/26/2015 03:01 AM, Emilio Pozuelo Monfort wrote: On 25/06/15 17:44, Matthias Klose wrote: On 06/25/2015 01:20 PM, Matthias Klose wrote: On 06/25/2015 11:23 AM, Emilio Pozuelo Monfort wrote: - You suggest that some libraries may need to be renamed due to the ABI breaks. Do you have a

Re: preparing for GCC 5, especially libstdc++6

2015-06-25 Thread Matthias Klose
On 06/25/2015 11:23 AM, Emilio Pozuelo Monfort wrote: Thanks for the report. I have looked at the wiki page, but it's not entirely clear to me how the libstdc++ transition will go, so I have a few questions to better understand it. - You suggest that some libraries may need to be renamed due

Re: preparing for GCC 5, especially libstdc++6

2015-06-25 Thread Matthias Klose
On 06/25/2015 01:20 PM, Matthias Klose wrote: On 06/25/2015 11:23 AM, Emilio Pozuelo Monfort wrote: - You suggest that some libraries may need to be renamed due to the ABI breaks. Do you have a list of affected libraries? No. Getting this list is a bit difficult. Candidates for these

Re: preparing for GCC 5, especially libstdc++6

2015-06-25 Thread Emilio Pozuelo Monfort
On 25/06/15 17:44, Matthias Klose wrote: On 06/25/2015 01:20 PM, Matthias Klose wrote: On 06/25/2015 11:23 AM, Emilio Pozuelo Monfort wrote: - You suggest that some libraries may need to be renamed due to the ABI breaks. Do you have a list of affected libraries? No. Getting this list is a

Re: preparing for GCC 5, especially libstdc++6

2015-06-25 Thread Emilio Pozuelo Monfort
On 16/06/15 23:37, Matthias Klose wrote: Hi, it's time to prepare for GCC 5 as the default compiler in unstable. Compared to earlier version bumps, the switch to GCC 5 is a bit more complicated because libstdc++6 sees a few ABI incompatibilities, partially depending on the C++ standard

Re: preparing for GCC 5, especially libstdc++6

2015-06-18 Thread Matthias Klose
On 06/17/2015 09:42 PM, Lisandro Damián Nicanor Pérez Meyer wrote: On Tuesday 16 June 2015 23:37:41 Matthias Klose wrote: Hi, it's time to prepare for GCC 5 as the default compiler in unstable. Compared to earlier version bumps, the switch to GCC 5 is a bit more complicated because

Re: preparing for GCC 5, especially libstdc++6

2015-06-18 Thread Lisandro Damián Nicanor Pérez Meyer
On Thursday 18 June 2015 14:59:39 Matthias Klose wrote: [snip] I would prefer b), and preparing the packages to build with the gcc-5 from experimental (not unstable). OK. Does Qt 5.4.2 change sonames? If not, please prepare to change the library package names, if new cxx11 symbols are

Re: preparing for GCC 5, especially libstdc++6

2015-06-17 Thread Lisandro Damián Nicanor Pérez Meyer
On Tuesday 16 June 2015 23:37:41 Matthias Klose wrote: Hi, it's time to prepare for GCC 5 as the default compiler in unstable. Compared to earlier version bumps, the switch to GCC 5 is a bit more complicated because libstdc++6 sees a few ABI incompatibilities, partially depending on the

preparing for GCC 5, especially libstdc++6

2015-06-16 Thread Matthias Klose
Hi, it's time to prepare for GCC 5 as the default compiler in unstable. Compared to earlier version bumps, the switch to GCC 5 is a bit more complicated because libstdc++6 sees a few ABI incompatibilities, partially depending on the C++ standard version used for the builds. libstdc++6 will