Re: [petsc-users] Warning while compiling Fortran with PETSc

Are you using the same MPI to build both PETSc and your appliation? Satish On Wed, 2022-02-09 at 05:21 +0100, Bojan Niceno wrote: > To whom it may concern, > > > I am working on a Fortran (2003) computational fluid dynamics solver, > which is actually quite mature, was parallelized with MPI

Re: [petsc-users] Solver compilation with 64-bit version of PETSc under Windows 10 using Cygwin

I would suggest installing regular 32bit int blas/lapack - And then using it with --with-blaslapack-lib option [we don't know what -fdefault-integer-8 does with --download-fblaslapack - if it really creates --known-64-bit-blas-indices variant of blas/lapack or not] Satish On Tue, 21 Jan 2020,

Re: [petsc-users] Solver compilation with 64-bit version of PETSc under Windows 10 using Cygwin

I have some changes (incomplete) here - my hack to bfort. diff --git a/src/bfort/bfort.c b/src/bfort/bfort.c index 0efe900..31ff154 100644 --- a/src/bfort/bfort.c +++ b/src/bfort/bfort.c @@ -1654,7 +1654,7 @@ void PrintDefinition( FILE *fout, int is_function, char *name, int nstrings,

Re: [petsc-users] Solver compilation with 64-bit version of PETSc under Windows 10 using Cygwin

On Wed, 15 Jan 2020, Matthew Knepley wrote: > On Wed, Jan 15, 2020 at 10:26 AM Дмитрий Мельничук < > dmitry.melnic...@geosteertech.com> wrote: > > > > And I'm not sure why you are having to use PetscInt for ierr. All PETSc > > routines should be suing 'PetscErrorCode for ierr' > > > > If I

Re: [petsc-users] Solver compilation with 64-bit version of PETSc under Windows 10 using Cygwin

-fdefault-integer-8 is likely to break things [esp with MPI - where 'integer' is used everywhere for ex - MPI_Comm etc - so MPI includes become incompatible with the MPI library with -fdefault-integer-8.] And I'm not sure why you are having to use PetscInt for ierr. All PETSc routines should

Re: [petsc-users] petsc without MPI

l_lp64 -lmkl_gnu_thread -lmkl_core " > > --with-blacs-lib=/apps/cent7/intel/compilers_and_libraries_2017.1.132/linux/mkl/lib/intel64/libmkl_blacs_intelmpi_lp64.so > > > > --with-blacs-include=/apps/cent7/intel/compilers_and_libraries_2017.1.132/linux/mkl/include > > --with-scalapac

Re: [petsc-users] petsc without MPI

-include=/apps/cent7/intel/compilers_and_libraries_2017.1.132/linux/mkl/include --with-scalapack=0 <<<<<<< And configure completed successfully. What issue are you encountering? Why do you think its activating MPI? Satish On Tue, 19 Nov 2019, Balay, Satish via pets

Re: [petsc-users] petsc without MPI

On Tue, 19 Nov 2019, Povolotskyi, Mykhailo via petsc-users wrote: > Hello, > > I'm trying to build PETSC without MPI. > > Even if I specify --with_mpi=0, the configuration script still activates > MPI. > > I attach the configure.log. > > What am I doing wrong? The option is --with-mpi=0

Re: [petsc-users] PETSc 3.12 with .f90 files

On Tue, 29 Oct 2019, Matthew Knepley via petsc-users wrote: > On Tue, Oct 29, 2019 at 2:35 PM Smith, Barry F. wrote: > > > > >The problem is that this change DOES use the preprocessor on the f90 > > file, does it not? We need a rule that does not use the preprocessor. > > > > This change

Re: [petsc-users] PETSc 3.12 with .f90 files

On Tue, 29 Oct 2019, Randall Mackie via petsc-users wrote: > Dear PETSc users: > > In our code, we have one or two small .f90 files that are part of the > software, and they have always compiled without any issues with previous > versions of PETSc, using standard PETSc make files. > >

Re: [petsc-users] anaconda installation of petsc

Likely this install is broken as mpicc [used here] is unable to find 'clang' used to built it. And we have no idea how the petsc install in anaconda works. Suggest installing PETSc from source - this is what we support if you encounter problems. Satish On Wed, 23 Oct 2019, Gideon Simpson via

[petsc-users] petsc-3.12.1.tar.gz now available

Dear PETSc users, The patch release petsc-3.12.1 is now available for download, with change list at 'PETSc-3.12 Changelog' http://www.mcs.anl.gov/petsc/download/index.html Satish

Re: [petsc-users] Compile petsc with a simple code

Try compiling a PETSc example with the corresponding PETSc makefile - to check the compile/link command that you need to use. Its best to use a PETSc formatted makefile for user code [check users manual for an example] Satish On Mon, 21 Oct 2019, Jianhua Qin via petsc-users wrote: > Hello

Re: [petsc-users] Makefile problems: environmental variables, includes paths and libraries.

On Tue, 15 Oct 2019, Matthew Agius via petsc-users wrote: > Dear PETSC users, > > This is my first attempt at PETSC package. > > First step, I think I have installed PETSC, well at least no errors. > Now I am trying to run a simple makefile as suggested in the manual > I am confused about

Re: [petsc-users] Makefile change for PETSc3.12.0???

Can you retry with this fix: https://gitlab.com/petsc/petsc/commit/3ae65d51d08dba2e118033664acfd64a46c9bf1d [You can use maint branch for it] Satish On Wed, 2 Oct 2019, Danyang Su via petsc-users wrote: > Dear All, > > I installed PETSc3.12.0 version and got problem in compiling my code

Re: [petsc-users] reproduced the problem

As the message says - you need to use configure option --with-cxx-dialect=C++11 with --download-superlu_dist [this requirement is automated in petsc/master so extra configure option is no longer required] Satish On Fri, 20 Sep 2019, Povolotskyi, Mykhailo via petsc-users wrote: > Hello

Re: [petsc-users] reproduced the problem

> TEST checkRuntimeIssues from config.packages.BlasLapack(/depot/kildisha/apps/brown/nemo5/libs/petsc/build-real3.11/config/BuildSystem/config/packages/BlasLapack.py:579) TESTING: checkRuntimeIssues from

Re: [petsc-users] question about installing petsc3.11

--with-64-bit-indices=1 => PetscInt = int64_t --known-64-bit-blas-indices=1 => blas specified uses 64bit indices. What is your requirement (use case)? Satish On Fri, 20 Sep 2019, Povolotskyi, Mykhailo via petsc-users wrote: > Does it mean I have to configure petsc with --with-64-bit-indices=1

Re: [petsc-users] [petsc-dev] IMPORTANT PETSc repository changed from Bucketbit to GitLab

On Thu, 5 Sep 2019, Balay, Satish via petsc-dev wrote: > On Thu, 22 Aug 2019, Balay, Satish via petsc-users wrote: > All, > > We now have a preliminary CI in place that can process merge requests (MRs) - > so please go ahead and submit them. We have a notice on 'Data Center Ou

Re: [petsc-users] [petsc-dev] IMPORTANT PETSc repository changed from Bucketbit to GitLab

On Thu, 22 Aug 2019, Balay, Satish via petsc-users wrote: > > > > Please do not make pull requests to the Gitlab site yet; we will be > > manually processing the PR from the BitBucket site over the next couple of > > days as we implement the testing. > &

Re: [petsc-users] configuring on OSX

On Wed, 4 Sep 2019, Balay, Satish via petsc-users wrote: > On Tue, 3 Sep 2019, Brian Van Straalen via petsc-users wrote: > > > pulling from git PETSC and on master branch. > > > > ./co

Re: [petsc-users] configuring on OSX

On Tue, 3 Sep 2019, Brian Van Straalen via petsc-users wrote: > pulling from git PETSC and on master branch. > > ./configure CPP=/usr/bin/cpp > === > Configuring PETSc to compile on your system > >

Re: [petsc-users] petsc on windows

Thanks for the update. Yes - having the wrong variant of libpetsc.dll in PATH can cause problems. Satish On Fri, 30 Aug 2019, Sam Guo via petsc-users wrote: > Thanks a lot for your help. It is my pilot error: I have both serial > version and parallel version of petstc. It turns out serial

Re: [petsc-users] petsc on windows

On MS-Windows - you need the location of the DLLs in PATH Or use --with-shared-libraries=0 Satish On Thu, 29 Aug 2019, Sam Guo via petsc-users wrote: > When I use intel mpi, configuration, compile and test all work fine but I > cannot use dll in my application. > > On Thu, Aug 29, 2019 at

Re: [petsc-users] petsc on windows

On Thu, 29 Aug 2019, Sam Guo via petsc-users wrote: > I can link when I add my wrapper to > PCC_LINKER_FLAGS =-MD -wd4996 -Z7 > /home/xianzhongg/dev/star/lib/win64/intel18.3vc14/lib/StarMpiWrapper.lib I don't understand what you mean here. Add PCC_LINKER_FLAGS to where? This is a variable

Re: [petsc-users] Unable to compile super_dist using an intel compiler

attached zip file has the same/old configure.log Can you use PETSC_ARCH=arch-test - so that the old build files are not reused, and resend the new configure.log Satish On Tue, 27 Aug 2019, Fande Kong via petsc-users wrote: > No, I hit exactly the same error using your script. > > Thanks, > >

Re: [petsc-users] Unable to compile super_dist using an intel compiler

On Tue, 27 Aug 2019, Fande Kong via petsc-users wrote: > Hi All, > > I was trying to compile PETSc with "--download-superlu_dist" using an intel > compiler. I have explored with different options, but did not get PETSc > built successfully so far. Any help would be appreciated. > > The log file

Re: [petsc-users] errors when using elemental with petsc3.10.5

On Fri, 23 Aug 2019, Smith, Barry F. via petsc-users wrote: > bsmith@es:~$ ldd /usr/lib/libparmetis.so.3.1 > linux-vdso.so.1 => (0x7fff9115e000) > libmpi.so.1 => /usr/lib/libmpi.so.1 (0x7faf95f87000) > libm.so.6 => /lib/x86_64-linux-gnu/libm.so.6 (0x7faf95c81000) >

Re: [petsc-users] errors when using elemental with petsc3.10.5

In general you never want to install external software such as > parmetis, PETSc, MPI, etc in systems directories (/usr/ and /usr/local) > > You should delete this library (and the includes in /usr/include) > > Barry > > > > > > On Aug 22, 2019, at 5:17 PM, B

Re: [petsc-users] errors when using elemental with petsc3.10.5

> ./ex19: symbol lookup error: /usr/lib/libparmetis.so: undefined symbol: > ompi_mpi_comm_world For some reason the wrong parmetis library is getting picked up. I don't know why. Can you copy/paste the log from the following? cd src/snes/examples/tutorials make

Re: [petsc-users] errors when using elemental with petsc3.10.5

Any reason for using petsc-3.10.5 and not latest petsc-3.11? I suggest starting from scatch and rebuilding. And if you still have issues - send corresponding configure.log and make.log Satish On Thu, 22 Aug 2019, Lailai Zhu via petsc-users wrote: > sorry, Satish, > > but it does not seem to

Re: [petsc-users] [petsc-dev] IMPORTANT PETSc repository changed from Bucketbit to GitLab

On Mon, 19 Aug 2019, Smith, Barry F. via petsc-dev wrote: > > >PETSc folks. > > This announcement is for people who access PETSc from the BitBucket > repository or post issues or have other activities with the Bitbucket > repository > >We have changed the location of the PETSc

Re: [petsc-users] errors when using elemental with petsc3.10.5

Can you run 'make' again and see if this error goes away? Satish On Wed, 21 Aug 2019, Lailai Zhu via petsc-users wrote: > hi, Satish, > i tried to do it following your suggestion, i get the following errors when > installing. > here is my configuration, > > any ideas? > > best, > lailai > >

Re: [petsc-users] errors when using elemental with petsc3.10.5

To install elemental - you use: --download-elemental=1 [not --download-elemental-commit=v0.87.7] Satish On Wed, 21 Aug 2019, Lailai Zhu via petsc-users wrote: > hi, dear petsc developers, > > I am having a problem when using the external solver elemental. > I installed petsc3.10.5 version

Re: [petsc-users] [petsc-dev] IMPORTANT PETSc repository changed from Bucketbit to GitLab

A note: The bitbucket repository is saved at https://bitbucket.org/petsc/petsc-pre-gitlab The git part is now read-only. The other parts [issues, PRs, wiki etc] are perhaps writable - but we should avoid that. Satish On Mon, 19 Aug 2019, Smith, Barry F. via petsc-dev wrote: > > >

Re: [petsc-users] When building PETSc with --prefix, reference to temporary build directory remains

On Thu, 1 Aug 2019, Smith, Barry F. via petsc-users wrote: > > Please consider upgrading to the latest PETSc 3.11 it has many new features > and fewer bugs etc. > > > 5. From now on set PETSC_DIR=/readonly PETSC_ARCH='' > > step 4 moves the compiled PETSc to /readonly/ and it works, but when

[petsc-users] petsc-3.11.3.tar.gz now available

Dear PETSc users, The patch release petsc-3.11.3 is now available for download, with change list at 'PETSc-3.11 Changelog' http://www.mcs.anl.gov/petsc/download/index.html Satish

Re: [petsc-users] ERROR_WITH_EXAMPLE_BUILD

Can you send configure.log, make.log for this build? Also copy/paste complete output from the 'make' command below. Satish On Sat, 15 Jun 2019, govind sharma via petsc-users wrote: > Hello, > > I am trying to build one example of tutorial on snes with following command > "make

Re: [petsc-users] Configuration process of Petsc hanging

PETSc configure is attempting to run some MPI binaries - and that is hanging with this MPI. You can retry with the options: --batch=1 --known-64-bit-blas-indices=0 -known-mpi-shared-libraries=0 [and follow instructions provided by configure] Satish On Fri, 31 May 2019, Ma, Xiao via

Re: [petsc-users] How do I supply the compiler PIC flag via CFLAGS, CXXXFLAGS, and FCFLAGS

Configure.log shows '--with-pic=1' - hence this error. Remove '--with-pic=1' and retry. Saitsh On Tue, 28 May 2019, Inge Gutheil via petsc-users wrote: > Dear PETSc list, > when I try to install the petsc-3.11.2 library as a static library - for > some reasons I do not want the dynamic library

Re: [petsc-users] With-batch (new) flags

I'm not yet sure what the correct fix is - but the following change should get this going.. diff --git a/config/BuildSystem/config/packages/BlasLapack.py b/config/BuildSystem/config/packages/BlasLapack.py index e0310da4b0..7355f1a369 100644 --- a/config/BuildSystem/config/packages/BlasLapack.py

Re: [petsc-users] With-batch (new) flags

for ex: ilp version of mkl is --known-64-bit-blas-indices=1 while lp mkl is --known-64-bit-blas-indices=0 Default blas we normally use is --known-64-bit-blas-indices=0 [they don't use 64bit indices] Satish On Mon, 20 May 2019, Mark Adams via petsc-users wrote: > We are getting this failure.

[petsc-users] petsc-3.11.2.tar.gz now available

Dear PETSc users, The patch release petsc-3.11.2 is now available for download, with change list at 'PETSc-3.11 Changelog' http://www.mcs.anl.gov/petsc/download/index.html Satish

Re: [petsc-users] ``--with-clanguage=c++" turns on "PETSC_HAVE_COMPLEX"?

On Fri, 3 May 2019, Fande Kong via petsc-users wrote: > On Fri, May 3, 2019 at 8:02 PM Balay, Satish wrote: > > > On Fri, 3 May 2019, Fande Kong via petsc-users wrote: > > > > > It looks like mpicxx from openmpi does not handle this correctly. > > > > Perhaps my earlier messages was not clear.

Re: [petsc-users] ``--with-clanguage=c++" turns on "PETSC_HAVE_COMPLEX"?

On Fri, 3 May 2019, Fande Kong via petsc-users wrote: > It looks like mpicxx from openmpi does not handle this correctly. Perhaps my earlier messages was not clear. The problem is not with OpenMPI - but your build of it. Its installed with 'clang' as the C++ compiler - it should be built with

Re: [petsc-users] ``--with-clanguage=c++" turns on "PETSC_HAVE_COMPLEX"?

Executing: mpicxx -show stdout: clang -I/Users/kongf/projects/openmpi-2.1.1_installed/include

Re: [petsc-users] Iterative solver behavior with increasing number of mpi

Yes - the default preconditioner is block-jacobi - with one block on each processor. So when run on 1 proc vs 8 proc - the preconditioner is different (with 1block for bjacobi vs 8blocks for bjacobi)- hence difference in convergence. Satish On Wed, 17 Apr 2019, Marian Greg via petsc-users

Re: [petsc-users] VecView to hdf5 broken for large (complex) vectors

On Wed, 17 Apr 2019, Smith, Barry F. via petsc-users wrote: > This is fine for "hacking" on PETSc but worthless for any other package. > Here is my concern, when someone > realizes there is a problem with a package they are using through a package > manager they think, crud I have to > > 1)

Re: [petsc-users] VecView to hdf5 broken for large (complex) vectors

On Wed, 17 Apr 2019, Satish Balay wrote: > Its not ideal - but having local changes in our spack clones (change > git url, add appropriate version lines to branches that one is > working on) is possible [for a group working in this mode]. [balay@pj03 petsc]$ pwd /home/balay/petsc [balay@pj03

Re: [petsc-users] VecView to hdf5 broken for large (complex) vectors

On Wed, 17 Apr 2019, Smith, Barry F. wrote: > > So it sounds like spack is still mostly a "package manager" where people > use "static" packages and don't hack the package's code. This is not > unreasonable, no other package manager supports hacking a package's code > easily, presumably.

Re: [petsc-users] VecView to hdf5 broken for large (complex) vectors

On Tue, 16 Apr 2019, Sajid Ali via petsc-users wrote: > > develop > 3.11.99 > 3.10.xx > maint (or other strings) > Just discovered this issue when trying to build with my fork of spack at [1 > ]. > > > So,

Re: [petsc-users] VecView to hdf5 broken for large (complex) vectors

On Wed, 17 Apr 2019, Balay, Satish via petsc-users wrote: > On Tue, 16 Apr 2019, Smith, Barry F. wrote: > > > > > > > > On Apr 16, 2019, at 10:30 PM, Sajid Ali > > > wrote: > > > > > > @Barry: Thanks for the bugfix! > > > >

Re: [petsc-users] VecView to hdf5 broken for large (complex) vectors

On Tue, 16 Apr 2019, Smith, Barry F. wrote: > > > > On Apr 16, 2019, at 10:30 PM, Sajid Ali > > wrote: > > > > @Barry: Thanks for the bugfix! > > > > @Satish: Thanks for pointing out this method! > > > > My preferred way previously was to download the source code, unzip, edit, > > zip.

Re: [petsc-users] VecView to hdf5 broken for large (complex) vectors

On Tue, 16 Apr 2019, Sajid Ali wrote: > Lately, spack has added git support and now I create a branch of > spack where I add my bugfix branch as the default build git repo instead of > master to now deal with checksum headaches. Some good and bad here.. version('develop', branch='master')

Re: [petsc-users] VecView to hdf5 broken for large (complex) vectors

On Wed, 17 Apr 2019, Smith, Barry F. via petsc-users wrote: > > Funny you should ask, I just found the bug. > > > On Apr 16, 2019, at 9:47 PM, Sajid Ali > > wrote: > > > > Quick question : To drop a print statement at the required location, I need > > to modify the source code, build

Re: [petsc-users] Link broken for: PETSc users manual - pdf (fully searchable with hyperlinks)

Looks like the manual didn't get generated correctly for petsc-3.11.1. For now - I've restored the 3.11 manual - so the URL should work now. Satish On Mon, 15 Apr 2019, Xiang Huang via petsc-users wrote: > http://www.mcs.anl.gov/petsc/petsc-current/docs/manual.pdf > > Error 404 > The web

[petsc-users] petsc-3.11.1.tar.gz now available

Dear PETSc users, The patch release petsc-3.11.1 is now available for download, with change list at 'PETSc-3.11 Changelog' http://www.mcs.anl.gov/petsc/download/index.html Satish

Re: [petsc-users] How to build FFTW3 interface?

Great! The change is now in spack 'develop' branch. Satish On Fri, 12 Apr 2019, Sajid Ali via petsc-users wrote: > Hi Balay, > > Confirming that the spack variant works. Thanks for adding it. >

Re: [petsc-users] How to build FFTW3 interface?

On Thu, 11 Apr 2019, Sajid Ali via petsc-users wrote: > Hi PETSc Developers, > > To run an example that involves the petsc-fftw interface, I loaded both > petsc and fftw modules (linked of course to the same mpi) but the compiler > complains of having no knowledge of functions like

Re: [petsc-users] Problem coupling Petsc into OpenFOAM

Runtime error? You might have to add the path to $PETSC_ARCH/lib in LD_LIBRARY_PATH env variable or - to your link command. If linux/gcc - the linker option is -Wl,-rpath,$PETSC_ARCH/lib If not - send detail logs. Satish On Wed, 10 Apr 2019, Vu Do Quoc via petsc-users wrote: > Hi all, > >

Re: [petsc-users] Error with parallel solve

On Mon, 8 Apr 2019, Manav Bhatia via petsc-users wrote: > > > > On Apr 8, 2019, at 2:19 PM, Stefano Zampini > > wrote: > > > > You can circumvent the problem by using a sequential solver for it. There's > > a command line option in petsc as well as API that allows you to do so. > >

Re: [petsc-users] Error with parallel solve

https://github.com/spack/spack/pull/11132 If this works - please add a comment on the PR Satish On Mon, 8 Apr 2019, Balay, Satish via petsc-users wrote: > spack update to use mumps-5.1.2 - with this patch is in branch > 'balay/mumps-5.1.2' > > Satish > > On Mon, 8 Apr

Re: [petsc-users] Error with parallel solve

spack update to use mumps-5.1.2 - with this patch is in branch 'balay/mumps-5.1.2' Satish On Mon, 8 Apr 2019, Satish Balay wrote: > Yes - mumps via spack is unlikely to have this patch - but it can be added. > >

Re: [petsc-users] Strange compiling error in DMPlexDistribute after updating PETSc to V3.11.0

I'm off base > > here.. > > > > Satish > > > > > > On Fri, 5 Apr 2019, Balay, Satish via petsc-users wrote: > > > >> A fortran interface definition was added in petsc-3.11 so the compile now > >> checks if its used cor

Re: [petsc-users] Strange compiling error in DMPlexDistribute after updating PETSc to V3.11.0

Ah - the message about distributed_dm - not PETSC_NULL_SF. So I'm off base here.. Satish On Fri, 5 Apr 2019, Balay, Satish via petsc-users wrote: > A fortran interface definition was added in petsc-3.11 so the compile now > checks if its used correctly. > > http://bitbucket.org

Re: [petsc-users] Strange compiling error in DMPlexDistribute after updating PETSc to V3.11.0

A fortran interface definition was added in petsc-3.11 so the compile now checks if its used correctly. http://bitbucket.org/petsc/petsc/commits/fdb49207a8b58c421782c7e45b1394c0a6567048 + PetscSF, intent(out) :: sf So this should be inout? [All auto-generated stubs don't quantify

Re: [petsc-users] 3.11 configure error on pleiades

Hm - with-mpi-exec is wrong and ignored - but configure should default to 'mpiexec' from PATH anyway. It would be good to check configure.log for details on this error. Satish On Sat, 30 Mar 2019, Matthew Knepley via petsc-users wrote: > On Sat, Mar 30, 2019 at 4:31 PM Kokron, Daniel S.

Re: [petsc-users] 3.11 configure error on pleiades

configure creates configure.log with all the debugging details. Its best to compare configure.log from the successful 3.8.3 with the current one - and see what changed between these 2 builds [you can send us both logs at petsc-maint] Satish On Sat, 30 Mar 2019, Kokron, Daniel S.

Re: [petsc-users] [Ext] Re: error: identifier "MatCreateMPIAIJMKL" is undefined in 3.10.4

Please apply the patch I sent earlier and retry. Satish On Tue, 26 Mar 2019, Kun Jiao via petsc-users wrote: > Strange things, when I compile my code in the test dir in PETSC, it works. > After I "make install" PETSC, and try to compile my code against the > installed PETSC, it doesn't work

Re: [petsc-users] [Ext] Re: error: identifier "MatCreateMPIAIJMKL" is undefined in 3.10.4

>>> balay@sb /home/balay/petsc (maint=) $ git grep MatCreateMPIAIJMKL maint-3.8 maint-3.8:src/mat/impls/aij/mpi/aijmkl/mpiaijmkl.c: MatCreateMPIAIJMKL - Creates a sparse parallel matrix whose local maint-3.8:src/mat/impls/aij/mpi/aijmkl/mpiaijmkl.c:PetscErrorCode

Re: [petsc-users] Valgrind Issue With Ghosted Vectors

I see you are using " 0e667e8fea4aa from December 23rd" - which is old petsc 'master' snapshot. 1. After your fix for 'bad input file' - do you still get these valgrind messages? 2. You should be able to easily apply Stefano's potential fix to your snapshot [without upgrading to latest petsc].

Re: [petsc-users] About Configuring PETSc

Did you build PETSc with PETSC_ARCH=arch-opt? Btw - I used PETSC_ARCH=arch-debug to illustrate - but you already have a build with PETSC_ARCH=arch-linux2-c-debug - so you should stick to that. Satish On Fri, 22 Mar 2019, Maahi Talukder via petsc-users wrote: > Hi, > > I tried to run the

Re: [petsc-users] About Configuring PETSc

On Thu, 21 Mar 2019, Maahi Talukder via petsc-users wrote: > Thank you for your reply. > > So do I need to set the value of PETSC_ARCH as needed in .bashrc as I did > in case of PETSC_DIR ? You can specify PETSC_ARCH as an option to make. You can have a default value set in .bashrc - and

Re: [petsc-users] About Configuring PETSc

PETSc uses the concept of PETSC_ARCH to enable multiple in-place builds. So you can have a debug build with PETSC_ARCH=arch-debug, and a optimized build with PETSC_ARCH=arch-opt etc. And if you are using a petsc formatted makefile with your code - you can switch between these builds by just

Re: [petsc-users] Valgrind Issue With Ghosted Vectors

Ok - cherrypicked and pushed to maint. Satish On Thu, 21 Mar 2019, Zhang, Junchao via petsc-users wrote: > Yes, it does. It is a bug. > --Junchao Zhang > > > On Thu, Mar 21, 2019 at 11:16 AM Balay, Satish > mailto:ba...@mcs.anl.gov>> wrote: > Does maint also need this fix? > > Satish > >

Re: [petsc-users] Valgrind Issue With Ghosted Vectors

Does maint also need this fix? Satish On Thu, 21 Mar 2019, Stefano Zampini via petsc-users wrote: > Derek > > I have fixed the optimized plan few weeks ago > > https://bitbucket.org/petsc/petsc/commits/c3caad8634d376283f7053f3b388606b45b3122c > > Maybe this will fix your problem too? > >

Re: [petsc-users] Cross-compilation cluster

As these warnings indicate - 64bit compiler ignores 32bit libraries [so they don't get used]. i.e mixing 32bit and 64bit libraries ins not the cause of your problems on this machine.. Satish On Wed, 13 Mar 2019, Amneet Bhalla via petsc-users wrote: > Hi Folks, > > I am on a cluster that has

Re: [petsc-users] Compiling Fortran Code

check petsc makefile format - for ex: src/tao/unconstrained/examples/tutorials/makefile Also rename your fortran sources that have petsc calls from .f to .F On Wed, 13 Mar 2019, Matthew Knepley via petsc-users wrote: > On Wed, Mar 13, 2019 at 7:36 PM Maahi Talukder via petsc-users < >

Re: [petsc-users] What's the correct syntax for PetscOptionsSetValue("-pc_hypre_boomeramg_no_CF","true"); ?

On Thu, 28 Feb 2019, Klaus Burkart via petsc-users wrote: > Hello, > I try to use the Hypre boomeramg preconditioner but I keep getting type > conversion errors like this one for PetscOptionsSetValue(...): > Fehler: »const char*« kann nicht nach »PetscOptions« {aka »_n_PetscOptions*«} >

Re: [petsc-users] Error with petsc on OSX with libpng

On Wed, 27 Feb 2019, Amneet Pal Bhalla via petsc-users wrote: > Ah, I see. I will try to make sure that my Xcode is working. Did you try to > update XCode yet. Hm - currently petsc is tested with: balay@ipro^~ $ xcodebuild -version Xcode 10.1 Build version 10B61 balay@ipro^~ $ clang

Re: [petsc-users] Error with petsc on OSX with libpng

On Thu, 28 Feb 2019, Balay, Satish via petsc-users wrote: > For some reason your xcode compiler is giving these warnings during linktime > - and I don't know why. These warnings are confusing petsc configure. > > >>>>>>> > ld: warning: text-based stu

Re: [petsc-users] Error with petsc on OSX with libpng

Can you try the following and see if it makes a difference? ./configure --CC=mpicc --CXX=mpicxx --FC=mpif90 --PETSC_ARCH=sierra-dbg --with-debugging=1 --download-hypre=1 --with-x=0 LIBS='-L/usr/local/Cellar/mpich/3.3/lib -lmpifort -L/usr/local/Cellar/gcc/8.3.0/lib/gcc/8 -lgfortran' For some

Re: [petsc-users] (no subject)

Can you send configure.log from this build? Satish On Thu, 28 Feb 2019, DAFNAKIS PANAGIOTIS via petsc-users wrote: > Hi everybody, > > I am trying to install PETSc version 3.10.3 on OSX Sierra 10.13.6 with the > following configure options > ./configure --CC=mpicc --CXX=mpicxx --FC=mpif90

Re: [petsc-users] Fwd: PETSC installation issues

On Wed, 27 Feb 2019, Alexander Lindsay wrote: > Is this part of the log relevant? Here is the relevant part. Do not need to rebuild FBLASLAPACK <<< Here configure thinks FBLASLAPACK is already built. > TEST checkLib from

Re: [petsc-users] Fwd: PETSC installation issues

>>> stderr: /usr/bin/ld: cannot find -lfblas <<< Looks like a broken/incomplete build - that configure thinks is successful. Suggest doing a fresh build after 'rm -rf /home/ryan/projects/moose/petsc/linux-c-opt' Also if using threads - might want to use --download-openblas [or MKL] Satish On

Re: [petsc-users] Link to the latest tutorials broken

fixed now. Satish On Thu, 7 Feb 2019, Sajid Ali via petsc-users wrote: > Hi, > > The links to the Jan 2019 presentations at > https://www.mcs.anl.gov/petsc/documentation/tutorials/index.html are > broken. Could these be fixed ? > > Thank You, > Sajid Ali > Applied Physics > Northwestern

Re: [petsc-users] Installing PETSc

On Tue, 5 Feb 2019, Fazlul Huq via petsc-users wrote: > Hello PETSc Developers, > > may be this is a trivial question! > > I usually run PETSc code from Home/petsc-3.10.2 directory. Last day I tried > to run the code from Documents/petsc directory but I can't. I don't know what you mean here -

Re: [petsc-users] C++ compilation error

Glad you figured this out. Thanks for the update. Satish On Sun, 13 Jan 2019, Choudhary, Devyani D wrote: > It was the issue with the compiler, and is resolved now. I can run the > examples now. > > Thank you for your help. > > > Devyani > > > From: Balay,

Re: [petsc-users] C++ compilation error

Do you get this error with any petsc example – say src/ksp/ksp/examples /tutorials/ex2 ? Also, copy paste the complete output from make – when building example or your Test code. Satish From: petsc-users on behalf of Choudhary, Devyani D via petsc-users

Re: [petsc-users] C++ compilation error

Presumably PETSc is buit with intel compilers - but somehow gcc/g++ is getting used via your makefile. Do you get this error when you use PETSc example with a petsc makefile? Perhaps you need to format your makefile using petsc makefile format. For ex: check

Re: [petsc-users] PETSc configure error

Can you send configure.log from this failure? Do you have any old version of bfort in your PATH? Satish On Thu, 10 Jan 2019, Yaqi Wang via petsc-users wrote: > Hello, > > I am having difficulty on configuring PETSc. Running configure crashed in > the middle. At the end of configure.log, I

Re: [petsc-users] METIS double precision

https://bitbucket.org/petsc/petsc/pull-requests/1316/metis-provide-download-metis-use/ Satish On Thu, 10 Jan 2019, Balay, Satish via petsc-users wrote: > Well - this was the previous default - and was removed as it was deemed > unnecessary. > > https://bitbucket.org/petsc/p

Re: [petsc-users] Configuring PETSc with OpenMPI

Should have clarified: when using --with-cc=/usr/local/depot/openmpi-3.1.1-gcc-7.3.0/bin/mpicc - removing -with-mpi-dir option. i.e - try: /configure PETSC_ARCH=linux-cumulus-hpc --with-cc=/usr/local/depot/openmpi-3.1.1-gcc-7.3.0/bin/mpicc

Re: [petsc-users] Question about correctly catching fp_trap

On Mon, 7 Jan 2019, Sajid Ali via petsc-users wrote: > Hi Satish, > > Please find attached the logs for the previous patch for petsc+debug. >>> Compilers: C Compiler:

Re: [petsc-users] Configuring PETSc with OpenMPI

Configure Options: --configModules=PETSc.Configure --optionsModule=config.compilerOptions PETSC_ARCH=linux-cumulus-hpc --with-cc=gcc --with-fc=gfortran --with-cxx=g++ --with-mpi-dir=/usr/local/depot/openmpi-3.1.1-gcc-7.3.0/bin/ --download-parmetis --download-metis --download-ptscotch

Re: [petsc-users] Question about correctly catching fp_trap

On Mon, 7 Jan 2019, Sajid Ali wrote: > @Satish Balay : I tried building with the patch and > don't see any difference. Do you want me to send you the config and build > logs to investigate further? Hm - you should see '-g' for 'petsc+debug'. Send the logs. I have - in

Re: [petsc-users] VecGetArrayF90 in PETSc/3.10 (Fortran)

This code is missing: #include use petscvec Check: https://www.mcs.anl.gov/petsc/petsc-current/docs/manualpages/Sys/UsingFortran.html Satish On Sun, 6 Jan 2019, Chang Liu via petsc-users wrote: > Hi All, > Recently, when I am upgrading our code from 3.8 to 3.10, it always runs > into

Re: [petsc-users] Question about correctly catching fp_trap

I guess the primary bug here is 'petsc+debug' option is broken in spack. Its not clear to me if a package in spack should have 'debug' option. [so I should remove this?] since spack way is perhaps: spack install CFLAGS=-g FFLAGS=-g CXXFLAGS=-g petsc Satish On Fri, 4 Jan 2019, Smith, Barry F.

Re: [petsc-users] Installation error on macOS Mojave using GNU compiler

On Thu, 3 Jan 2019, Matthew Knepley via petsc-users wrote: > On Thu, Jan 3, 2019 at 7:02 PM Danyang Su via petsc-users < > petsc-users@mcs.anl.gov> wrote: > > > Hi All, > > > > I am trying to install PETSc on macOS Mojave using GNU compiler. > > First, I tried the debug version using the

Re: [petsc-users] Configure error after upgrading GCC

The fix for petsc build error with openmpi-4.0.0 is in branch 'barry/remove-mpi-handler-function/maint' You can always get petsc to build mpich or openmpi - with --download-mpich or --download-openmpi Satish On Mon, 10 Dec 2018, Amneet Bhalla via petsc-users wrote: > That still caused the

  1   2   >