Bug#808181: libc6: Upgrade can make the linker unusable

2015-12-18 Thread Francesco Poli
On Fri, 18 Dec 2015 14:46:18 +0100 Aurelien Jarno wrote: [...] > binutils version 2.25.90.20151209-1 is now in testing, I am therefore > closing the bug. Thanks! I am another user who was bitten by this bug: I worked around it by installing binutils from unstable. In the meanwhile this bug repor

Bug#808181: Re[2]: Bug#808181: libc6: Upgrade can make the linker unusable

2015-12-17 Thread Vlad Orlov
Hi, > We are working to migrate binutils version 2.25.90.20151209-1 into > testing asap. If everything goes well it should be the case after the > 13:52 UTC dinstall run, so a few hours after that on the mirrors. > > In the meantime fetching and installing this version from sid, should > solve th

Bug#808181: libc6: Upgrade can make the linker unusable

2015-12-17 Thread Aurelien Jarno
reassign 808181 libc6-dev reassign 808205 libc6-dev forcemerge 808181 808205 forcemerge 808181 808206 severity 808181 serious thanks On 2015-12-16 23:36, Aurelien Jarno wrote: > On 2015-12-16 13:15, Dima Kogan wrote: > > Package: libc6 > > Severity: normal > > > > Hi. I had > > > > libc6=

Bug#808181: libc6: Upgrade can make the linker unusable

2015-12-17 Thread Vlad Orlov
Control: severity -1 important Control: tags -1 stretch Hi, Just stumbled upon this today in Testing (Stretch) - after today's libc6 upgrade. This issue breaks compilation of ANY autotools-based project as ld fails early in the configure phase: configure:3441: checking whether the C compiler

Bug#808181: libc6: Upgrade can make the linker unusable

2015-12-17 Thread Emmanuel Charpentier
Dear developers, I've just got bitten by this bug. About 3 millimeters from my carotid artery... This bugs effectively renders my system unusable for compilation purposes : even extremely mundane uses, such as upgradng some R packages, is now impossible. Suggestions : 1) The gravity of this bug

Bug#808181: libc6: Upgrade can make the linker unusable

2015-12-17 Thread Christophe
I am not sure to understand correctly... I currently have the same behavior with Stretch without sid/experimental repository, and I see binutils is not ready to migrate from testing, so no partial updates here I think. I do not understand how libc6-dev came built with an unavailable binutils versi

Bug#808181: libc6: Upgrade can make the linker unusable

2015-12-16 Thread Aurelien Jarno
On 2015-12-16 13:15, Dima Kogan wrote: > Package: libc6 > Severity: normal > > Hi. I had > > libc6= 2.19-22 > binutils = 2.25-4 > > and all was well. Then I upgraded to libc6 = 2.21-4 (currently latest in > sid). As a result, even the most basic build-time linking would fail. > For insta

Bug#808181: libc6: Upgrade can make the linker unusable

2015-12-16 Thread Dima Kogan
Package: libc6 Severity: normal Hi. I had libc6= 2.19-22 binutils = 2.25-4 and all was well. Then I upgraded to libc6 = 2.21-4 (currently latest in sid). As a result, even the most basic build-time linking would fail. For instance, with a trivial hello-world program: $ gcc-5 -o tst ts