[petsc-users] funny link error
Scott Kruger
kruger at txcorp.com
Mon Mar 22 09:45:30 CDT 2021
>From you make.log, it looks like petsc found it here:
/opt/cray/wlm_detect/1.3.3-7.0.1.1_4.19__g7109084.ari/lib64
PETSc has it and found it because BuildSystem did the query of what
it takes to get C/C++/Fortran to work together. Why is it needed?
That's up to Cray.
But the question is:
How is your CMake build getting PETSc info?
If
a) it using pkg-config and CMake's ability to parse it, then it looks like our pkg-config export might need work.
We'd need to see the pkg-config file to be sure though.
and if
b) it is not using pkg-config, then the answer is it should.
Scott
On 2021-03-21 08:25, Mark Adams did write:
> We are having problems with linking and use static linking.
> We get this error and have seen others like it (eg, lpetsc_lib_gcc_s)
>
> /usr/bin/ld: cannot find -lpetsc_lib_wlm_detect-NOTFOUND
>
> wlm_detect is some sort of system library, but I have no idea where this
> petsc string comes from.
> This is on Cori and the application uses cmake.
> I can run PETSc tests fine.
>
> Any ideas?
>
> Thanks,
> Mark
--
Scott Kruger
Tech-X Corporation kruger at txcorp.com
5621 Arapahoe Ave, Suite A Phone: (720) 466-3196
Boulder, CO 80303 Fax: (303) 448-7756
More information about the petsc-users
mailing list