IPO Error: unresolved

[francesc_verdaguer]

Dear all,

I am installing an air qualitity model called CMAQ.
In the middle of installation I encountered some errors. With the help of diferent people, and this forum, I managed to solve them, but now I have a new one.

It apears this error:

IPO Error: unresolved : pvm_version
Referenced in libioapi.a(iocplf2c.o)

I searched the file referencend, iocplf2c.o and then the source of it. I found the "pvm_version", but I don't understand which is the problem

I attach the terminal outputs, the iocplf2c.o source file (and iocpl.o source file, becaus there are more than one IPO errors), and the Makefile used to help to understand whats happening.

I hope you can tell me what I'm doing wrong.

Thank you for all, and of course, Merry Christmas to everybody

Francesc

[xgli]

I have probably a similar problem and am looking for an answer.

We know IPO stands for InterProcedural Optimizations. The errors are on those calls to a C library function and probably ipo can not be done between FORTRAN and C functions at level 2 or 3. But it only gives ipo errors on 32-bit build. The same code and library and alsowith -O2 is built OK for 64-bit executable. And even with ipo errors, the 32-bit built executable seems working OK. I guess it is just not optimized. Why 32-bit build is different from 64-bit build? Both are using Intel 9.0 compiler.

-xli

[TimP]

For the original question, my suspicion is that you don't have a compatible version of pvm installed. The code appears to have been written before the days of MPI. Did you ask the authors if there is an MPI version?

I don't know whether the 2nd post has any relationship, other than that both provoked the bogus "IPO error" which is a catch-all now for almost any kind of link failure report with current Intel compilers.

[xgli]

Oh, thereason made my guessing two cases aresimilar is by name his library looks likemade of C code too. So I turned to think theremight be issues with doing ipo cross different languages.

BWT, my case is fine if use -O0. So far it is not serious.

-xli