A bit off topic, but having trouble again with the 64-bit libs when trying to compile this short fortran code to build a shared object. Can anyone offer an explaination of what is meant by the relocation bit, and how to fix it? I've tried the -fPIC, but apparently I either didn't have it in the right place or it does not work. Be glad to take this offline if somone could help me. Here's the output from the compile....
Hostid: PGI=003048E02E69493B247282 fortran routine compiled create shared library... /usr/bin/ld: wrf_user_fortran_util_0.o: relocation R_X86_64_32 against `a local symbol' can not be used when making a shared object; recompile with -fPIC wrf_user_fortran_util_0.o: could not read symbols: Bad value error in load, error exit
Hi Sam:
Some library somewhere is using a different ABI than you expect. Do a
file wrf_user_fortran_util_0.o
and against any of the shared/static objects you are linking against. Make sure you have the right -L options. I got this when I had a stale build of something. I had to rebuild the application after cleaning out the old libs/objects (a simple make clean often helps).
Joe
Sam Drinkard wrote:
A bit off topic, but having trouble again with the 64-bit libs when trying to compile this short fortran code to build a shared object. Can anyone offer an explaination of what is meant by the relocation bit, and how to fix it? I've tried the -fPIC, but apparently I either didn't have it in the right place or it does not work. Be glad to take this offline if somone could help me. Here's the output from the compile....
Hostid: PGI=003048E02E69493B247282 fortran routine compiled create shared library... /usr/bin/ld: wrf_user_fortran_util_0.o: relocation R_X86_64_32 against `a local symbol' can not be used when making a shared object; recompile with -fPIC wrf_user_fortran_util_0.o: could not read symbols: Bad value error in load, error exit
CentOS mailing list CentOS@centos.org http://lists.centos.org/mailman/listinfo/centos
Joe,
Actually, there is little to do other than link this mess. The C compile is working OK, and so is the fortran part of the compile. Just the link blows up. There is no makefile either, so no way to clean anything. The pkg is part of a set of scripts put out by ucar.edu for viewing meteorlogical model output with NCL/NCAR Graphics. For more info, the url of what is needed is: http://box.mmm.ucar.edu/mm5/WRF_post/NCL.htm.
As for the file, it's a 64-bit elf LSB relocatable for AMD x86_64 not stripped (sysV). I think it might take one of the 32 bit libs that I don't have on this 64-bit machine, or so I've been told. If it would build on a 32, I just wonder if it would be usable on here?
Joe Landman wrote:
Hi Sam:
Some library somewhere is using a different ABI than you expect. Do a
file wrf_user_fortran_util_0.oand against any of the shared/static objects you are linking against. Make sure you have the right -L options. I got this when I had a stale build of something. I had to rebuild the application after cleaning out the old libs/objects (a simple make clean often helps).
Joe
Hi Sam:
Does this http://www.pgroup.com/resources/wrf/wrfv2_pgi52.htm help any? I know it is for 5.2, but similar things may apply.
Joe
Sam Drinkard wrote:
Joe,
Actually, there is little to do other than link this mess. The C compile is working OK, and so is the fortran part of the compile. Just the link blows up. There is no makefile either, so no way to clean anything. The pkg is part of a set of scripts put out by ucar.edu for viewing meteorlogical model output with NCL/NCAR Graphics. For more info, the url of what is needed is: http://box.mmm.ucar.edu/mm5/WRF_post/NCL.htm.
As for the file, it's a 64-bit elf LSB relocatable for AMD x86_64 not stripped (sysV). I think it might take one of the 32 bit libs that I don't have on this 64-bit machine, or so I've been told. If it would build on a 32, I just wonder if it would be usable on here?
Joe Landman wrote:
Hi Sam:
Some library somewhere is using a different ABI than you expect. Do a
file wrf_user_fortran_util_0.oand against any of the shared/static objects you are linking against. Make sure you have the right -L options. I got this when I had a stale build of something. I had to rebuild the application after cleaning out the old libs/objects (a simple make clean often helps).
Joe
No, actually we have the WRF built and running, but this script is part of a bunch of stuff to view the output from the WRF. AFIK, there is only one place that had any help at all, and the suggestions she sent me were way over my head.. something about compiling the thing with "wrapit77" but having to mess with the code itself. Seems there are more problems than normal on the x86-64 box when mixing fortran and C code.
Joe Landman wrote:
Hi Sam:
Does this http://www.pgroup.com/resources/wrf/wrfv2_pgi52.htm help any? I know it is for 5.2, but similar things may apply.
Joe
On Mon, 2005-10-10 at 17:11 -0400, Sam Drinkard wrote:
A bit off topic, but having trouble again with the 64-bit libs when trying to compile this short fortran code to build a shared object. Can anyone offer an explaination of what is meant by the relocation bit, and how to fix it? I've tried the -fPIC, but apparently I either didn't have it in the right place or it does not work. Be glad to take this offline if somone could help me. Here's the output from the compile....
Hostid: PGI=003048E02E69493B247282 fortran routine compiled create shared library... /usr/bin/ld: wrf_user_fortran_util_0.o: relocation R_X86_64_32 against `a local symbol' can not be used when making a shared object; recompile with -fPIC wrf_user_fortran_util_0.o: could not read symbols: Bad value error in load, error exit
It has to do with the .a or .o file you're linking against, in this case wrf_user_fortran_util_0.o. That object needs to use -fPIC when being built.
-
Ignacio Vazquez-Abrams -
Joe Landman -
Sam Drinkard