I realize I'm ahead of the game a bit, but is there a way (.e.,g., with XFLAGS
or LFLAGS) to force XC to use a 32-bit compilation.
XC will accept the following environment flags to modify the compilation:
as well as XC_CC, XC_F77 and XC_LINKER to change the command used for each stage of the compilation or source file. So, try
setenv XC_FFLAGS "-m32"
to force 32-bit. Note this may be a problem for the F2C driver script, I can send you a patched version if needed. Put these definitions in your .cshrc file so they'll be picked up when MKPKG calls XC.
What do you think the chances are of a successful sysgen on the 64-bit
About the same chance we'll get snow later today. The IRAF kernel is not 64-bit clean and things like pointers, file descriptors, structures, etc all need to be looked at. It is essentially a new platform port at this level. Beyond that, applications need to be reviewed, e.g. the NPIX counter from IMSTAT needs to become a long integer, header structures may need to be changed, etc. I can make it easier to force 32-bit compiles, full 64-bit support is a lot of repetative checking of code.
BTW, on the Alpha we got away with using the '-taso' flag when compiling
and at the time GCC didn't have a -m32, one reason we couldn't ever do an Alpha/linux port. Linux kernels are already starting to mess with the memory model we rely on internally, at some point this will become much more critical.
In case you're wondering: It is cloudy now but a little warm.....
You cannot post new topics in this forum You cannot reply to topics in this forum You cannot edit your posts in this forum You cannot delete your posts in this forum You cannot vote in polls in this forum