On Sunday 16 April 2006 09:20, Maura Edeweiss Monville wrote:
then all the compilers (gcc, f77, g++) invoked by "start_cern" will see the processor being emulated, that is i686 rather than the true processor x86_64, therefore they automatically will, hopefully, geneate 32-bit code WITHOUT setting any flag and/or option ... ???? .... I might be insane .....
No, linux32 just changes uname output.
If this is not the case then I will have to split the native CERNLIB installation procedure e manually force the proper options/flags in order to generate code for a 32-bit machine.... a pain ...
You can download ftp://ftp.firstfloor.org/pub/ak/shell/gccwrap.tar.gz and unpack it in your home directory. Then compile the program with ~/gccwrap/32bit <build command> This will work as long as the build command looks in $PATH for gcc, not hardcodes /usr/bin/gcc or similar. Better strategy is to fix the broken build system though to support passing flags. Sooner or later someone has to do this anyways and you might as well start. -Andi