Skip site navigation (1)Skip section navigation (2)
Date:      Fri, 27 Jul 2007 17:32:35 +0100
From:      Tom Evans <tevans.uk@googlemail.com>
To:        Peter Jeremy <peterjeremy@optushome.com.au>
Cc:        Sharad Chandra <sharadc@niksun.com>, FreeBSD Hackers <freebsd-hackers@freebsd.org>
Subject:   Re: gcc -m32 option on amd64.
Message-ID:  <1185553955.1457.8.camel@localhost>
In-Reply-To: <20070727102027.GH1152@turion.vk2pj.dyndns.org>
References:  <200707271513.48639.sharadc@niksun.com> <20070727102027.GH1152@turion.vk2pj.dyndns.org>

next in thread | previous in thread | raw e-mail | index | archive | help

--=-7o+A3uSvJUVkkyaOSDIU
Content-Type: text/plain
Content-Transfer-Encoding: quoted-printable

On Fri, 2007-07-27 at 20:20 +1000, Peter Jeremy wrote:
> On 2007-Jul-27 15:13:48 +0530, Sharad Chandra <sharadc@niksun.com> wrote:
> >I am trying gcc -m32 on freebsd 6.1 amd64 env, but it does not seems to =
be=20
> >working. i also installed /usr/port/lang/linux-libgcc/ but did not help
> >what i did is=3D>
> >echo "main () {}" > t.c; gcc -m32 t.c
> >/usr/bin/ld: skipping=20
> >incompatible /usr/local/lib/gcc/x86_64-portbld-freebsd6.1/4.2.0/gcc/x86_=
64-portbld-freebsd6.1/4.2.0/libgcc.a=20
> >when searching for -lgcc
> >/usr/bin/ld: cannot find -lgcc
> >collect2: ld returned 1 exit status
> >
> >how can we make this working?
>=20
> You are using gcc 4.2 from ports.  I suspect this only includes the
> 64-bit libraries.  gcc in the base system includes both 32-bit and
> 64-bit libraries by default but it still suffers the same problem.
>=20
> I had a go at fixing the problem in amd64/112215 but this has other
> problems and needs more work.  Note that non-trivial code will break
> because <machine/XXXX.h> points at amd64 headers whilst the -m32
> compiler needs i386 headers in many cases.  There's a non-trivial
> amount of work needed to actually get cross-building working.  I
> suggest you look throught the FreeBSD-amd64 archives.
>=20

gcc on amd64 is capable of generating i386 code, but ld on amd64 is
incapable of linking i386 code together without serious amounts of work.

At work, we use a large number of amd64 boxes as compile farm servers
for i386 development, using distcc and a wrapper to invoke gcc correctly
on the external boxes.

To verify that it works (it compiles to i386 code), do this:
$ uname -a; echo "main() { } " > t.c ; gcc -c -m32 -o t.o t.c; file t.o
FreeBSD chef.mintel.co.uk 6.1-STABLE FreeBSD 6.1-STABLE #1: Fri Jun 23
12:48:28 BST 2006
operator@chef.mintel.co.uk:/usr/obj/usr/src/sys/CHEF  amd64
t.o: ELF 32-bit LSB relocatable, Intel 80386, version 1 (FreeBSD), not
stripped


--=-7o+A3uSvJUVkkyaOSDIU
Content-Type: application/pgp-signature; name=signature.asc
Content-Description: This is a digitally signed message part

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.7 (FreeBSD)

iD8DBQBGqh4dlcRvFfyds/cRAlHPAKCEobXeinMaJu4IZTdyEdlFlyKHRQCgvNjy
mvMk1ivTtGNKTtCiLt49rpY=
=7zQL
-----END PGP SIGNATURE-----

--=-7o+A3uSvJUVkkyaOSDIU--




Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?1185553955.1457.8.camel>