How are you linking you’re code? These symbols are included in the PGI C runtime library “libpgc.[a,so]” which gets linked automatically when linking using one of the PGI drivers, so I’m not sure why you’d be missing them.
Thanks for replying, Mat. That is what I thought … that these symbols should be getting linked internally/automatically. Could it be a problem with the way PGI has been installed on our systems or a conflicting PGI driver?
The following is a command line ‘dump’ by using the “-v” switch:
ANSYS bundles the PGI runtime with their source. I believe what happening is that the linker is picking up the bundled runtime (in the “ansys/syslib/linop64” directory) and not the 7.2-4 versions. Please check with ANSYS, what version of PGI they recommend and/or if you can replace the runtime they ship with 7.2-4.
Your suspicion was correct … the mismatch between the ANSYS-bundled PGI version and the 7.2-4 version of PGI that I am using was causing the conflict in the undefined reference symbols.