[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Bug#747935: gcc-4.8: Cross compiling -m32 on amd64 host fails due to finding amd64 libaries instead of x86 libraries



Package: gcc-4.8
Version: 4.8.2-21
Severity: normal

Attempts to compile a trivial program (test.c):

	int main() { return 0; }

fail on amd64 host:

$ gcc -m32 test.c
/usr/bin/ld: skipping incompatible /usr/lib/gcc/x86_64-linux-gnu/4.8/libgcc.a when searching for -lgcc
/usr/bin/ld: cannot find -lgcc
/usr/bin/ld: skipping incompatible /usr/lib/gcc/x86_64-linux-gnu/4.8/libgcc_s.so when searching for -lgcc_s
/usr/bin/ld: cannot find -lgcc_s
collect2: error: ld returned 1 exit status
$

I'm assuming gcc is simply mis-configured to not adjust the multilib
path when the -m32 command line option is present.

-- System Information:
Debian Release: jessie/sid
  APT prefers unstable
  APT policy: (500, 'unstable'), (500, 'stable')
Architecture: amd64 (x86_64)
Foreign Architectures: i386

Kernel: Linux 3.14.0 (SMP w/4 CPU cores)
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash

Versions of packages gcc-4.8 depends on:
ii  binutils        2.24.51.20140425-1
ii  cpp-4.8         4.8.2-21
ii  gcc-4.8-base    4.8.2-21
ii  libc6           2.18-5
ii  libcloog-isl4   0.18.2-1
ii  libgcc-4.8-dev  4.8.2-21
ii  libgmp10        2:6.0.0+dfsg-4
ii  libisl10        0.12.2-1
ii  libmpc3         1.0.1-1
ii  libmpfr4        3.1.2-1
ii  zlib1g          1:1.2.8.dfsg-1

Versions of packages gcc-4.8 recommends:
ii  libc6-dev  2.18-5

Versions of packages gcc-4.8 suggests:
ii  binutils [binutils-gold]  2.24.51.20140425-1
ii  gcc-4.8-doc               4.8.2-2
pn  gcc-4.8-locales           <none>
pn  gcc-4.8-multilib          <none>
pn  libasan0-dbg              <none>
pn  libatomic1-dbg            <none>
pn  libbacktrace1-dbg         <none>
pn  libgcc1-dbg               <none>
pn  libgomp1-dbg              <none>
pn  libitm1-dbg               <none>
pn  libquadmath0-dbg          <none>
pn  libtsan0-dbg              <none>

-- no debconf information


Reply to: