Bug#637232: general: Multiarch breaks support for non-multiarch toolchain
On 08/09/2011 07:31 PM, Aurelien Jarno wrote: > I got fed up by people reporting bug on libc6, while this problem results > from a decision Debian to implement multiarch. People should work on > implementing a compatibility wrapper and to make upstream toolchain > multiarch aware. Until this is done, this bug should be kept opened. just do it. upstream changes will only land on trunk, and afaik the outcome of one of the multiarch sessions at Debconf was to have a multiarch-compat package at least containing symlinks for the .o files in /usr/lib, and maybe the /usr/include/asm symlink (replacing the one from gcc-multilib). -- To UNSUBSCRIBE, email to debian-devel-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/4e46b05c.3090...@debian.org
Bug#637232: general: Multiarch breaks support for non-multiarch toolchain
Aurelien Jarno wrote: > On Wed, Aug 10, 2011 at 10:48:23AM -0500, Jonathan Nieder wrote: >> I am >> tempted to reassign 629819 to general and merge the bugs. [...] > The bug is closed given we have provided some hints in NEWS.Debian.gz. I > am not sure what reassigning this already closed bug would change there. Yep. Thanks for the hints, by the way, and sorry to have filled your inbox. So if I understand correctly, this bug is about two or three remaining things: 1. Getting multiarch support patches applied in non-Debian toolchains (upstream gcc, upstream clang, and so on); 2. Wrapper scripts for building and using toolchains that lack built-in support for multiarch paths (e.g., for bisecting bugs introduced by old versions of gcc, using proprietary compilers, etc); 3. (?) Some other sort of trick to fool toolchains without lack for multiarch paths into coping with wheezy (symlinks to each library and header don't scale well for that, though it has been suggested by some people, but maybe a fake sysroot with symlinks to the multiarch and common directories could work). (1) and (2) is basically what you said already. Sorry for the noise. -- To UNSUBSCRIBE, email to debian-devel-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/20110810205918.ga7...@elie.gateway.2wire.net
Bug#637232: general: Multiarch breaks support for non-multiarch toolchain
On Wed, Aug 10, 2011 at 10:48:23AM -0500, Jonathan Nieder wrote: > Aurelien Jarno wrote: > > > I got fed up by people reporting bug on libc6, while this problem results > > from a decision Debian to implement multiarch. People should work on > > implementing a compatibility wrapper and to make upstream toolchain > > multiarch aware. Until this is done, this bug should be kept opened. > > Presumably you are referring to Bug#629819 and Bug#637218. > > Bug#629819 was about upstream gcc failing to build after crti.o et al > were moved. This is thorny because > > - the relevant non-Debian compiler is xgcc, which is an intermediate >product from the build process. So a compatibility wrapper for >gcc would not help here, though a nice build script could. > > - gcc's build system is a pain in the neck. > > Bug#637218 is a similar problem about headers moving. Again, the use > case was building and testing upstream gcc. > > http://bugs.debian.org/cgi-bin/bugreport.cgi?msg=85;bug=637218 > http://bugs.debian.org/cgi-bin/bugreport.cgi?msg=90;bug=637218 > > give a recipe for building non-multiarch-aware gcc in a multiarch > environment. > > You are right that this doesn't have much to do with eglibc, so I am > tempted to reassign 629819 to general and merge the bugs. As more > packages use the multiarch paths, it will only become more important > to have a way to communicate their location to non-Debian toolchains. > The bug is closed given we have provided some hints in NEWS.Debian.gz. I am not sure what reassigning this already closed bug would change there. -- Aurelien Jarno GPG: 1024D/F1BCDB73 aurel...@aurel32.net http://www.aurel32.net -- To UNSUBSCRIBE, email to debian-devel-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/20110810203458.ga5...@hall.aurel32.net
Bug#637232: general: Multiarch breaks support for non-multiarch toolchain
Aurelien Jarno wrote: > I got fed up by people reporting bug on libc6, while this problem results > from a decision Debian to implement multiarch. People should work on > implementing a compatibility wrapper and to make upstream toolchain > multiarch aware. Until this is done, this bug should be kept opened. Presumably you are referring to Bug#629819 and Bug#637218. Bug#629819 was about upstream gcc failing to build after crti.o et al were moved. This is thorny because - the relevant non-Debian compiler is xgcc, which is an intermediate product from the build process. So a compatibility wrapper for gcc would not help here, though a nice build script could. - gcc's build system is a pain in the neck. Bug#637218 is a similar problem about headers moving. Again, the use case was building and testing upstream gcc. http://bugs.debian.org/cgi-bin/bugreport.cgi?msg=85;bug=637218 http://bugs.debian.org/cgi-bin/bugreport.cgi?msg=90;bug=637218 give a recipe for building non-multiarch-aware gcc in a multiarch environment. You are right that this doesn't have much to do with eglibc, so I am tempted to reassign 629819 to general and merge the bugs. As more packages use the multiarch paths, it will only become more important to have a way to communicate their location to non-Debian toolchains. -- To UNSUBSCRIBE, email to debian-devel-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/20110810154823.ga4...@elie.gateway.2wire.net
Bug#637232: general: Multiarch breaks support for non-multiarch toolchain
Package: general Severity: critical Debian has choosen to implement multiarch, which amongs other things, means that the includes and libraries are moved in a new "multiarch" path. This breaks some upstream applications and non-Debian toolchain. It is possible to workaround some of the issues as described in /usr/share/doc/libc6/NEWS.Debian.gz. | eglibc (2.13-11) unstable; urgency=low | | Starting with the eglibc package version 2.13-5, the libraries are | shipped in the multiarch directory /lib/$arch instead of the more | traditional /lib. | | The toolchain in Debian has been updated to cope with that, and most | build systems should be unaffected. If you are using a non-Debian | toolchain to build your software and it is not able to cope with | multiarch, you might try to pass the following option to your | compiler: | |-B/usr/lib/$arch | | -- Aurelien Jarno Sat, 23 Jul 2011 23:42:46 +0200 I got fed up by people reporting bug on libc6, while this problem results from a decision Debian to implement multiarch. People should work on implementing a compatibility wrapper and to make upstream toolchain multiarch aware. Until this is done, this bug should be kept opened. -- System Information: Debian Release: wheezy/sid APT prefers unstable APT policy: (500, 'unstable') Architecture: amd64 (x86_64) Kernel: Linux 2.6.39-2-amd64 (SMP w/4 CPU cores) Locale: LANG=fr_FR.UTF-8, LC_CTYPE=fr_FR.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/bash -- To UNSUBSCRIBE, email to debian-devel-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/20110809173156.25324.28514.report...@volta.aurel32.net
