Your message dated Mon, 27 Jul 2020 18:05:22 +0200
with message-id <[email protected]>
and subject line Re: general: Multiarch breaks support for non-multiarch
toolchain
has caused the Debian Bug report #637232,
regarding eglibc: changes to paths concerning crt1.o, crti.o and crtn.o breaks
building LLVM Trunk
to be marked as done.
This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.
(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact [email protected]
immediately.)
--
637232: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=637232
Debian Bug Tracking System
Contact [email protected] with problems
--- Begin Message ---
Package: eglibc
Version: 2.13-18
Severity: normal
With the most recent changes of moving the object files under
/usr/lib/x86_64-linux-gnu/ the linker to build Clang/LLVM breaks.
A workaround is to add symlinks for crt1.o, crti.o and crtn.o back under
/usr/lib.
Is there a solution possible in perhaps alternatives to make a clean approach
for the LLVM/Clang project to see these object files necessary to link against
and continue building without having to rehack their configure/makefiles?
I would expect the Debian FreeBSD being part of the family would be a great
opportunity to make this issue be resolved and work across all architectures
and for other compilers besides the GCC Family.
- Marc
-- System Information:
Debian Release: wheezy/sid
APT prefers unstable
APT policy: (500, 'unstable'), (1, 'experimental')
Architecture: amd64 (x86_64)
Kernel: Linux 3.0.0-1-amd64 (SMP w/2 CPU cores)
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/bash
--- End Message ---
--- Begin Message ---
On Tue, 09 Aug 2011 19:31:56 +0200 Aurelien Jarno <[email protected]> wrote:
> 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.
[...]
> 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.
This was now ~9 years ago and this report had no activity since late
2014. I would hope it is no longer relevant, so I'll close the report.
Ansgar
--- End Message ---
