I see what you are talking about in the blas checks. However those checks "don't really matter" in that configure still succeeds.
Do you have a problem later with libnvJitLink.so <https://urldefense.us/v3/__http://libnvjitlink.so/__;!!G_uCfscf7eWS!Z6nfaGuXVLfVmi9EWFNhytjn-PHZA5vGVu1QdEZRgc8LaJigVHrccbBrA_nCIceeBq6hsOhfFwvrrTStrtuPdTA$ > ? When you build PETSc (send make.log) or when you run tests, make check? Or when you try to run your code? Barry > On Apr 5, 2024, at 2:14 PM, Frank Bramkamp <[email protected]> wrote: > > Hi Barry, > > Here I send you the configure.log file for the libnvJitLink problem. > > At the top of the configure.log file it seems to find libnvJitLink.so.12 > > But in the test for BlasLapack, it mentions > stdout: /tmp/petsc-h7tpd5_s/config.packages.BlasLapack/conftest: error while > loading shared libraries: libnvJitLink.so.12: cannot open shared object file: > No such file or directory > > > Is seems that for the BlasLapack test you include the “stubs" directory. In > “stubs”, we only have libnvJitLink.so > but not libnvJitLink.so.12 The libnvJitLink.so.12 we have in a different > directory (libs64), where is was also found before. > But maybe in the BlasLapack test, you only search for the libnvJitLink.so.12 > in the stubs directory. > > Here I am not sure, if there should be a libnvJitLink.so.12 in stubs as well > or not. > That means, it is not so clear if you should check in different directories, > or if we should add another link from libnvJitLink.so in stubs to > libnvJitLink.so.12. But if other people also do not have > libnvJitLink.so.12 in the stubs directory by default, that would be still a > problem. But I also do not know if the stubs directory is the problem. > > > Thanks, Frank > > <configure.log>
