<div dir="ltr"><div class="gmail_quote"><div dir="ltr">On Sun, Sep 2, 2018 at 11:11 AM Antonio <<a href="mailto:anto.trande@gmail.com">anto.trande@gmail.com</a>> wrote:<br></div><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"> --with-blas-lapack-lib=-lopenblas --known-64-bit-blas-indices=0<br></blockquote><div><br></div><div>I am curious why you are giving the 64-bit option. This should be figured automatically unless</div><div>you cannot executable programs on the platform on which you are configuring. What goes wrong?</div><div><br></div><div>  Thanks,</div><div><br></div><div>     Matt</div><div> </div><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
is working.<br>
<br>
Thanks.<br>
<br>
On 31/08/2018 20:11, Satish Balay wrote:<br>
> It should work. configure.log will have details..<br>
> <br>
> Satish<br>
> <br>
> ----------<br>
> <br>
> balay@asterix /home/balay/petsc (maint=)<br>
> $ ./configure --with-blaslapack-lib=-lopenblas<br>
> ===============================================================================<br>
>              Configuring PETSc to compile on your system                       <br>
> ===============================================================================<br>
> ===============================================================================                                                                                        It appears you do not have valgrind installed on your system.                                                                                                    We HIGHLY recommend you install it from <a href="http://www.valgrind.org" rel="noreferrer" target="_blank">www.valgrind.org</a>                                                                                                         Or install valgrind-devel or equivalent using your package manager.                                                                                              Then rerun ./configure                                                                                                                                     ===============================================================================                                                                                  Compilers:                                                                                                                                                       <br>
>   C Compiler:         mpicc    -Wall -Wwrite-strings -Wno-strict-aliasing -Wno-unknown-pragmas -fstack-protector -fvisibility=hidden -g3 <br>
>   C++ Compiler:       mpicxx  -Wall -Wwrite-strings -Wno-strict-aliasing -Wno-unknown-pragmas -fstack-protector -fvisibility=hidden -g      <br>
>   Fortran Compiler:   mpif90   -Wall -ffree-line-length-0 -Wno-unused-dummy-argument -g  <br>
> Linkers:<br>
>   Shared linker:   mpicc  -shared    -Wall -Wwrite-strings -Wno-strict-aliasing -Wno-unknown-pragmas -fstack-protector -fvisibility=hidden -g3<br>
>   Dynamic linker:   mpicc  -shared    -Wall -Wwrite-strings -Wno-strict-aliasing -Wno-unknown-pragmas -fstack-protector -fvisibility=hidden -g3<br>
> make:<br>
> BLAS/LAPACK: -lopenblas<br>
> MPI:<br>
> cmake:<br>
> X:<br>
>   Library:  -lX11<br>
> c2html:<br>
>   Arch:     <br>
> pthread:<br>
>   Library:  -lpthread<br>
> PETSc:<br>
>   PETSC_ARCH: arch-linux2-c-debug<br>
>   PETSC_DIR: /home/balay/petsc<br>
>   Scalar type: real<br>
>   Precision: double<br>
>   Clanguage: C<br>
>   Integer size: 32<br>
>   shared libraries: enabled<br>
>   Memory alignment: 16<br>
> xxx=========================================================================xxx<br>
>  Configure stage complete. Now build PETSc libraries with (gnumake build):<br>
>    make PETSC_DIR=/home/balay/petsc PETSC_ARCH=arch-linux2-c-debug all<br>
> xxx=========================================================================xxx<br>
> balay@asterix /home/balay/petsc (maint=)                                                                                                                         <br>
> $ <br>
> <br>
> <br>
> On Fri, 31 Aug 2018, Antonio wrote:<br>
> <br>
>> It's failing for missing (not required) links:<br>
>><br>
>> Executing: mpicc  -o /tmp/petsc-FYncGY/config.libraries/conftest<br>
>> -Wl,-z,relro   -fPIC  -Wall -Wwrite-strings -Wno-strict-aliasing<br>
>> -Wno-unknown-pragmas -fstack-protector -fvisibility=hidden -g3<br>
>> /tmp/petsc-FYncGY/config.libraries/conftest.o  -lsunperf -lfui -lfsu<br>
>> -lsunmath -lm -lstdc++ -ldl -L/usr/lib64/openmpi/lib -lmpi_usempif08<br>
>> -lmpi_usempi_ignore_tkr -lmpi_mpifh -lmpi -lgfortran -lm<br>
>> -L/usr/lib/gcc/x86_64-redhat-linux/8 -L/usr/lib64/openmpi/lib -lgfortran<br>
>> -lm -lgcc_s -lquadmath -lpthread -lstdc++ -ldl<br>
>> Possible ERROR while running linker: exit code 256<br>
>> stderr:<br>
>> /usr/bin/ld: cannot find -lsunperf<br>
>> /usr/bin/ld: cannot find -lfui<br>
>> /usr/bin/ld: cannot find -lfsu<br>
>> /usr/bin/ld: cannot find -lsunmath<br>
>> collect2: error: ld returned 1 exit status<br>
>>                       Popping language C<br>
>>                 Unknown name mangling in BLAS/LAPACK<br>
>>               MKL Path not found.. skipping: /cygdrive/c/Program<br>
>> Files/Intel/MKL/9.0<br>
>>               MKL Path not found.. skipping: /cygdrive/c/Program<br>
>> Files/Intel/MKL/8.1.1<br>
>>               MKL Path not found.. skipping: /cygdrive/c/Program<br>
>> Files/Intel/MKL/8.1<br>
>>               MKL Path not found.. skipping: /cygdrive/c/Program<br>
>> Files/Intel/MKL/8.0.1<br>
>>               MKL Path not found.. skipping: /cygdrive/c/Program<br>
>> Files/Intel/MKL/8.0<br>
>>               MKL Path not found.. skipping: /cygdrive/c/Program<br>
>> Files/Intel/MKL72<br>
>>               MKL Path not found.. skipping: /cygdrive/c/Program<br>
>> Files/Intel/MKL70<br>
>>               MKL Path not found.. skipping: /cygdrive/c/Program<br>
>> Files/Intel/MKL61<br>
>>               MKL Path not found.. skipping: /cygdrive/c/Program<br>
>> Files/Intel/MKL<br>
>> **** Configure header /tmp/petsc-FYncGY/confdefs.h ****<br>
>><br>
>> On 31/08/2018 19:41, Smith, Barry F. wrote:<br>
>>><br>
>>>    Ah, sorry for the confusion. We do support --download-openblas where PETSc will download and install and OpenBlas for you but if you have it already installed then you need to treat it just as a BLASLAPACK library so use<br>
>>><br>
>>><br>
>>>> --with-blaslapack-include=%{_includedir} \<br>
>>>> --with-blaslapack-lib=%{_libdir}/libopenblas.so \<br>
>>>> --known-64-bit-blas-indices=0 \<br>
>>><br>
>>>    If this fails then mail configure.log to <a href="mailto:petsc-maint@mcs.anl.gov" target="_blank">petsc-maint@mcs.anl.gov</a><br>
>>><br>
>>>     Barry<br>
>>><br>
>><br>
>><br>
<br>
-- <br>
---<br>
Antonio Trande<br>
Fedora Project<br>
mailto 'sagitter at fedoraproject dot org'<br>
GPG key: 0x5E212EE1D35568BE<br>
GPG key server: <a href="https://keys.fedoraproject.org/" rel="noreferrer" target="_blank">https://keys.fedoraproject.org/</a><br>
</blockquote></div><br clear="all"><div><br></div>-- <br><div dir="ltr" class="gmail_signature" data-smartmail="gmail_signature"><div dir="ltr"><div><div dir="ltr"><div><div dir="ltr"><div>What most experimenters take for granted before they begin their experiments is infinitely more interesting than any results to which their experiments lead.<br>-- Norbert Wiener</div><div><br></div><div><a href="http://www.cse.buffalo.edu/~knepley/" target="_blank">https://www.cse.buffalo.edu/~knepley/</a><br></div></div></div></div></div></div></div></div>