-m32 broken on bi-arch amd64 systems?

[Alexander Kabaev]

On Tue, 23 Dec 2008 17:36:08 +0100
Maciej Suszko <maciej at suszko.eu> wrote:

> "Garrett Cooper" <yanefbsd at gmail.com> wrote:
> > Hi guys,
> >     I think I may have found an issue today with our bi-endian
> > structure, and I wanted to make sure whether or not it was an
> > already known issue (-m32 is broken for gcc with lib32/libgcc.a):
> > 
> > [root at fbsd-7-test]# gcc -o boo boo.c # Compiles
> > [root at fbsd-7-test]# gcc -m32 -o boo boo.c
> > /usr/bin/ld: skipping incompatible /usr/lib/libgcc.a when searching
> > for -lgcc /usr/bin/ld: skipping incompatible /usr/lib/libgcc.a when
> > searching for -lgcc /usr/bin/ld: cannot find -lgcc
> > [root at fbsd-7-test]# file /usr/lib32/libgcc_s.so.1
> > /usr/lib32/libgcc_s.so.1: ELF 32-bit LSB shared object, Intel 80386,
> > version 1 (FreeBSD), dynamically linked, stripped
> > [root at fbsd-7-test]# uname -a
> > FreeBSD fbsd-7-test.gateway.2wire.net 7.1-PRERELEASE FreeBSD
> > 7.1-PRERELEASE #0: Sun Nov 23 16:19:09 UTC 2008
> > root at fbsd-7-test.gateway.2wire.net:/usr/obj/usr/src/sys/STARR  amd64
> > 
> >     I wish I had my amd64 CURRENT machine in front of me to confirm
> > this, but I don't.
> >     Please keep me CC'ed as I am not subscribed to either amd64@ or
> > stable at . Thanks!
> > -Garrett
> 
> I also noticed that behavior, shouldn't compiler/linker look
> into /usr/lib32 without additional -B switch?
> -- 
> regards, Maciej Suszko.

Read email archives, this was discussed on several occasions before.
Short summary: it never worked and will not work unless some
non-trivial work is put into how GCC handles include and linker search
paths.

-- 
Alexander Kabaev
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 187 bytes
Desc: not available
Url : http://lists.freebsd.org/pipermail/freebsd-stable/attachments/20081223/17c56970/signature.pgp