Re: [petsc-users] Help Needed Debugging Installation Issue for PETSc with SLEPc

[Zongze Yang]

Thanks very much!

Best wishes,
Zongze

> On 15 Mar 2024, at 22:50, Pierre Jolivet  wrote:
> 
> This was fixed 5 days ago in 
> https://urldefense.us/v3/__https://gitlab.com/slepc/slepc/-/merge_requests/638__;!!G_uCfscf7eWS!fPbzaiH98Qdihq74E8kcX8JQE_EGk_PhMqYnheGPjwJD2l8AhgXg3ZrEkFZmV0lfG8vVlKawhAaQq4eSMRZVffeF$
>  , so you need to use an up-to-date release branch of SLEPc.
> 
> Thanks,
> Pierre
> 
>> On 15 Mar 2024, at 3:44 PM, Zongze Yang  wrote:
>> 
>> This Message Is From an External Sender
>> This message came from outside your organization.
>> Hi,
>> 
>> I am currently facing an issue while attempting to install PETSc with SLEPc. 
>> Despite not encountering any errors in the log generated by the 'make' 
>> command, I am receiving an error message stating "Error during compile".
>> 
>> I would greatly appreciate it if someone could provide me with some guidance 
>> on debugging this issue. 
>> 
>> I have attached the configure logs and make logs for both PETSc and SLEPc 
>> for your reference.
>> 
>> Below is an excerpt from the make.log file of SLEPc:
>> ```
>> CLINKER default/lib/libslepc.3.020.1.dylib
>> ld: warning: -commons use_dylibs is no longer supported, using error 
>> treatment instead
>> ld: warning: -commons use_dylibs is no longer supported, using error 
>> treatment instead
>> ld: warning: -commons use_dylibs is no longer supported, using error 
>> treatment instead
>> ld: warning: duplicate -rpath 
>> '/Users/zzyang/opt/firedrake/firedrake-real-int32-debug/src/petsc/default/lib'
>>  ignored
>> ld: warning: dylib 
>> (/opt/homebrew/Cellar/gcc/13.2.0/lib/gcc/current/libgfortran.dylib) was 
>> built for newer macOS version (14.0) than being linked (12.0)
>> ld: warning: dylib 
>> (/opt/homebrew/Cellar/gcc/13.2.0/lib/gcc/current/libquadmath.dylib) was 
>> built for newer macOS version (14.0) than being linked (12.0)
>>DSYMUTIL default/lib/libslepc.3.020.1.dylib
>> gmake[6]: Leaving directory 
>> '/Users/zzyang/opt/firedrake/firedrake-real-int32-debug/src/petsc/default/externalpackages/git.slepc'
>> gmake[5]: Leaving directory 
>> '/Users/zzyang/opt/firedrake/firedrake-real-int32-debug/src/petsc/default/externalpackages/git.slepc'
>> ***ERROR
>>  Error during compile, check default/lib/slepc/conf/make.log
>>  Send all contents of ./default/lib/slepc/conf to slepc-ma...@upv.es 
>> 
>> 
>> Finishing make run at 五, 15  3 2024 21:04:17 +0800
>> ```
>> 
>> Thank you very much for your attention and support.
>> 
>> Best wishes,
>> Zongze
>> 
>> 
> 

Re: [petsc-users] Help Needed Debugging Installation Issue for PETSc with SLEPc

[Pierre Jolivet]

This was fixed 5 days ago in 
https://urldefense.us/v3/__https://gitlab.com/slepc/slepc/-/merge_requests/638__;!!G_uCfscf7eWS!Z6nHLo3qh8bAe4zTIkJHhBcLc2WyVfPb47nBF38kwu8pyoNFz11wVdiL2ytUg66oHoVPkjBafopf_Gag8j6dXQ$
 , so you need to use an up-to-date release branch of SLEPc.

Thanks,
Pierre

> On 15 Mar 2024, at 3:44 PM, Zongze Yang  wrote:
> 
> This Message Is From an External Sender
> This message came from outside your organization.
> Hi,
> 
> I am currently facing an issue while attempting to install PETSc with SLEPc. 
> Despite not encountering any errors in the log generated by the 'make' 
> command, I am receiving an error message stating "Error during compile".
> 
> I would greatly appreciate it if someone could provide me with some guidance 
> on debugging this issue. 
> 
> I have attached the configure logs and make logs for both PETSc and SLEPc for 
> your reference.
> 
> Below is an excerpt from the make.log file of SLEPc:
> ```
> CLINKER default/lib/libslepc.3.020.1.dylib
> ld: warning: -commons use_dylibs is no longer supported, using error 
> treatment instead
> ld: warning: -commons use_dylibs is no longer supported, using error 
> treatment instead
> ld: warning: -commons use_dylibs is no longer supported, using error 
> treatment instead
> ld: warning: duplicate -rpath 
> '/Users/zzyang/opt/firedrake/firedrake-real-int32-debug/src/petsc/default/lib'
>  ignored
> ld: warning: dylib 
> (/opt/homebrew/Cellar/gcc/13.2.0/lib/gcc/current/libgfortran.dylib) was built 
> for newer macOS version (14.0) than being linked (12.0)
> ld: warning: dylib 
> (/opt/homebrew/Cellar/gcc/13.2.0/lib/gcc/current/libquadmath.dylib) was built 
> for newer macOS version (14.0) than being linked (12.0)
>DSYMUTIL default/lib/libslepc.3.020.1.dylib
> gmake[6]: Leaving directory 
> '/Users/zzyang/opt/firedrake/firedrake-real-int32-debug/src/petsc/default/externalpackages/git.slepc'
> gmake[5]: Leaving directory 
> '/Users/zzyang/opt/firedrake/firedrake-real-int32-debug/src/petsc/default/externalpackages/git.slepc'
> ***ERROR
>  Error during compile, check default/lib/slepc/conf/make.log
>  Send all contents of ./default/lib/slepc/conf to slepc-ma...@upv.es 
> 
> 
> Finishing make run at 五, 15  3 2024 21:04:17 +0800
> ```
> 
> Thank you very much for your attention and support.
> 
> Best wishes,
> Zongze
> 
> 

Re: [petsc-users] MATSETVALUES: Fortran problem

[Matthew Knepley]

On Fri, Mar 15, 2024 at 9:55 AM Frank Bramkamp  wrote:

> Dear PETSc Team, I am using the latest petsc version 3. 20. 5. I would
> like to create a matrix using MatCreateSeqAIJ To insert values, I use
> MatSetValues. It seems that the Fortran interface/stubs are missing for
> MatsetValues, as the linker does
> ZjQcmQRYFpfptBannerStart
> This Message Is From an External Sender
> This message came from outside your organization.
>
> ZjQcmQRYFpfptBannerEnd
>
> Dear PETSc Team,
>
> I am using the latest petsc version 3.20.5.
>
>
> I would like to create a matrix using
> MatCreateSeqAIJ
>
> To insert values, I use MatSetValues.
> It seems that the Fortran interface/stubs are missing for MatsetValues, as 
> the linker does not find any subroutine with that name.
> MatSetValueLocal seems to be fine.
>
>
Here is a Fortran example calling MatSetValues():


https://urldefense.us/v3/__https://gitlab.com/petsc/petsc/-/blob/main/src/ksp/ksp/tutorials/ex1f.F90?ref_type=heads__;!!G_uCfscf7eWS!ag7gfsg4qE_beGvp2_VPt5PyN1bZcFr8xkVlbukEpUnqYHx_awYDepWWZfT-7rtVF5-lHC2GXj1ETtSIaOLc$
 


> Typically I am using a blocked matrix format (BAIJ), which works fine in 
> fortran.
> Soon we want to try PETSC on GPUs, using the format MATAIJCUSPARSE, since 
> there seems not to be a blocked format available in PETSC for GPUs so far.
>
> You can use the blocked input API, like MatSetValuesBlocked(), with all
the storage formats. There is no explicit blocking in the MATAIJCUSPARSE format
because Nvidia handles the optimization differently.

  Thanks,

 Matt

Therefore I first want to try the pointwise format MatCreateSeqAIJ
format on a CPU, before using the GPU format.
>
> I think that CUDA also supports a block format now ?! Maybe that would be 
> also useful to have one day.
>
>
> Greetings, Frank Bramkamp
>
>
>
>
>
>
>
>

-- 
What most experimenters take for granted before they begin their
experiments is infinitely more interesting than any results to which their
experiments lead.
-- Norbert Wiener

https://urldefense.us/v3/__https://www.cse.buffalo.edu/*knepley/__;fg!!G_uCfscf7eWS!ag7gfsg4qE_beGvp2_VPt5PyN1bZcFr8xkVlbukEpUnqYHx_awYDepWWZfT-7rtVF5-lHC2GXj1ETryTqsT3$
  

Re: [petsc-users] MATSETVALUES: Fortran problem

[Barry Smith]

> On Mar 15, 2024, at 9:53 AM, Frank Bramkamp  wrote:
> 
> This Message Is From an External Sender
> This message came from outside your organization.
> Dear PETSc Team,
> 
> I am using the latest petsc version 3.20.5.
> 
> 
> I would like to create a matrix using
> MatCreateSeqAIJ
> 
> To insert values, I use MatSetValues.
> It seems that the Fortran interface/stubs are missing for MatsetValues, as 
> the linker does not find any subroutine with that name.
> MatSetValueLocal seems to be fine.

   Please send the exact error message (cut and paste), there are definitely 
Fortran stubs for this function but it could be you exact parameter input does 
not have a stub yet.

   Barry

> 
> 
> Typically I am using a blocked matrix format (BAIJ), which works fine in 
> fortran.
> Soon we want to try PETSC on GPUs, using the format MATAIJCUSPARSE, since 
> there seems not to be a blocked format available in PETSC for GPUs so far.
> Therefore I first want to try the pointwise format MatCreateSeqAIJ format on 
> a CPU, before using the GPU format.
> 
> I think that CUDA also supports a block format now ?! Maybe that would be 
> also useful to have one day.
> 
> 
> Greetings, Frank Bramkamp
> 
> 
> 
> 
> 
> 
> 

[petsc-users] MATSETVALUES: Fortran problem

[Frank Bramkamp]

 Dear PETSc Team, I am using the latest petsc version 3. 20. 5. I would like to create a matrix using MatCreateSeqAIJ To insert values, I use MatSetValues. It seems that the Fortran interface/stubs are missing for MatsetValues, as the linker does




ZjQcmQRYFpfptBannerStart




  

  
	This Message Is From an External Sender
  
  
This message came from outside your organization.
  



 
  


ZjQcmQRYFpfptBannerEnd




Dear PETSc Team,

I am using the latest petsc version 3.20.5.


I would like to create a matrix using
MatCreateSeqAIJ

To insert values, I use MatSetValues.
It seems that the Fortran interface/stubs are missing for MatsetValues, as the linker does not find any subroutine with that name.
MatSetValueLocal seems to be fine.


Typically I am using a blocked matrix format (BAIJ), which works fine in fortran.
Soon we want to try PETSC on GPUs, using the format MATAIJCUSPARSE, since there seems not to be a blocked format available in PETSC for GPUs so far.
Therefore I first want to try the pointwise format MatCreateSeqAIJ format on a CPU, before using the GPU format.

I think that CUDA also supports a block format now ?! Maybe that would be also useful to have one day.


Greetings, Frank Bramkamp