Date: Sat, 28 Jul 2007 17:55:53 +1000 From: Peter Jeremy <peterjeremy@optushome.com.au> To: Tom Evans <tevans.uk@googlemail.com> Cc: FreeBSD Hackers <freebsd-hackers@freebsd.org> Subject: Re: gcc -m32 option on amd64. Message-ID: <20070728075553.GW1152@turion.vk2pj.dyndns.org> In-Reply-To: <1185553955.1457.8.camel@localhost> References: <200707271513.48639.sharadc@niksun.com> <20070727102027.GH1152@turion.vk2pj.dyndns.org> <1185553955.1457.8.camel@localhost>
next in thread | previous in thread | raw e-mail | index | archive | help
--NtwzykIc2mflq5ck Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable On 2007-Jul-27 17:32:35 +0100, Tom Evans <tevans.uk@googlemail.com> wrote: >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. Can you elaborate on what you mean by "incapable of linking i386 code"? The stock ld can definitely link i386 code: turion% ld -V GNU ld version 2.15 [FreeBSD] 2004-05-23 Supported emulations: elf_i386_fbsd elf_x86_64_fbsd turion%=20 There is a problem that the 32-bit pathnames on FreeBSD/amd64 are different to the 32-bit pathnames on FreeBSD/i386 (ie an i386 executable built on amd64 will point to /libexec/ld-elf32.so.1, rather than /libexec/ld-elf.so.1) so the result won't execute on a FreeBSD/i386 box - but I don't see that as a problem with ld, rather the configuration. --=20 Peter Jeremy --NtwzykIc2mflq5ck Content-Type: application/pgp-signature Content-Disposition: inline -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.7 (FreeBSD) iD8DBQFGqvaJ/opHv/APuIcRAiGPAJ9a7oZcY+MHSrUa9MbDW8+NLHlRjACcDubC HfHdWJwm9S6t4UAQ4Ri2fSM= =3zYe -----END PGP SIGNATURE----- --NtwzykIc2mflq5ck--
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20070728075553.GW1152>