Frank, Could you send the final, successful configure. log. I want to see if PETSc ever mucks with it later in the configure process/ Barry > On Apr 5, 2024, at 10: 44 AM, Frank Bramkamp <bramkamp@ nsc. liu. se> wrote: > > > Dear
ZjQcmQRYFpfptBannerStart
This Message Is From an External Sender
This message came from outside your organization.
 
ZjQcmQRYFpfptBannerEnd
  Frank,

   Could you send the final, successful configure.log. I want to see if PETSc ever mucks with it later in the configure process/

  Barry


> On Apr 5, 2024, at 10:44 AM, Frank Bramkamp <[email protected]> wrote:
> 
> 
> Dear Barry,
> 
> That looks very good now. The -lnvc is gone now.
> 
> I also tested my small fortran program. There I can see that libnvc is automatically added as well, but this time is comes after the 
> libaccdevice.so. library for openacc. And then my openacc commands also work again.
> 
> 
> I also mentioned some issues with some cuda nvJitlink  library. I just found out that some path in our cuda compiler module was not set correctly.
> I will try to compile it with cuda again as well.
> 
> We just start to get PETSC on GPUs with the cuda backend, and I start with openccc for our fortran code to get first experience how everything works with GPU
> porting.
> 
> 
> Good that you could fix the issue. 
> 
> Thanks for the great help. Have a nice weekend, Frank Bramkamp
> 
> 
> 
> 
> 
> 

Reply via email to