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

[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 tst.c

  /usr/bin/ld: 
/usr/lib/gcc/x86_64-linux-gnu/5/../../../x86_64-linux-gnu/crti.o: unrecognized 
relocation (0x2a) in section `.init'
  /usr/bin/ld: final link failed: Bad value
  collect2: error: ld returned 1 exit status

This would happen with gcc-5 and with gcc-4.9. Downgrading libc6 would
fix it. After some fiddling I realized that upgrading to binutils =
2.25.90.20151209-1 (currently latest in sid) fixes it. I.e. with the
latest libc6 and the latest binutils packages things work.

Can the broken combination be prevented with some Conflicts: tags?
Currently this is a trap for the unwary.

Bug#747933: ping

[Dima Kogan]

Hi. This is a gentle ping.

This issue is still really annoying for anybody touching
cross-compilers. Can we please release this without that Recommends:
line (or a Suggests: instead)? It's great to solve this in a nice,
general way, but simply removing a (in my opinion) useless Recommends:
makes a very prominent manifestation of this issue go away right now. I
can attach a patch, but the change is trivial. Please tell me if there's
some way I can speed this along.

Thanks
dima


-- 
To UNSUBSCRIBE, email to debian-glibc-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Archive: https://lists.debian.org/8738dw3n2j@secretsauce.net

Bug#747933: libc6-dev: Recommends: (gcc | c-compiler) is problematic with cross-compilers

[Dima Kogan]

Package: libc6-dev
Version: 2.18-4
Severity: normal

Hi. Currently the libc6-dev package is

 Recommends: gcc | c-compiler

This is fine with native compilers. However, if I'm on an amd64 host,
and I try to install libc6-dev:armel with intent to use it with a
cross-compiler that targets armel, this recommendation is wrong.

By default, apt wants to install the Recommends, so if using aptitude to
install libc6-dev:armel, aptitude will try to install gcc:armel, which
clashes with gcc:amd64, since gcc is not Multi-Arch:same. Aptitude then
really tries to make that work by proposing to remove gcc in various
ways. You have to resolve this manually. This is arguably a deficiency
in aptitude, but maybe this Recommends can be loosened.

I don't believe Debian has any way to specify a Multi-Arch:foreign
virtual package (so the cross-compiler can't satisfy the c-compiler part
of this). Can we downgrade this Recommends to a Suggests, or maybe
remove it entirely? The user who installs libc6-dev likely already has a
compiler, and doesn't really benefit from this Recommends.


-- 
To UNSUBSCRIBE, email to debian-glibc-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Archive: https://lists.debian.org/87fvkei3aq@secretsauce.net

Bug#629534: libc6: Dynamic linker assertion failed after upgrade, nothing startable anymore

[Dima]

Just to confirm that Sven is not alone, I was hit by the same bug.

Bug#629534: libc6: Dynamic linker assertion failed after upgrade, nothing startable anymore

[Dima]

 Thanks.  To be clear, that means you are also on i386 and also trigger
 the ! bad dynamic tag assertion on upgrade from 2.13-4 to 2.13-5?

That's right.

I'm still logged into the box remotely, but I can not start any new
processes.

Regards,
Dima.

Bug#629534: libc6: Dynamic linker assertion failed after upgrade, nothing startable anymore

[Dima]

  But it was in an inline function in that header, so if some binary
  package was built on a machine with ancient libc6-dev, that could be a
  half-explanation.  Where do you get your binary packages from?

 ftp.de.debian.org


I also get my packages from ftp.de.debian.org


 But the system has been updated on Debian Unstable since Debian Woody
 (and moved from PC to PC, from harddisk to harddisk, without reinstall).


Mine is also quite old, I've been running unstable for the last 10 years.

Regards,
Dima.

Bug#629534: libc6: Dynamic linker assertion failed after upgrade, nothing startable anymore

[Dima]

 As you wrote that you are still logged into it you should be able to do
 the following:

 $ cd /lib
 $ echo ld*


Here is is:

$ echo ld*
ld-2.2.5.so ld-linux.so.1.8.10 ld-linux.so.2 ld.so ld.so.1.8.10