[petsc-users] Problem about compiling PETSc-3.21.2 under Cygwin

[Barry Smith]

  What do 

file /cygdrive/e/Major/Codes/libraries/PETSc/petsc-3.21.2/lib/petsc/conf/rules_doc.mk

and

file /cygdrive/e/Major/Codes/libraries/PETSc/petsc-3.21.2/lib/petsc/conf/rules_util.mk

return?


> On Jun 25, 2024, at 9:59 AM, Gang Li <ligang0309 at gmail.com> wrote:
> 
> Hi Barry,
> 
> It is: 
> Administrator at YC-20210717DLFI /cygdrive/e/Major/Codes/libraries/PETSc/petsc-3.21.2
> $ ls /cygdrive/e/Major/Codes/libraries/PETSc/petsc-3.21.2/lib/petsc/conf
> bfort-base.txt bfort-petsc.txt rules rules_util.mk uncrustify.cfg
> bfort-mpi.txt petscvariables rules_doc.mk test variables
> 
> Sincerely,
> Gang
> ---- Replied Message ----
> From	Barry Smith<bsmith at petsc.dev> <mailto:undefined>
> Date	6/25/2024 21:13
> To	Gang Li<ligang0309 at gmail.com> <mailto:ligang0309 at gmail.com>
> Cc	petsc-users<petsc-users at mcs.anl.gov> <mailto:petsc-users at mcs.anl.gov>
> Subject	Re: [petsc-users] Problem about compiling PETSc-3.21.2 under Cygwin
> 
>   Please do
> 
> ls /cygdrive/e/Major/Codes/libraries/PETSc/petsc-3.21.2/lib/petsc/conf
> 
> and send the results
> 
> 
> 
>> On Jun 25, 2024, at 4:44 AM, Gang Li <ligang0309 at gmail.com <mailto:ligang0309 at gmail.com>> wrote:
>> 
>> This Message Is From an External Sender
>> This message came from outside your organization.
>> Hi Barry and Satish,
>> 
>> Thanks for your help.
>>  
>> The same error when I restart this build using a fresh tarball.
>> See the attached file for details. 
>> 
>> Sincerely,
>> Gang
>> ---- Replied Message ----
>> From	Satish Balay<balay.anl at fastmail.org> <mailto:undefined>
>> Date	6/25/2024 00:11
>> To	Barry Smith<bsmith at petsc.dev> <mailto:bsmith at petsc.dev>
>> Cc	Gang Li<ligang0309 at gmail.com>,
>>  <mailto:ligang0309 at gmail.com>petsc-users at mcs.anl.gov<petsc-users at mcs.anl.gov> <mailto:petsc-users at mcs.anl.gov>
>> Subject	Re: [petsc-users] Problem about compiling PETSc-3.21.2 under Cygwin
>> Probably best if you can restart this build using a fresh tarball - and see if the problem persists
>> 
>> Satish
>> 
>> On Mon, 24 Jun 2024, Barry Smith wrote:
>> 
>> 
>> Do
>> 
>> ls /cygdrive/e/Major/Codes/libraries/PETSc/petsc-3.21.2/lib/petsc/conf/
>> 
>> 
>> 
>> 
>> On Jun 23, 2024, at 8:27 AM, Gang Li <ligang0309 at gmail.com <mailto:ligang0309 at gmail.com>> wrote:
>> 
>> This Message Is From an External Sender
>> This message came from outside your organization.
>> Hi,
>> 
>> I have configured the PETSc under Cygwin by:
>> 
>> cygpath -u `cygpath -ms '/cygdrive/c/Program Files (x86)/IntelSWTools/compilers_and_libraries/windows/mkl/lib/intel64'`
>> ./configure --with-cc='win32fe_icl' --with-fc='win32fe_ifort' --with-cxx='win32fe_icl' \
>> --with-precision=double --with-scalar-type=complex \
>> --with-shared-libraries=0 \
>> --with-mpi=0 \
>> --with-blaslapack-lib='-L/cygdrive/c/PROGRA~2/INTELS~1/COMPIL~2/windows/mkl/lib/intel64 mkl_intel_lp64.lib mkl_sequential.lib mkl_core.lib'
>> 
>> It seems to be successful. When make it, I faced a problem:
>> 
>> $ make PETSC_DIR=/cygdrive/e/Major/Codes/libraries/PETSc/petsc-3.21.2 PETSC_ARCH=arch-mswin-c-debug all
>> /usr/bin/python3 ./config/gmakegen.py --petsc-arch=arch-mswin-c-debug
>> makefile:25: /cygdrive/e/Major/Codes/libraries/PETSc/petsc-3.21.2/lib/petsc/conf
>> /rules_util.mk: No such file or directory
>> gmake[1]: *** No rule to make target '/cygdrive/e/Major/Codes/libraries/PETSc/pe
>> tsc-3.21.2/lib/petsc/conf/rules_util.mk'. Stop.
>> make: *** [GNUmakefile:9: all] Error 2
>> 
>> Could you help to check it?
>> Thanks.
>> 
>> Gang Li
>> 
>> 
>> 
>> 
>> <configure.log><gmake.log>
>> 
>> 
>> <error.jpg>
> 

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.mcs.anl.gov/pipermail/petsc-users/attachments/20240625/2d946dac/attachment-0001.html>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: ls.jpg
Type: image/jpeg
Size: 18653 bytes
Desc: not available
URL: <http://lists.mcs.anl.gov/pipermail/petsc-users/attachments/20240625/2d946dac/attachment-0001.jpg>