On 03/11/2006, at 12:36 AM, Enno Fennema wrote:
I run on a x86_64 system and to build 32-bit objects the compiler
needs a -m32 option.
I am trying to rebuild the sal module (initially to get debugging
symbols). The first thing that build seems to do is create and
execute a .cmd file to compile and link the typesconfig program.
The Makefiles description page of the tools project indicates the
use of environment variables ENVCFLAGS and ENVCXXFLAGS to add extra
options, like my -m32, to the buildprocess. I have tried this and
a few other things but I can't get the -m32 into the
(generated) .cmd file.
All help appreciated.
Enno
Enno
A simple method is to set CC="/path/to/gcc -m32" and CXX="/path/to/g+
+ -m32" before running configure. Note the quotes ("). This works for
me building 32 bit on 64 bit machine for GNU/Linux SPARC (debian/
unstable) like CC="/usr/local/4.1/bin/gcc -m32" and it is easy to
switch to a different compiler. The configure step checks the
compiler and sets up some related paths.
If you are using a distribution supplied compiler it should be
sufficient to configure and build in a 32 bit shell, after using
command $ linux32 bash. This changes the value returned by uname -m.
I didn't try this for a long time, as I think it would hide any bugs
based on wrong uses of uname -m.
jim
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
