Re: [petsc-users] Configuration error during OpenBLAS

2020-07-31 Thread Eda Oktay
Dear Satish, Thank you so much for your replies. I installed git and I was able to configure PETSc. Thanks again! Eda Satish Balay , 30 Tem 2020 Per, 18:32 tarihinde şunu yazdı: > > On Thu, 30 Jul 2020, Eda Oktay wrote: > > > Dear Satish, > > > > I am sorry but I couldn't understand what

Re: [petsc-users] Configuration error during OpenBLAS

2020-07-30 Thread Satish Balay via petsc-users
On Thu, 30 Jul 2020, Eda Oktay wrote: > Dear Satish, > > I am sorry but I couldn't understand what should I do. Am I getting this > error because of case insensitivity? Its a bug in configure. I sent the fix [diff - 2 different fixes, you can try any one of them] in a different reply. > > If

Re: [petsc-users] Configuration error during OpenBLAS

2020-07-30 Thread Eda Oktay
Dear Satish, I am sorry but I couldn't understand what should I do. Am I getting this error because of case insensitivity? If I am, why now? I mean I configured Petsc with exact same options before in 2 machines. What can be the reason? Thanks! Eda On Thu, Jul 30, 2020, 6:21 PM Satish Balay

Re: [petsc-users] Configuration error during OpenBLAS

2020-07-30 Thread Satish Balay via petsc-users
Generally we recommend using system blas/lapack Wrt: Blis - the usage is slightly complicated. It needs additional lapack So I think - if using blis - the following 2 modes might work --download-blis --download-f2cblaslapack --download-blis [system lapack] Satish On Thu, 30 Jul 2020, Victor

Re: [petsc-users] Configuration error during OpenBLAS

2020-07-30 Thread Satish Balay via petsc-users
Normally - when the name is picked up from PACKAGENAME.py - and it can be overwritten by - for ex: diff --git a/config/BuildSystem/config/packages/openblas.py b/config/BuildSystem/config/packages/openblas.py index 97fd5da67e..2f65b94fde 100644 ---

Re: [petsc-users] Configuration error during OpenBLAS

2020-07-30 Thread Victor Eijkhout
On , 2020Jul30, at 07:17, Matthew Knepley mailto:knep...@gmail.com>> wrote: Shouldn't we be Be recommending Blis instead of OpenBlas? Victor.

Re: [petsc-users] Configuration error during OpenBLAS

2020-07-30 Thread Matthew Knepley
Satish, Shouldn't we be checking in a case insensitive way, or do we want case sensitivity here? Looking for OPENBLAS at git.openblas, hg.openblas or a directory starting with ['openblas'] Could not locate an existing copy of OPENBLAS:

Re: [petsc-users] configuration error

2017-10-31 Thread Satish Balay
I've already replied to this issue Try a fresh build - and do not reuse --prefix for different version builds. Have you tried doing this? Satish On Tue, 31 Oct 2017, Manav Bhatia wrote: > Thanks, Barry. > > Does this also address the mumps compilation issue that I had shared in the > same

Re: [petsc-users] configuration error

2017-10-31 Thread Manav Bhatia
Thanks, Barry. Does this also address the mumps compilation issue that I had shared in the same thread: mumps_c.c:307:53: error: no member named 'nnz' in 'CMUMPS_STRUC_C'; did you mean 'nz'? mumps_par->n=0; mumps_par->nz=0; mumps_par->nnz=0; mumps_par->nz_loc=0;

Re: [petsc-users] configuration error

2017-10-31 Thread Smith, Barry F.
Manav, Thanks for reporting the problem Fande, Thanks for the pointer. Satish determined the correct long term fix and it is in the branch barry/fix-lto_library-option-maint and will be put in the maint branch and master branch if it passes the testing tonight. Barry

Re: [petsc-users] configuration error

2017-10-30 Thread Satish Balay
The compiler library detection code is a bit messy. Its there to help with interlanguage linking. One workarround [to such failures] is to tell configure not to guess, and specify the relavent info. For eg: balay@ipro^~/petsc(master) $ ./configure --download-mpich --download-hypre CC=clang

Re: [petsc-users] configuration error

2017-10-30 Thread Satish Balay
--prefix=/Users/manav/Documents/codes/numerical_lib/petsc/petsc-3.8.0/../ You have a strange prefix. You are basically using: --prefix=/Users/manav/Documents/codes/numerical_lib/petsc The general convention is to use a different prefix for different versions of libraries [or different type of

Re: [petsc-users] configuration error

2017-10-30 Thread Manav Bhatia
I am not getting errors with mumps (please see below). Interestingly, I just compiled this on another machine with clang-3.8 and gfortran-6.7 without problems. -Manav mumps_c.c:307:53: error: no member named 'nnz' in 'CMUMPS_STRUC_C'; did you mean 'nz'? mumps_par->n=0;

Re: [petsc-users] configuration error

2017-10-30 Thread Manav Bhatia
Fande, I made the change you recommended and it seems to have moved past that stage in the configuration. Thanks for your help! Regards, Manav > On Oct 30, 2017, at 11:36 AM, Kong, Fande wrote: > > We had exactly the same issue when upgraded compilers. I guess

Re: [petsc-users] configuration error

2017-10-30 Thread Kong, Fande
We had exactly the same issue when upgraded compilers. I guess this is somehow related to gfortran. A simple way to work around for us is to change* if with_rpath*: to * if False *at line 54 of config/BuildSystem/config/libraries.py. Not sure if it works for you. Fande, On Mon, Oct 30,

[petsc-users] configuration error on Windows with VS2005

2011-11-16 Thread Satish Balay
Please send the corresponding configure.log to petsc-maint at mcs.anl.gov Satish On Wed, 16 Nov 2011, Yixun Liu wrote: Hi, I have a configuration error as I install PETSc. According to the installation instructions, I first *Setup cygwin bash shell with Working Compilers:* C:\Program