Thursday, September 17, 2009

AU program compilation issues

I dwelt earlier on the shared library issues with Topspin because of the 64 bit cyberworld in my workstation not able to emulate the 32 bit environment properly. The remedy was installing the 'needed' 32 bit libraries. The devil is indeed lurking in the 'needed' word. One of these days I will add the list of libraries I installed in another post (i.e. after FC10 crashes again,....:-{ ]

A related problem is compiling the AU programs from within Topspin. Since these are at the heart, C programs, they do need all your 'gcc' muscle to compile, which is what the command like 'cplbruk ' initiates by passing the appropriate call to the gcc.  Convenient yes, but we cannot switch on or off any extra options sent to gcc.  This means that, the compiler and all the libraries it needs (mostly the 32 variety) should be there.  There is no easy way to pass different path name, for instance, as you would do in a 'configure' step that typically precedes the 'make'.  


Ok, for Topspin this is what you do :

yum install glibc-devel.i386 

 AU program compilation works after this flawlessly  (...gulp....)  so far !

1 comment:

  1. Recently I upgraded to FC12 and faced exactly the same issue as above. Once I installed glibc-devel.i686, the Bruker au programs compiled normally. Incidentally, DRX499 has the same compilation issues, even though that box does not run 64 bit distro.

    ReplyDelete