Message: Force the use of internal EXPAT Not Logged In (login)
 Next-in-Thread Next-in-Thread
 Next-in-Forum Next-in-Forum

Question Force the use of internal EXPAT 

Forum: Installation and Configuration
Date: 09 May, 2012
From: Cristian Bungau <Cristian Bungau>

Hello everybody,

I am trying to run a script on GRID, which implies running the code, then making changes to the code, recompiling and running again but within the same job submission.

But when a recompilation is attempted I get this error, and the job terminates:

/usr/bin/ld: cannot find -lexpat collect2: ld returned 1 exit status

All the compilations are running fine interactively, but not in the job submitted.

It looks like the expat library is in /usr/lib64 on the head node, and /lib64 on the compute nodes. As G4 was intalled interactively, the libraries are linked in such a way they expect expat to be in /usr/lib64, so when a compilation is attempted on the compute nodes, it will not find it, as it is in /lib64, so the linking error appears. Simply adding /lib64 to $LD_LIBRARY_PATH does not solve this.

Therefore although EXPAT is installed on the system, is there a way to install G4 using its internal EXPAT instead? I know it is not recommended, but in this case I think it is necessary...

Thank you very much for your help,

Best regards,


 Add Message Add Message
to: "Force the use of internal EXPAT"

 Subscribe Subscribe

This site runs SLAC HyperNews version 1.11-slac-98, derived from the original HyperNews

[ Geant 4 Home | Geant 4 HyperNews | Search | Request New Forum | Feedback ]