From owner-freebsd-hackers@FreeBSD.ORG Mon Jul 30 08:24:48 2007 Return-Path: Delivered-To: freebsd-hackers@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id DB50216A420 for ; Mon, 30 Jul 2007 08:24:48 +0000 (UTC) (envelope-from tevans.uk@googlemail.com) Received: from ug-out-1314.google.com (ug-out-1314.google.com [66.249.92.172]) by mx1.freebsd.org (Postfix) with ESMTP id 7067913C468 for ; Mon, 30 Jul 2007 08:24:48 +0000 (UTC) (envelope-from tevans.uk@googlemail.com) Received: by ug-out-1314.google.com with SMTP id o4so1173759uge for ; Mon, 30 Jul 2007 01:24:47 -0700 (PDT) DKIM-Signature: a=rsa-sha1; c=relaxed/relaxed; d=googlemail.com; s=beta; h=domainkey-signature:received:received:subject:from:to:cc:in-reply-to:references:content-type:date:message-id:mime-version:x-mailer; b=b9NRlVGKE7ilF1FcaAIvg758Kker9aOWYMnbCpW48nCdX3evXoo8WDTDPdvImVN+U83mZ4fjOm3BM/G/PFqSe9a83beAPDWWiOjTCguZxCOPRoHl1M3PNSTT4zJ7BbmedFSiH6KGNwvqrtTMljg5LMFvTVkqrsNANPPNtvbOGQI= DomainKey-Signature: a=rsa-sha1; c=nofws; d=googlemail.com; s=beta; h=received:subject:from:to:cc:in-reply-to:references:content-type:date:message-id:mime-version:x-mailer; b=UI1JmHT4H98NMZdVMiKyQP+JzT/htUd2bD6J0yew8gFIvM/me1IU4Ow4pQXZSiUsSUb8uYa4QLuE3YKTvK+ZFSZMxuSy1OvvkFYoMhkcDXqnUpCmXUG/FGWUz1ZFeXaS2JU8z7Oow0IR4iUhyXMSO06uMNiOfCeVqPioaYJnWWY= Received: by 10.82.182.1 with SMTP id e1mr3822040buf.1185783886813; Mon, 30 Jul 2007 01:24:46 -0700 (PDT) Received: from ?127.0.0.1? ( [217.206.187.79]) by mx.google.com with ESMTPS id h6sm11596175nfh.2007.07.30.01.24.45 (version=SSLv3 cipher=RC4-MD5); Mon, 30 Jul 2007 01:24:45 -0700 (PDT) From: Tom Evans To: Peter Jeremy In-Reply-To: <20070728075553.GW1152@turion.vk2pj.dyndns.org> References: <200707271513.48639.sharadc@niksun.com> <20070727102027.GH1152@turion.vk2pj.dyndns.org> <1185553955.1457.8.camel@localhost> <20070728075553.GW1152@turion.vk2pj.dyndns.org> Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="=-lyV5EA5D10ilnKybwVv1" Date: Mon, 30 Jul 2007 09:24:43 +0100 Message-Id: <1185783883.1444.3.camel@localhost> Mime-Version: 1.0 X-Mailer: Evolution 2.10.2 FreeBSD GNOME Team Port Cc: FreeBSD Hackers Subject: Re: gcc -m32 option on amd64. X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 30 Jul 2007 08:24:48 -0000 --=-lyV5EA5D10ilnKybwVv1 Content-Type: text/plain Content-Transfer-Encoding: quoted-printable On Sat, 2007-07-28 at 17:55 +1000, Peter Jeremy wrote: > On 2007-Jul-27 17:32:35 +0100, Tom Evans 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. >=20 > 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 >=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 Sure. By 'incapable of linking i386 code' I mean that the default toolchain of gcc invoking ld to assemble libraries and object files into executables is incapable of doing so when compiling i386 code. I say without serious amounts of work because, as you point out, it is possible to do. Any other english sentences you need explaining? --=-lyV5EA5D10ilnKybwVv1 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) iD8DBQBGraBIlcRvFfyds/cRAjv5AJ9rHZKoMvjXYD1eiJMiY6B2LHDKAACgu6p8 fVuRuIgN28qibHLyhGK69YQ= =2Bor -----END PGP SIGNATURE----- --=-lyV5EA5D10ilnKybwVv1--