Date: Thu, 10 Sep 2009 05:33:45 +1000 From: Peter Jeremy <peterjeremy@acm.org> To: =?iso-8859-1?Q?V=E1clav?= Haisman <v.haisman@sh.cvut.cz> Cc: freebsd-stable@freebsd.org Subject: Re: GCC -m32 option on FreeBSD/AMD64 7.2 Message-ID: <20090909193345.GA55347@server.vk2pj.dyndns.org> In-Reply-To: <4A9D561F.5000808@sh.cvut.cz> References: <4A9D561F.5000808@sh.cvut.cz>
next in thread | previous in thread | raw e-mail | index | archive | help
--0OAP2g/MAC+5xKAE Content-Type: text/plain; charset=iso-8859-1 Content-Disposition: inline Content-Transfer-Encoding: quoted-printable On 2009-Sep-01 19:13:03 +0200, V=E1clav Haisman <v.haisman@sh.cvut.cz> wrot= e: >is C++ + GCC -m32 option officially supported by FreeBSD/AMD64 7.2? The short answer is "no" - though this is a common request and there are some PRs open for it. At present, the only supported way to build i386 code on amd64 is by installing an i386 world and compiling in either a jail or chroot. Basically, whilst '-m32' correctly generates 32-bit code, virtually all programs wind up (indirectly) #include'ing files from /usr/include/machine and this directory assumes the native machine definitions - in the case of amd64, longs and pointers are 64-bits. Whilst it's not immediately obvious what happened here, I am confident this is the underlying cause. --=20 Peter Jeremy --0OAP2g/MAC+5xKAE Content-Type: application/pgp-signature Content-Disposition: inline -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.12 (FreeBSD) iEYEARECAAYFAkqoAxkACgkQ/opHv/APuIf78ACfcqfmVlgpkjFNe9UGbJM5fXVP AuUAn0KFZe2OSwOCGYgSVRQNQctF/YR2 =ncBT -----END PGP SIGNATURE----- --0OAP2g/MAC+5xKAE--
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20090909193345.GA55347>