--- Begin Message ---
Package: gcc-5-multilib
Version: 5.3.1-14
Severity: important
Dear Maintainers,
when trying to build i386 binaries using gcc-5-multilib on an amd64
host, <errno.h> includes cannot be resolved.
,----
| $ echo '#include <errno.h>' | gcc -m32 -E - > /dev/null
| In file included from /usr/include/bits/errno.h:24:0,
| from /usr/include/errno.h:35,
| from <stdin>:1:
| /usr/include/linux/errno.h:1:23: fatal error: asm/errno.h: No such file or directory
| $ echo '#include <errno.h>' | gcc -m64 -E - > /dev/null
| $
`----
gcc-multilib used to provide a symlink for /usr/include/asm (in my case
to x86_64-linux-gnu/asm). Restoring that symlink would fix the problem I
observed.
Cheers,
-Hilko
-- System Information:
Debian Release: stretch/sid
APT prefers unstable
APT policy: (500, 'unstable')
Architecture: amd64 (x86_64)
Foreign Architectures: i386
Kernel: Linux 4.4.0-1-amd64 (SMP w/6 CPU cores)
Locale: LANG=en_US.utf8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)
Versions of packages gcc-5-multilib depends on:
ii gcc-5 5.3.1-14
ii gcc-5-base 5.3.1-14
ii lib32gcc-5-dev 5.3.1-14
ii libc6-dev-i386 2.22-7
ii libc6-dev-x32 2.22-7
ii libx32gcc-5-dev 5.3.1-14
gcc-5-multilib recommends no packages.
gcc-5-multilib suggests no packages.
-- no debconf information
--- End Message ---
--- Begin Message ---
Control: tags -1 + wontfix
On 22.04.2016 00:03, Hilko Bengen wrote:
Package: gcc-5-multilib
Version: 5.3.1-14
Severity: important
Dear Maintainers,
when trying to build i386 binaries using gcc-5-multilib on an amd64
host, <errno.h> includes cannot be resolved.
,----
| $ echo '#include <errno.h>' | gcc -m32 -E - > /dev/null
| In file included from /usr/include/bits/errno.h:24:0,
| from /usr/include/errno.h:35,
| from <stdin>:1:
| /usr/include/linux/errno.h:1:23: fatal error: asm/errno.h: No such file or directory
| $ echo '#include <errno.h>' | gcc -m64 -E - > /dev/null
| $
`----
gcc-multilib used to provide a symlink for /usr/include/asm (in my case
to x86_64-linux-gnu/asm). Restoring that symlink would fix the problem I
observed.
the /usr/include/asm symlink is shipped in the gcc-multilib package. We can't
ship it in any gcc-*-multilib package without giving up coinstallability of
different toolchain versions.
There maybe is an older glibc report which proposes shipping this symlink in a
new binary package built from glibc, but for now it's shipped in gcc-multilib.
--- End Message ---