freebsd stable - Sep 2009 - GCC -m32 option on FreeBSD/AMD64 7.2

Hi,
is C++ + GCC -m32 option officially supported by FreeBSD/AMD64 7.2? I am
getting the following errors for simplest input:

shell::wilx:~/tmp> cat >m32.cxx
#include <iostream>
shell::wilx:~/tmp> g++ -c m32.cxx
shell::wilx:~/tmp> g++ -m32 m32.cxx
In file included from /usr/include/c++/4.2/ext/new_allocator.h:37,
                 from /usr/include/c++/4.2/bits/c++allocator.h:39,
                 from /usr/include/c++/4.2/bits/allocator.h:53,
                 from /usr/include/c++/4.2/memory:54,
                 from /usr/include/c++/4.2/string:48,
                 from /usr/include/c++/4.2/bits/locale_classes.h:47,
                 from /usr/include/c++/4.2/bits/ios_base.h:47,
                 from /usr/include/c++/4.2/ios:48,
                 from /usr/include/c++/4.2/ostream:45,
                 from /usr/include/c++/4.2/iostream:45,
                 from m32.cxx:1:
/usr/include/c++/4.2/new:95: error: 'operator new' takes type
'size_t'
('unsigned int') as first parameter
/usr/include/c++/4.2/new:96: error: 'operator new' takes type
'size_t'
('unsigned int') as first parameter
/usr/include/c++/4.2/new:99: error: 'operator new' takes type
'size_t'
('unsigned int') as first parameter
/usr/include/c++/4.2/new:100: error: 'operator new' takes type
'size_t'
('unsigned int') as first parameter
/usr/include/c++/4.2/new:105: error: 'operator new' takes type
'size_t'
('unsigned int') as first parameter
/usr/include/c++/4.2/new:106: error: 'operator new' takes type
'size_t'
('unsigned int') as first parameter

--
VH

-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 195 bytes
Desc: OpenPGP digital signature
Url :
http://lists.freebsd.org/pipermail/freebsd-stable/attachments/20090901/4ddaf01f/signature.pgp

On 2009-Sep-01 19:13:03 +0200, V?clav Haisman <v.haisman@sh.cvut.cz>
wrote:
>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.

-- 
Peter Jeremy
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 196 bytes
Desc: not available
Url :
http://lists.freebsd.org/pipermail/freebsd-stable/attachments/20090909/8440d7d0/attachment.pgp