Re: [petsc-users] PetscSortInt() in PETSc 3.22

https://urldefense.us/v3/__https://petsc.org/release/manualpages/Sys/PetscSortInt/__;!!G_uCfscf7eWS!abfR-2RYdZsOXFaja4qPl17LNED2IYBaty9XZrlDUTRk3PGyPVqfaHKUMl9w130BTQi21XlV1oOhUbxVmyOhOUI1Y9A$ 'na' should be PetscCount Satish On Tue, 1 Oct 2024, Adrian Croucher wrote: > hi > > I just pulled

Re: [petsc-users] Compiling 3.21.5 version on a Grace Hopper node failed

these discussions to our system admin, hoping they can get > some hints on this internal compiler error. > > Thanks, > Qiyue Lu > > On Tue, Sep 24, 2024 at 11:09 PM Satish Balay > wrote: > > > Can you try the following and see if it makes a difference > > &

Re: [petsc-users] Compiling 3.21.5 version on a Grace Hopper node failed

Can you try the following and see if it makes a difference make V=1 CUDAFLAGS="-g -O0" all Satish On Tue, 24 Sep 2024, Junchao Zhang wrote: > Hi, Qiyue, > I don't have the exact compilers as yours (cuda-12.3 + gcc-13.2.1). I > tried petsc-3.21.5 with cuda-12.6 + gcc-13.3.0 and it compiled f

Re: [petsc-users] [MPI GPU Aware] KSP_DIVERGED

t courrier n°43 > F-91191 Gif-sur-Yvette > +33 1 69 08 04 03 > +33 6 83 42 05 79 > > De : Satish Balay > Envoyé : lundi 16 septembre 2024 18:57:02 > À : Junchao Zhang > Cc : LEDAC Pierre; petsc-users@mcs.anl.gov; ROUMET Elie > Objet : Re: [petsc-users]

Re: [petsc-users] [MPI GPU Aware] KSP_DIVERGED

And/Or - try latest OpenMPI [or MPICH] and see if that makes a difference. --download-mpich or --download-openmpi with latest petsc should build gpu-aware-mpi Satish On Mon, 16 Sep 2024, Junchao Zhang wrote: > Could you try petsc/main to see if the problem persists? > > --Junchao Zhang > >

Re: [petsc-users] Bug or mis-use for 64 indices PETSc mpi linear solver server with more than 8 cores

I fixed the "garbled" text at https://urldefense.us/v3/__https://gitlab.com/petsc/petsc/-/issues/1643__;!!G_uCfscf7eWS!YEs2AyYzwZQphspkgEhgojcPm1ypNLOD9_BZwl9NzvkOhN7BdIXzBHuN2n_6s2yV2e8VMCn58IgSGrN6NakWS5sRZnw$ - and best if additional followup is on the issue tracker [so that the replies to t

Re: [petsc-users] Installing PETSc in Ubuntu 24.04 - check test error

what do you have for: /usr/local/openmpi-4.1.5/bin/mpif90 -show Also, can you try: make check FFLAGS=-Wno-maybe-uninitialized Satish On Tue, 3 Sep 2024, Barry Smith wrote: > >This is fine. Just an over-enthusiastic compiler > >Barry > > > > On Sep 3, 2024, at 9:43 PM, Bodhinanda

Re: [petsc-users] Configure issues with scalapack

I would: - use 'top' to see where the hang is - retry the build and see if the hang persists - tweak compiler options [change from -O3 to -O2 or such, or use latest cmake] and see if that makes a difference. Also note - the instructions for using Intel OneAPI MPI https://urldefense.us/v3/__http

Re: [petsc-users] Issue configuring PETSc with HYPRE in Polaris

If building on front-end - try using --with-make-np=8 [or 4] If you still have issues - send configure.log Satish On Fri, 9 Aug 2024, Vanella, Marcos (Fed) via petsc-users wrote: > Hi All, I keep running into this issue when trying to configure PETSc > downloading HYPRE in Polaris. > My module

Re: [petsc-users] [petsc-maint] MKL installation can't be used to configure PETSc

On Thu, 25 Jul 2024, Barry Smith wrote: > > Another question, do you know if PETSc can be configured with AMD AOCL https: //urldefense. us/v3/__https: //www. amd. com/en/developer/aocl. html__;!!G_uCfscf7eWS!fpZDfJNW8hTF-oegPfBQc6tJ9KB_EqE8Zy7cnZSJReTjCNvHRduS4G1yz6XRJYS5DN8jtS97BgXeBhy84u7Bo2

Re: [petsc-users] MKL installation can't be used to configure PETSc

Are you sure you are providing the correct path? --with-blaslapack-dir=/tool/pandora64/. package/oneMKL-2021. 3/mkl MKL Path not found. . skipping: /tool/pandora64/. package/oneMKL-2021. 3/mkl/lib/64 MKL Path not found. . skipping:  ZjQcmQRYFpfptBannerStart This Me

Re: [petsc-users] configure petsc with X windows

heck https://urldefense.us/v3/__https://petsc.org/release/community/mailing/__;!!G_uCfscf7eWS!aSHmbfgm1oFpkKOgqRGDwrejlDZDv8pnFv97nvk9muKRcYs-fSlrEKsptNQVCnCjh4Bvm7yAWTYm1BB_kPblWsPQks0$ for details. Satish On Mon, 22 Jul 2024, Satish Balay wrote: > > On Mon, 22 Jul 2024, Ivan Luthfi wrote: >

Re: [petsc-users] configure petsc with X windows

On Mon, 22 Jul 2024, Ivan Luthfi wrote: > Hi there, > I want to configure PETSc with X windows, but i get this notification. > > Unable to find x in default locations! > Perhaps you can specify with --with-x-dir= ZjQcmQRYFpfptBannerStart This Message Is From an External

Re: [petsc-users] Help me for compiling my Code

you don't invoke linker to create .o files. Here is the format you can use. Satish --- balay@ pj01: ~/test$ ls app. c app-req. c makefile balay@ pj01: ~/test$ cat makefile all: app CLEANFILES = app include ${PETSC_DIR}/lib/petsc/conf/variables include ZjQcmQRYFpfptBanner

Re: [petsc-users] Asking about warning unused variable

On Fri, 12 Jul 2024, Ivan Luthfi wrote: > Hello, > > I have declare a variable in my petsc code like the following: > > PetscInt mg_level = 2, finest; > > but i get warning. The warning is, > > (line185) warning:  ZjQcmQRYFpfptBannerStart This Message Is From an Externa

Re: [petsc-users] How to add additional cpp flags in the makefile while compiling a code?

CXXFLAGS, (and similarly CXXPPFLAGS) should work -as I've shown in my prior e-mail [if you are using default PETSc makefile targets] Satish balay@ pj01: ~/test$ ls ex2. cpp makefile balay@ pj01: ~/test$ cat makefile CXXFLAGS = -test_cxxflags ZjQcmQRYFpfptBanner

Re: [petsc-users] How to add additional cpp flags in the makefile while compiling a code?

-L/usr/lib/gcc/x86_64-redhat-linux/13 -lpetsc -llapack -lblas -ltriangle -lm -lX11 -lmpifort -lmpi -lgfortran -lm -lgfortran -lm -lgcc_s -lquadmath -lstdc++ -lquadmath -foobar -o ex2 g++: error: unrecognized command-line option ‘-foobar’ make: *** [: ex2] Error 1 Satish On Tue, 9 Jul 2024, Satish

Re: [petsc-users] How to add additional cpp flags in the makefile while compiling a code?

It depends on your makefile - and how you are over-riding the targets. 1. Why add -rpath to CXXFLAGS, and not LDFLAGS? The following work for me with the default makefile format used by petsc examples balay@ pj01: ~/test$ ls ex2. cpp makefile ZjQcmQRYFpfptBannerStart Th

Re: [petsc-users] make check error using Intel MKL

Satish > > 获取Outlook for Android<https://urldefense.us/v3/__https://aka.ms/AAb9ysg__;!!G_uCfscf7eWS!YD3pSCtmel4vZOSRRp4xe90d2P67Alot3sDBXE54GF3Gaj55MxEmoJjwCHNWWlcyOwTlsK7kpRs_r3lsFjO3hfiZPHbd0g$> > ____ > From: Satish Balay > Sent: Friday, July 5

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

texpr _n_WeakContext() noexcept = default; > ^ > compilation aborted for C:\Users\gli\Desktop\PETSc\PETSC-~1.3\src\sys\objects\device\INTERF~1\device.cxx (code 2) > make[3]: *** [gmakefile:203: arch-mswin-c-debug/obj/src/sys/objects/device/interface/device.o] Error 2 > CXX arch-mswin

Re: [petsc-users] make check error using Intel MKL

Intel compilers require a compatible gcc/g++ compiler. gcc-11 on ubuntu20. 04 might be too new for "Intel parallel studio 2019" So you'll need an older gcc - perhaps gcc-7 or gcc-8 for this version of Intel compiler. Alternative: if you do not ZjQcmQRYFpfptBannerStart T

Re: [petsc-users] Weird handling of compiler flags by the build system

On Mon, 1 Jul 2024, meator wrote: > On 7/1/24 5: 23 PM, Stefano Zampini wrote: > > This is unfortunate. I assume that patching the buildsystem or some > > other trickery will be necessary if what you're saying is true. > > ZjQcmQRYFpfptBannerStart This Message Is From a

Re: [petsc-users] Weird handling of compiler flags by the build system

Some additional notes: On Mon, 1 Jul 2024, meator wrote: > I would normally get -fvisibility=hidden This is controlled by configure option --with-visibility=1/0 > because -fPIC gets included in C flags even when CFLAGS is set. This is ZjQcmQRYFpfptBannerStart This Messa

Re: [petsc-users] Weird handling of compiler flags by the build system

On Mon, 1 Jul 2024, Stefano Zampini wrote: > Il giorno lun 1 lug 2024 alle ore 16: 43 meator ha > scritto: > > > Thank you for your reply! > > > > On 7/1/24 4: 14 PM, Barry Smith wrote:  ZjQcmQRYFpfptBannerStart This Message Is From an External Sender Thi

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

Here is what I get Satish balay@ petsc-win01 /cygdrive/e/balay $ wget -q https: //urldefense. us/v3/__https: //web. cels. anl. gov/projects/petsc/download/release-snapshots/petsc-3. 21. 2. tar. gz__;!!G_uCfscf7eWS!a-qNL2S_yxJ-jU6i9u-E05zJ0

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

This is strange. What do you have for: ls -l lib/petsc/conf/ And please send copy/paste text - and not screenshots Satish On Fri, 28 Jun 2024, Gang Li wrote: > Hi Satish, > Thanks for your help.   > The same error happens after I used ZjQcmQRYFpfptBannerStart This Messa

Re: [petsc-users] Issues Compiling petsc4py with Cython

Best to get latest petsc and build petsc4py along with petsc: For example: balay@ petsc-gpu-02: /scratch/balay$ wget -q https: //urldefense. us/v3/__https: //web. cels. anl. gov/projects/petsc/download/release-snapshots/petsc-3. 21. 2. tar. gz__;!!G_uCfscf7eWS!cU65HojMoX4qnDw9h2E_i8frWwq0jfbCE

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

On Tue, 25 Jun 2024, Gang Li wrote: > The same error when I restart this build using a fresh tarball. Did you use winzip or similar windows utility to 'untar' the tarball? Can you try from cygwin shell: tar -czf petsc-3. 21. 2. tar. gz And see ZjQcmQRYFpfptBannerStart T

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/ ZjQcmQRYFpfptBannerStart This Message

Re: [petsc-users] Petsc Build error

> > > On Jun 13, 2024, at 6: 33 PM, s. pradeep kumar wrote: > > > ./configure --with-scalar-type=real --with-precision=double --download-metis=$metis_path --download-metis-use-doubleprecision=1 ZjQcmQRYFpfptBannerStart This Message Is From an External Sender

Re: [petsc-users] Petsc Build error

> > gmake[3]: *** No rule to make target '/$NETWORK$/users/$USERNAME$/NumLib/petsc-3. 21. 1/src/sys/f90-mod/petscsysmod. F90', needed by 'gnu-opt/obj/src/sys/f90-mod/petscsysmod. o'. Stop. Why is the above source file missing? Make sure your ZjQcmQRYFpfptBannerStart Thi

Re: [petsc-users] Error in PETSc configuration on Mac Sonoma

Try using the additional configure option: 'LDFLAGS=-Wl,-ld_classic -Wl,-commons,use_dylibs' Also consider upgrading to the latest petsc release 3. 21. 2 Satish On Tue, 11 Jun 2024, Barry Smith wrote: > > The issue is here > > configure: 31815:  ZjQcmQRYFpfptBannerStart

Re: [petsc-users] 2^32 integer problems

A couple of suggestions. - try building with gcc/gfortran - likely the compiler will flag issues (warnings) with the sources - that might be the cause of some of the errors. - try using PetscInt datatype across all sources (i.e use .F90 suffix - and include petsc includes) - to avoid any lingeri

Re: [petsc-users] duplicated libs

On Tue, 14 May 2024, Runjian Wu wrote: 61;7601;1c > Yes, it is indeed cleaner. Thanks for your explanation! > > Now I have a question. If I stick to the old PETSc version (v3.16.2), I can > manually remove the duplicated libraries in PETSC_LIB and keep the order of > libraries at the same time, th

Re: [petsc-users] duplicated libs

ort -lmpi -lgfortran -lstdc++ Satish On Tue, 14 May 2024, Satish Balay via petsc-users wrote: > You can try using latest petsc version [3.21] - the list should be a bit more > cleaner with it. > > balay@pj01:~/petsc$ ./configure --download-mpich --download-fblaslapack > --

Re: [petsc-users] duplicated libs

t; -lmpichfort -lmpich -lgfortran -lm -lgfortran -lm -lgcc_s -lquadmath > -lstdc++ -ldl > > On Mon, May 13, 2024 at 9:34 PM Satish Balay wrote: > > > what version of PETSc? What configure command? What do you have for > > PETSC_EXTERNAL_LIB_BASIC? > > > > You ca

Re: [petsc-users] Can not find the header file for OpenMPI

it in compile commands. Satish On Mon, 13 May 2024, Satish Balay via petsc-users wrote: > On Mon, 13 May 2024, neil liu wrote: > > > > I also tried the 2nd way, it didn't work. > > configure.log attached is successful. > > >>>>>>>> > Conf

Re: [petsc-users] Can not find the header file for OpenMPI

On Mon, 13 May 2024, neil liu wrote: > I also tried the 2nd way, it didn't work. configure.log attached is successful. Configure Options: --configModules=PETSc.Configure --optionsModule=config.compilerOptions --download-fblaslapack --with-mpi-dir=/usr/lib64/openmpi Compilers: C Co

Re: [petsc-users] Can not find the header file for OpenMPI

mpi > > > On Mon, May 13, 2024 at 11:42 AM Satish Balay wrote: > > > You are misinterpreting --with-mpi-include --with-mpi-lib options. > > > > Any particular reason you want to use these options instead of mpi > > compilers? > > > > >>>>&

Re: [petsc-users] Can not find the header file for OpenMPI

- > --with-mpi-lib=['/usr/lib64/openmpi/lib'] and > --with-mpi-include=['/usr/include/openmpi-x86_64'] did not work > ***** > > On Mon, May 13, 2024 at

Re: [petsc-users] Can not find the header file for OpenMPI

On Mon, 13 May 2024, neil liu wrote: > Dear Petsc developers, > > I am trying to install Petsc with a preinstalled OpenMPi. > > ./configure --download-fblaslapack --with-mpi-dir=/usr/lib64/openmpi --with-mpi-dir=DIR is a bit unique [wrt other pkg-dir options]. It means: --with-cc=DIR/bin/mp

Re: [petsc-users] duplicated libs

what version of PETSc? What configure command? What do you have for PETSC_EXTERNAL_LIB_BASIC? You can send configure.log for your build to petsc-maint Generally duplicates should not cause grief. [as one needs them to overcome circular dependencies]. What issues are you seeing? [send relevant

Re: [petsc-users] About PC hpddm

Try: spack install slepc+hpddm ^petsc+hpddm Satish On Thu, 9 May 2024, Ng, Cho-Kuen via petsc-users wrote: > Pierre, > > petec and slepc libraries are found in the spack directory, but > libhpddm_petsc is not. So it is not built during the spack install process. > > ... ... > ./opt/spack/li

Re: [petsc-users] Fortran Linker Issue on Mac Sonoma

1. Suggest reinstalling brew/gfortran - to make sure its compatible with latest xcode you have. https://urldefense.us/v3/__https://petsc.org/release/install/install/*installing-on-macos__;Iw!!G_uCfscf7eWS!Y7eNVqUTtBNMYgHPI9pgKFBFMZJwLjwjtp4gGnxFTyYpQMN-rfvF4wJiuZywnYU-Rof6DANF1xg1U0VLr7FgG54$

Re: [petsc-users] Compiling PETSc in Polaris with gnu

ring runtime. > > I tried adding loading this module (also needed to add nvhpc-mixed) in my > submission script but I get the same result. > I'll get in touch with alcf help on this. > > > > > From: Satish Balay > Sent:

Re: [petsc-users] Compiling PETSc in Polaris with gnu

=1 --with-cudac=nvcc --with-cuda-arch=80 \ --with-debugging=0 COPTFLAGS=-O2 CXXOPTFLAGS=-O2 FOPTFLAGS=-O2 CUDAOPTFLAGS=-O2 --download-kokkos --download-kokkos-kernels make Satish --- balay@polaris-login-01:~> module list Currently Loaded Modules: 1) libfabric/1.15.2.0 4) darshan/3.

Re: [petsc-users] Compiling PETSc in Polaris with gnu

Try: module use /soft/modulefiles Satish On Thu, 2 May 2024, Vanella, Marcos (Fed) via petsc-users wrote: > Hi all, it seems the modules in Polaris have changed (can't find > cudatoolkit-standalone anymore). > Does anyone have recent experience compiling the library with gnu and cuda in > the

Re: [petsc-users] Asking SuiteSparse to use Metis at PETSc config time

f x is not installed - configure won't find it - and defaults to disabling x11. Otherwise you can always force: --with-x=0 Satish > Thank you, > Marcos > ________ > From: Satish Balay > Sent: Monday, April 29, 2024 12:00 PM > To: Vanella, Marcos (Fed) &

Re: [petsc-users] Asking SuiteSparse to use Metis at PETSc config time

anVR7b-fp6-0WA2AHagxB5l4dfWhCIXRkGDh_lPJgJ0av1HSQ_YMreLtmLeeBQ5VB9M$ Satish On Mon, 29 Apr 2024, Satish Balay via petsc-users wrote: > > # Other CMakeLists.txt files inside SuiteSparse are from dependent packages > # (LAGraph/deps/json_h, GraphBLAS/cpu_features, and CHOLMOD/SuiteSparse_metis > # which

Re: [petsc-users] Asking SuiteSparse to use Metis at PETSc config time

# Other CMakeLists.txt files inside SuiteSparse are from dependent packages # (LAGraph/deps/json_h, GraphBLAS/cpu_features, and CHOLMOD/SuiteSparse_metis # which is a slightly revised copy of METIS 5.0.1) but none of those # CMakeLists.txt files are used to build any package in SuiteSparse. So

Re: [petsc-users] Spack build and ptscotch

This is the complexity with maintaining dependencies (and dependencies of dependencies), and different build systems - Its not easy to keep the "defaults" in both builds exactly the same. - And its not easy to expose all "variants" or keep the same variants in both builds. - And each pkg has its

Re: [petsc-users] Problem with NVIDIA compiler and OpenACC

Apr 2024, Satish Balay wrote: > >>> > Executing: mpifort -o /tmp/petsc-nopi85m9/config.compilers/conftest -v > -KPIC -O2 -g /tmp/petsc-nopi85m9/config.compilers/conftest.o > stdout: > Export > NVCOMPILER=/software/sse2/tetralith_el9/manual/nvhpc/23.7/Linux_x86_64/

Re: [petsc-users] Problem with NVIDIA compiler and OpenACC

>>> Executing: mpifort -o /tmp/petsc-nopi85m9/config.compilers/conftest -v -KPIC -O2 -g /tmp/petsc-nopi85m9/config.compilers/conftest.o stdout: Export NVCOMPILER=/software/sse2/tetralith_el9/manual/nvhpc/23.7/Linux_x86_64/23.7 Export PGI=/software/sse2/tetralith_el9/manual/nvhpc/23.7 /softwar

Re: [petsc-users] Problem with NVIDIA compiler and OpenACC

On Thu, 4 Apr 2024, Frank Bramkamp wrote: > Dear PETSC Team, > > I found the following problem: > I compile petsc 3.20.5 with Nvidia compiler 23.7. > > > I use a pretty standard configuration, including > > --with-cc=mpicc --with-cxx=mpicxx --with-fc=mpifort COPTFLAGS="-O2 -g" > CXXOPTFLAGS=

Re: [petsc-users] ex19: Segmentation Violation when run with MUMPS on MacOS (arm64)

With xcode-15.3 and branch "barry/2024-04-03/fix-chaco-modern-c/release" from https://urldefense.us/v3/__https://gitlab.com/petsc/petsc/-/merge_requests/7433__;!!G_uCfscf7eWS!YJPSyG4qeGbCKYRp9y16HJgjw7AOrQ0mL0QWb_XcKYZ17UwK2GtURGMpkyi4TctAY-8XqSvQUFmyCQFNnKy75fI$ [and a patched openmpi tarball t

Re: [petsc-users] ex19: Segmentation Violation when run with MUMPS on MacOS (arm64)

On Mon, 1 Apr 2024, Zongze Yang wrote: > Thank you for your update. > > I found some links that suggest this issue is related to the Apple linker, > which is causing problems with Fortran linking. > > 1. > https://urldefense.us/v3/__https://github.com/open-mpi/ompi/issues/12427__;!!G_uCfscf7eW

Re: [petsc-users] ex19: Segmentation Violation when run with MUMPS on MacOS (arm64)

On Mon, 1 Apr 2024, Zongze Yang wrote: > > I noticed this in the config.log of OpenMPI: > ``` > configure:30230: checking to see if mpifort compiler needs additional linker > flags > configure:30247: gfortran -o conftest -fPIC -ffree-line-length-none > -ffree-line-length-0 -Wno-lto-type-mismatc

Re: [petsc-users] ex19: Segmentation Violation when run with MUMPS on MacOS (arm64)

On Sun, 31 Mar 2024, Zongze Yang wrote: > > --- > > petsc@npro petsc % ./configure --download-bison --download-chaco > > --download-ctetgen --download-eigen --download-fftw --download-hdf5 > > --download-hpddm --download-hwloc --download-hypre --download-libpng > > --download-metis --download-mm

Re: [petsc-users] ex19: Segmentation Violation when run with MUMPS on MacOS (arm64)

ug.txt' in the attachment. Particularly, the > > file 'debug.txt' contains the output of bt command of lldb. > > > > Thanks for your attention. > > > > Best regards, > > Zeyu Xia > > > > > > Satish Balay mailto:ba...@mcs.anl.go

Re: [petsc-users] ex19: Segmentation Violation when run with MUMPS on MacOS (arm64)

the attachment. > > If possible, please do me a favor again. Thanks for your patience. > > Best wishes, > Zeyu Xia > > > Satish Balay 于2024年3月29日周五 23:48写道： > > > Could you: > > > > - reinstall brew after the xcode upgrade (not just update) &g

Re: [petsc-users] [External] Re: Does ILU(15) still make sense or should just use LU?

On Fri, 29 Mar 2024, Pfeiffer, Sharon wrote: > I’d like to unsubscribe to this mailing list. Done. Note: every list e-mail provides this info [in headers] List-Id: PETSc users list List-Unsubscribe:

Re: [petsc-users] ex19: Segmentation Violation when run with MUMPS on MacOS (arm64)

Could you: - reinstall brew after the xcode upgrade (not just update) https://urldefense.us/v3/__https://petsc.org/main/install/install/*installing-on-macos__;Iw!!G_uCfscf7eWS!fr-mLHdhIQgT2IBZhK9C2IQMUAmTmneTF38VsNLrywxooidf1uunovfx8qJrr8-Y73tICazCqyaZ6SJ6ca6JXnQ$ - not use --LDFLAGS=-Wl,-ld_cl

Re: [petsc-users] Using PetscPartitioner on WINDOWS

or use tarballs. Satish On Thu, 21 Mar 2024, Satish Balay via petsc-users wrote: > Delete your old build files - and retry. i.e > > rm -rf /cygdrive/g/mypetsc/petsc-3.20.5/arch-mswin-c-opt > > ./configure > > Satish > > > On Thu, 21 Mar 2024, 程奔 wrote: >

Re: [petsc-users] Using PetscPartitioner on WINDOWS

*** > > I send configure.log with "--download-parmetis --download-metis" to you and > ask for you help. > > sinserely, > Ben. > > > -原始邮件- > > 发件人: "Satish Balay" > > 发送时间:2024-03-20 21:29:56 (星期三) > > 收件人: 程奔 &g

Re: [petsc-users] Using PetscPartitioner on WINDOWS

lab.com/petsc/petsc/-/jobs/6412623047__;!!G_uCfscf7eWS!YOO7nEnwU4BJQXD3WkP3QCvaT1gfLxBxnrNdXp9SJbjETmw7uaRKaUkPRPEgWgxibROg8o_rr8SxbnaVWtJbAT-t281f2ha4Aw$ > for a successful build of lates > t petsc-3.20 , it seem have something called "sowing" and "bison" , but I >

Re: [petsc-users] Using PetscPartitioner on WINDOWS

Check https://urldefense.us/v3/__https://gitlab.com/petsc/petsc/-/jobs/6412623047__;!!G_uCfscf7eWS!ZAg_b85bAvm8-TShDMHvxaXIu77pjwlDqU2g9AXQSNNw0gmk3peDktdf8MsGAq3jHLTJHo6WSPGyEe5QrCJ-fN0$ for a successful build of latest petsc-3.20 [i.e release branch in git] with metis and parmetis Note the u

Re: [petsc-users] Install PETSc with option `--with-shared-libraries=1` failed on MacOS

On Mon, 18 Mar 2024, Pierre Jolivet wrote: > > And here we go: > https://urldefense.us/v3/__https://gitlab.com/petsc/petsc/-/jobs/6420606887__;!!G_uCfscf7eWS!alfBlmyFQ5JJUYKxxFdETav6xjHOl5W54BPrmJEyXdSakVXnj8eYIRZdknOI-FK4uiaPdL4zSdJlD2zrcw$ > > 20 minutes in, and still in the dm_* tests with

Re: [petsc-users] Install PETSc with option `--with-shared-libraries=1` failed on MacOS

On Mon, 18 Mar 2024, Satish Balay via petsc-users wrote: > On Mon, 18 Mar 2024, Pierre Jolivet wrote: > > > > > > > > On 18 Mar 2024, at 5:13 PM, Satish Balay via petsc-users > > > wrote: > > > > > > Ah - the compiler did flag code bugs.

Re: [petsc-users] Install PETSc with option `--with-shared-libraries=1` failed on MacOS

On Mon, 18 Mar 2024, Pierre Jolivet wrote: > > > > On 18 Mar 2024, at 5:13 PM, Satish Balay via petsc-users > > wrote: > > > > Ah - the compiler did flag code bugs. > > > >> (current version is 0.3.26 but we can’t update because there is a huge

Re: [petsc-users] Install PETSc with option `--with-shared-libraries=1` failed on MacOS

Zongze > > > On 18 Mar 2024, at 00:50, Zongze Yang wrote: > > > > It can be resolved by adding CFLAGS=-Wno-int-conversion. Perhaps the > > default behaviour of the new version compiler has been changed? > > > > Best wishes, > > Zongze > >>

Re: [petsc-users] Compile Error in configuring PETSc with Cygwin on Windows by using Intel MPI

Glad you have a successful build! Thanks for the update. Satish On Tue, 12 Mar 2024, 程奔 wrote: > Hi Satish Sorry for replying to your email so late, I follow your suggestion > and it have been installed successfully. Thank you so much. best wishes, Ben > > -原始邮件----- > 发件人

Re: [petsc-users] Broken links in FAQ

The website is now updated Satish On Fri, 8 Mar 2024, Satish Balay via petsc-users wrote: > Thanks for the report! The fix is at > https://urldefense.us/v3/__https://gitlab.com/petsc/petsc/-/merge_requests/7343__;!!G_uCfscf7eWS!aRgkooWLFmFbCqsaZyYQixeOgy0qD1N3WlxPMXIGCCA-fhjJ6DS

Re: [petsc-users] Broken links in FAQ

Thanks for the report! The fix is at https://urldefense.us/v3/__https://gitlab.com/petsc/petsc/-/merge_requests/7343__;!!G_uCfscf7eWS!aRgkooWLFmFbCqsaZyYQixeOgy0qD1N3WlxPMXIGCCA-fhjJ6DSuGhanT-xc5iuF4tjVn4BBShyMJnqZr2I0dEo$ Satish On Fri, 8 Mar 2024, David Bold wrote: > Dear all, I noticed tha

Re: [petsc-users] Compile Error in configuring PETSc with Cygwin on Windows by using Intel MPI

> make[3]: *** No rule to make target 'w'. Stop. Try the following to overcome the above error: make OMAKE_PRINTDIR=make all However 3.13.6 is a bit old - so don't know if it will work with these versions of compilers. Satish On Wed, 6 Mar 2024, 程奔 wrote: > Hello, > > > Last time I insta

Re: [petsc-users] Cannot do make on ex55k

Looks like ex55 is the one to use - that links in with ex55k But it needs a fix for a build from 'make' >> balay@petsc-gpu-01:/scratch/balay/petsc/src/snes/tutorials$ git diff diff --git a/src/snes/tutorials/makefile b/src/snes/tutorials/makefile index 672a62aa5a0..eed127f7eae 100644 ---

Re: [petsc-users] PetscSection: Fortran interfaces

diff --git a/src/vec/f90-mod/petscvecmod.F90 b/src/vec/f90-mod/petscvecmod.F90 index 4c54fbf63dc..8772f89e135 100644 --- a/src/vec/f90-mod/petscvecmod.F90 +++ b/src/vec/f90-mod/petscvecmod.F90 @@ -163,6 +163,7 @@ #include <../src/vec/f90-mod/petscvec.h90> interface #include <../src/vec/f

Re: [petsc-users] undefined reference to `petsc_allreduce_ct_th'

On Thu, 18 Jan 2024, Aaron Scheinberg wrote: > Hello, > > I'm getting this error when linking: > > undefined reference to `petsc_allreduce_ct_th' > > The instances are regular MPI_Allreduces in my code that are not located in > parts of the code related to PETSc, so I'm wondering what is happ

Re: [petsc-users] M2 macs

The usual xcode/clang + brew/gfortran should work. https://gitlab.com/petsc/petsc/-/jobs/5895519334 https://gitlab.com/petsc/petsc/-/jobs/5895519414 There can be issues - not all CI builds work in M2 - with latest xcode [when I tried this previously] - so some CI jobs are still on Intel/Mac [wit

Re: [petsc-users] Configure error while building PETSc with CUDA/MVAPICH2-GDR

Executing: mpicc -show stdout: icc -I/opt/apps/cuda/11.4/include -I/opt/apps/cuda/11.4/include -lcuda -L/opt/apps/cuda/11.4/lib64/stubs -L/opt/apps/cuda/11.4/lib64 -lcudart -lrt -Wl,-rpath,/opt/apps/cuda/11.4/lib64 -Wl,-rpath,XORIGIN/placeholder -Wl,--build-id -L/opt/apps/cuda/11.4/lib64/ -lm -

Re: [petsc-users] petsc build could not pass make check

Do you have a ~/.petscrc file - with -log_view enabled? Satish On Wed, 29 Nov 2023, Di Miao via petsc-users wrote: > Hi, > > I tried to compile PETSc with the following configuration: > > ./configure --with-debugging=0 COPTFLAGS='-O3' CXXOPTFLAGS='-O3' > FOPTFLAGS='-O3' --with-clean=1 > --wi

Re: [petsc-users] Segmentation Violation error using SuperLU_DIST in ex 19.c

oad-make > > Now, it runs the superLU_dist test successfully but it gives an error with > MATLAB engine 'Possible error running C/C++ src/vec/vec/tutorials/ex31 with > MATLAB engine' and also an error with MAKE check. > > > > On Thu, Nov 23, 2023 at 10:26 PM Sat

Re: [petsc-users] Segmentation Violation error using SuperLU_DIST in ex 19.c

Can you do a simple build with only superlu-dist and see if the error persists? ./configure PETSC_ARCH=linux-slu --with-cc=/usr/local/gcc11/bin/gcc --with-cxx=/usr/local/gcc11/bin/g++ --with-fc=gfortran --with-debugging=1 --with-scalar-type=complex --download-mpich --download-fblaslapack --down

Re: [petsc-users] Difficulty installing PETSC-3.17.0 on new macOS Sonoma

replied on petsc-maint xcode-15 changed considerably, (fixes are in petsc-3.20) that its not easy to backport all needed patches to 3.17.0 So best bet for petsc-3.19 and older is to use linux (remotely or via VM) - or downgrade to xcode-14. Satish On Mon, 20 Nov 2023, Jan Izak C. Vermaak via

Re: [petsc-users] error in configuring PETSc

Suggest attaching text logs (copy/paste) - instead of screenshots. Try: ./configure --with-cc=gcc-11 --with-cxx=g++-11 --with-fc=gfortran-11 --download-fftw --download-openmpi --download-fblaslapack --with-zlibs=yes --with-szlib=no --with-c2html=0 --with-x=0 --download-hdf5-fortran-bindings=1

Re: [petsc-users] OpenMP doesn't work anymore with PETSc building rules

s --with-openmp option, it cannot even > > build. The interesting thing is, I got this error even after removing the > > *-fopenmp* from *CXXFLAGS* contents: > > CXXFLAGS=-std=c++17 > > LDFLAGS= > > CXXPPFLAGS=-I/u/qiyuelu1/cuda/cuda-samples/Common > > include

Re: [petsc-users] OpenMP doesn't work anymore with PETSc building rules

On Wed, 25 Oct 2023, Qiyue Lu wrote: > Hello, > I have an in-house code enabled OpenMP and it works. Now I am trying to > incorporate PETSc as the linear solver and build together using the > building rules in $PETSC_HOME/lib/petsc/conf/rules. However, I found the > OpenMP part doesn't work anym

Re: [petsc-users] use MATSEQAIJMKL in 64-bit indices

Try using the additional option --with-64-bit-blas-indices=1 Satish On Fri, 20 Oct 2023, Di Miao wrote: > Hi, > > I found that when compiled with '--with-64-bit-indices=1' option, the > following three definitions in petscconf.h will be removed: > > #define PETSC_HAVE_MKL_SPARSE 1 > #define PE

Re: [petsc-users] Error when installing PETSc

> Working directory: /home/tt/petsc-3.16.0 use latest petsc release - 3.20 > --with-fc=flang I don't think this ever worked. Use --with-fc=gfortran instead /opt/ohpc/pub/spack/opt/spack/linux-centos7-skylake_avx512/gcc-8.3.0/m4-1.4.19-lwqcw3hzoxoia5q6nzolylxaf5zevluk/bin/m4: internal error det

Re: [petsc-users] Using Sundials from PETSc

I'll note - current sundials release has some interfaces to petsc functionality Satish On Mon, 16 Oct 2023, Matthew Knepley wrote: > On Mon, Oct 16, 2023 at 2:29 PM Vanella, Marcos (Fed) via petsc-users < > petsc-users@mcs.anl.gov> wrote: > > > Hi, we were wondering if it would be possible to c

Re: [petsc-users] Configuration of PETSc with Intel OneAPI and Intel MPI fails

able here, quite often I can't reach petsc.org. > Regards, > Roland Richter > > -Ursprüngliche Nachricht- > Von: Satish Balay > Gesendet: mandag 9. oktober 2023 17:29 > An: Barry Smith > Cc: Richter, Roland ; petsc-users@mcs.anl.gov > Betreff: Re: [petsc

Re: [petsc-users] Configuration of PETSc with Intel OneAPI and Intel MPI fails

Will note - OneAPI MPI usage is documented at https://petsc.org/release/install/install/#mpi Satish On Mon, 9 Oct 2023, Barry Smith wrote: > > Instead of using the mpiicc -cc=icx style use -- with-cc=mpiicc (etc) and > > export I_MPI_CC=icx > export I_MPI_CXX=icpx > export I_MPI_F90=ifx >

Re: [petsc-users] 'nvcc -show' Error for configure with NVCC

On Fri, 6 Oct 2023, Qiyue Lu wrote: > Hello, > I am trying to configure PETSc(current release version) with NVCC, with > these options: > ./configure --with-cc=nvcc --with-cxx=nvcc --with-fc=0 --with-cuda=1 this usage is incorrect. You need: --with-cc=mpicc --with-cxx=mpicxx --with-cudac=nvcc

Re: [petsc-users] Error when configure cmake

Here --download-cmake is failing [due to the old version of c++ compiler]. You can try installing an older version manually instead of --download-cmake Or you might be able to install a newer gcc/g++ easily [if its not already installed on your machine]. For ex: git clone https://github.com/spa

Re: [petsc-users] Issue when configuring my petsc-3.20.0

Can you send us the complete configure.log file [as attachment] - perhaps to petsc-ma...@mcs.anl.gov Satish On Sat, 30 Sep 2023, Ivan Luthfi wrote: > Hi team, > I have an issue when I configure my petsc with the following script: > > ./configure --with-fc=0 --download-f2cblaslapack=1 > --with

Re: [petsc-users] Xcode 15.0 breaks PETSc configure?

petsc git repo main branch has fixes for xcode-15. Can you give it a try? Satish On Thu, 28 Sep 2023, Paul Tackley wrote: > Hello, > > PETSc was working fine on my M1 Mac until I upgraded to Xcode 15.0 - now I > can’t even configure it. There seems to be a problem related to C and C++ in > Xc

Re: [petsc-users] I cannot find my libpetsc.a in my installation pets-3.4.5

or a static version of the library - and use it if found. Satish > > thank you for your recommendation, i will try as your recommendation step > by step, because the code uses some deprecated function that I have to > changed to be compiled in the latest version > > On Tue, Sep

Re: [petsc-users] I cannot find my libpetsc.a in my installation pets-3.4.5

Tue, Sep 26, 2023 at 4:20 AM Satish Balay wrote: > > > > > What are you looking at? Send 'ls' from PETSC_DIR/PETSC_ARCH/lib > > > > Perhaps its a shared library build - and you have libpetsc.so? > > > > BTW: the current release is 3.19 - and y

Re: [petsc-users] I cannot find my libpetsc.a in my installation pets-3.4.5

What are you looking at? Send 'ls' from PETSC_DIR/PETSC_ARCH/lib Perhaps its a shared library build - and you have libpetsc.so? BTW: the current release is 3.19 - and you are attempting to build a super old version 3.4. We recommend using the latest version to avoid build and other compatibil

Re: [petsc-users] PETSc with Xcode 15

Do you get this failure with petsc main branch as well? Satish On Thu, 21 Sep 2023, Blaise Bourdin wrote: > FWIW, CLT 15.0 also seems to include changes to the linker, with incompatible > options etc… I was able to rebuild mpich and petsc but I get many linker > warnings and have not fully te

Re: [petsc-users] Problem with BLASdot in 3.19.4

Its a run time option to petsc (application) binary. So you can either specify it via command line - at run time - or add it to env variable "PETSC_OPTIONS" - or add it to $HOME/.petscrc file Satish On Tue, 19 Sep 2023, Thuc Bui wrote: > Hi Barry, > > > > Thanks for getting back to me. Th

  1   2   3   4   5   6   7   8   9   10   >