Bug#629819: libc6-dev: moving crt1.o crti.o etc. to /usr/lib/<triplet> breaks external multiarch unaware applications
Package: libc6-dev
Version: 2.13-5
Severity: normal
Hi,
the moving of crt1.o, crti.o, ... from /usr/lib to /usr/lib/<triplet>
breaks external applications that are not aware of the new multiarch
paths. One such application is GCC from SVN, which now fails to compile
with this error:
/usr/bin/ld: cannot find crti.o: No such file or directory
(seems to happen the first time the stage1 compiler is used to link
something). Testing something with gcc-trunk (and eventually bisecting
gcc) is something I do quite regularily.
In general I like the multiarch idea and don't want to go the road back.
So a possible solution I see to make such external applications work
again could be the introduction of a libc6-dev-compat package that ships
the links /usr/lib/*.o -> /usr/lib/<triplet>/*.o. This package should
not be installed by default, but only by the admin knowing what he does.
Andreas
-- System Information:
Debian Release: wheezy/sid
APT prefers oldstable
APT policy: (600, 'oldstable'), (600, 'unstable'), (600, 'testing'), (600, 'stable'), (500, 'stable-updates'), (130, 'experimental')
Architecture: i386 (i686)
Kernel: Linux 2.6.32-5-amd64 (SMP w/4 CPU cores)
Locale: LANG=C, LC_CTYPE=C (charmap=ANSI_X3.4-1968)
Shell: /bin/sh linked to /bin/dash
Versions of packages libc6-dev depends on:
ii libc-dev-bin 2.13-5 Embedded GNU C Library: Developmen
ii libc6 2.13-5 Embedded GNU C Library: Shared lib
ii linux-libc-dev 2.6.39-1 Linux support headers for userspac
Versions of packages libc6-dev recommends:
ii gcc [c-compiler] 4:4.6.0-5 The GNU C compiler
ii gcc-4.2 [c-compiler] 4.2.4-6 The GNU C compiler
ii gcc-4.3 [c-compiler] 4.3.5-5 The GNU C compiler
ii gcc-4.4 [c-compiler] 4.4.6-3 The GNU C compiler
ii gcc-4.5 [c-compiler] 4.5.3-1 The GNU C compiler
ii gcc-4.6 [c-compiler] 4.6.0-11 The GNU C compiler
Versions of packages libc6-dev suggests:
pn glibc-doc <none> (no description available)
pn manpages-dev <none> (no description available)
-- no debconf information
Reply to: