On Fri, 19 Jan 2024, Satish Balay via petsc-dev wrote:
> >
> > Unable to download package ZLIB from:
> > http://ftp.mcs.anl.gov/pub/petsc/externalpackages/zlib-1.2.11.tar.gz
> >
>
> Hm - this works directly - but not from python? I'll have to check with our
&g
On Fri, 19 Jan 2024, Adrian Croucher wrote:
> hi
>
> I've just started having errors building PETSc on both my Github CI pipeline
> and on another machine, as a result of zlib failing to download. (I'm using
> the download-zlib option.) The error is:
>
> UNABLE to CONFIGURE with GIVEN OPTIONS
We are using discord:
https://lists.mcs.anl.gov/pipermail/petsc-users/2023-July/049115.html
Satish
On Tue, 5 Dec 2023, Escobedo, Andres via petsc-dev wrote:
> Hello,
>
>
> My name in Andy, I am a masters student in the computational fluid dynamics
> group at the University of British
Sounds like the issue is with using findPetsc - after petsc is installed [and
petsc install went fine?]
I think the current recommendation is to use pkg-config file interface via
cmake -instead of findPetsc
And the following works for me..
./configure COPTFLAGS="-O3 -g" CXXOPTFLAGS="-O3 -g"
Johann,
We are migrating to discord from slack:
https://lists.mcs.anl.gov/pipermail/petsc-users/2023-July/049115.html
[I guess docs need updating]
Satish
On Tue, 10 Oct 2023, Johann Rudi wrote:
> Hello,
>
> I would like to join the Petsc Slack space, and on petsc.org the
> instructions say
With our current 6-month release cycle, its again time for another PETSc
release.
For this release [3.20], lets work with the following dates:
- feature freeze: Sep 26 say 5PM EST
- release: Sep 28 say 5PM EST
"v3.20-release" milestone can be used with all MRs that are targeted for a
merge
Well in spack world - the idea is to get flags from spack and use it in petsc
build. Its possible that there are issues in this implementation.
Something spack does is - it internally adds in flags (to the compiler - via
its compiler wrapper) - that petsc configure doesn't see.
I see 'spack
Check:
https://lists.mcs.anl.gov/pipermail/petsc-users/2023-July/049015.html
Satish
On Mon, 10 Jul 2023, Singh, Abhishek Kumar wrote:
> I am working as a Postdoc at Max Planck Institute for Plasma Physics. I have
> started using PETSc as a tool for solving system of equations. I would like
https://gitlab.com/petsc/petsc/-/merge_requests/6578/commits
commit 0898713fbecf5e265dbd1d072d2bffc3dcf92948
Author: Stefano Zampini
Date: Sat Jun 17 20:40:28 2023 +0200
petsc4py docs: enforce 79 characters lines
<<<
so perhaps:
diff --git
On Thu, 15 Jun 2023, Blaise Bourdin wrote:
> Hi,
>
> I am trying to figure out why the doc page for PetscOptionsHeadBegin
> https://petsc.org/release/manualpages/Sys/PetscOptionsHeadBegin/ is broken.
>>
#else
/*MC
On Thu, 15 Jun 2023, Jacob Faibussowitsch wrote:
> > I am trying to figure out why the doc page for PetscOptionsHeadBegin
> > https://petsc.org/release/manualpages/Sys/PetscOptionsHeadBegin/ is broken.
>
> It's missing a Synopsis: section. See PetscOptionsEnd docstring.
>
> > I do
> >
> > cd
On Thu, 15 Jun 2023, Blaise Bourdin wrote:
> Hi,
>
> I am trying to figure out why the doc page for PetscOptionsHeadBegin
> https://petsc.org/release/manualpages/Sys/PetscOptionsHeadBegin/ is broken.
> Following the instructions at
>
not ok vec_pf_impls_string_tests-ex1_1 # Error code: 65
# [0]PETSC ERROR: - Error Message
--
# [0]PETSC ERROR: Unable to open file
# [0]PETSC ERROR: Unable to open dynamic library:
#
Not sure how can add deprecation message here - so adding this message to
'changes' doc
https://gitlab.com/petsc/petsc/-/merge_requests/6382
Satish
On Wed, 26 Apr 2023, Satish Balay via petsc-dev wrote:
> On Wed, 26 Apr 2023, Barry Smith wrote:
>
> >
> >
> >
On Wed, 26 Apr 2023, Barry Smith wrote:
>
>
> Urg, so user makefiles that worked for 25+ years suddenly don't work and
> that is ok? No deprecation message as Jed would have liked?
I think I raised this issue when 'CFLAGS = ' stuff was removed from all
makefiles.
You can view this change
Also note:
I think we previously handled this by always having this in each makefile
[without a configure default]
CFLAGS =
But that format was removed..
Satish
On Wed, 26 Apr 2023, Satish Balay via petsc-dev wrote:
> Well we wanted to always have CFLAGS initialized by config
Well we wanted to always have CFLAGS initialized by configure [to ignore stuff
from env].
So now - if we are setting in makefile - it has to be set after this default is
set - i.e after the line:
include ${PETSC_DIR}/lib/petsc/conf/variables
Or do:
make CFLAGS=garbase ex1
There might be a
is
[I guess support both CYTHON_MIN and CYTHON_MAX]
Satish
>
> Thanks,
>
> Matt
>
>
> > Thanks,
> > Pierre
> >
> > > On 16 Apr 2023, at 12:25 AM, Satish Balay via petsc-dev <
> > petsc-dev@mcs.anl.gov> wrote:
> > >
> &
Works for me with latest main - so I'm not sure whats going on here..
Is this reproducible in a clean clone? Also - are you using mpi4py in this
build?
https://gitlab.com/petsc/petsc/-/issues/1359
[this issue looks different though..]
Satish
--
*** Building petsc4py ***
running build
A reminder, the feature freeze for the upcoming release is in a couple of days.
Satish
On Tue, 28 Feb 2023, Satish Balay wrote:
> Its time for another PETSc release - due end of March.
>
> For this release [3.19], lets work with the following dates:
>
> - feature freeze: March 28 say 5PM EST
Its time for another PETSc release - due end of March.
For this release [3.19], lets work with the following dates:
- feature freeze: March 28 say 5PM EST
- release: March 30 say 5PM EST
Merges after freeze should contain only fixes that would normally be acceptable
to "release" work-flow.
BTW: ANL summer student application process is also in progress - and
it could be easier process [for Junchao] than google to get a student
[If I remember correctly - there is a category where students are at no
cost to the project]
Satish
On Fri, 3 Feb 2023, Junchao Zhang wrote:
> On Fri,
Both my builds below [4.2.0, 4.3.0] are with --download-cgns - yet they have
different symbols..
perhaps there are more differences between these 2 versions [than just Seq vs
MPI builds]
Satish
---
args.append('-DCGNS_ENABLE_PARALLEL:BOOL=ON')
Looks like cgp_close() is a cgns-4.3.0 feature.
Satish
---
4.2.0:
nm -Ao libcgns.so |grep close |grep ' T '
libcgns.so:000ae832 T ADFI_close_file
libcgns.so:00061492 T cg_close
libcgns.so:0005ece4 T cgio_close_file
4.3.0:
nm -Ao libcgns.so |grep close |grep ' T '
Dear PETSc users,
The patch release petsc-3.18.1 is now available for download.
https://petsc.org/release/install/download/
Satish
Hm - I see numpy on older OS - but not on M1. So Apple no longer bundles it?
And pip creates grief on NFS :(
Satish
--
balay@ypro ~ % sw_vers
ProductName:Mac OS X
ProductVersion: 10.15.7
BuildVersion: 19H2026
balay@ypro ~ % python3 -c "import numpy; print(numpy.__file__)"
Yes - this always bothered me...
But I don't think its always possible to automate it.
The likable version [.so] might not exist - only .so.ver might exist? [and it
might use blas but not lapack?]
Note: one way to avoid this issue is to let spack install
python,numpy,petsc,petsc4py
Satish
https://gitlab.com/petsc/petsc/-/merge_requests/5724/diffs
>>>
* [API Changes in each release](../changes/index.rst)
* [MPI](http://www.mpich.org/static/docs/latest/)
* [Vector Operations (Vec)](Vec/index.md)
etc was removed. I assumed it wasn't easy to migrate that to rst format.
prev:
MR with this fix at https://gitlab.com/petsc/petsc/-/merge_requests/5672
Satish
On Thu, 22 Sep 2022, Satish Balay via petsc-dev wrote:
> Perhaps the following change.
>
> Satish
> ---
>
> diff --git a/src/sys/dll/dlimpl.c b/src/sys/dll/dlimpl.c
> index fc48860316
;ompi_mpi_init") || !dlsym(RTLD_DEFAULT,
"MPID_Abort"), PETSC_COMM_SELF, PETSC_ERR_MPI_LIB_INCOMP, "Application was
linked against both OpenMPI and MPICH based MPI libraries and will not run
correctly");
#endif
On Thu, 22 Sep 2022, Satish Balay via petsc-dev wrote:
&
.c:337:35: error: use of
undeclared identifier 'info'
PetscCall(PetscDemangleSymbol(info.dli_sname, name));
^
1 warning and 3 errors generated.
make: *** [gmakefile:195: arch-olcf-crusher/obj/sys/dll/dlimpl.o] Error 1
On Thu, 22 Sep 2022, Satish Balay via petsc-dev wro
I see this is change was done at
https://gitlab.com/petsc/petsc/-/merge_requests/5268
Likely due to errors with cray compilers.
So I guess we could add in __clang__ as you suggest. Can you create an MR with
this change?
And probably the same fix for src/sys/objects/pinit.c ?
Satish
On Thu,
Hm - we don't use readthedocs anymore.
And I see docs.petsc.org is getting redirected to https://petsc.org/release/
So I guess perhaps we don't need to update anything on readthedocs.
[perhaps Jed can confirm]
Satish
On Tue, 30 Aug 2022, Matthew Knepley wrote:
> Is someone looking at this?
There is also -Wno-lto-type-mismatch - but don't know if its for this issue or
a different one.
Satish
On Fri, 19 Aug 2022, Blaise Bourdin wrote:
> It prints this warning instead of throwing an error. I should have mentioned
> that this is on a M1 Mac, since gfortran behaviour and flags is
Does -fallow-argument-mismatch work?
Satish
On Fri, 19 Aug 2022, Blaise Bourdin wrote:
> Hi,
>
> Does anybody know if there is a magic gfortran flag to get rid of type
> mismatch warnings?
> These pop up when using PetscObjectSetName with two different petsc objects,
> for instance.
>
>
I think there is some logic there that marks only the lines from the MR diff.
Barry might remember this correctly.
Satish
On Fri, 12 Aug 2022, Blaise Bourdin wrote:
> thanks Satish,
>
> That doesn’t seem quite right, though. For instance, I see that
>
There is some coverage info - there are a couple of gcov tests - but
that doesn't show coverage from all tests.
For ex: https://gitlab.com/petsc/petsc/-/merge_requests/5509
click on the last stage/job of the pipeline 'analyze-pipeline' i.e
https://gitlab.com/petsc/petsc/-/jobs/2841119765
Here -
Dear PETSc users,
The patch release petsc-3.17.4 is now available for download.
http://www.mcs.anl.gov/petsc/download/index.html
Satish
A fix is now merged to main. A *new* pipeline on the MR should work now.
Satish
On Fri, 29 Jul 2022, Barry Smith wrote:
>
> I just reported this on the testing-ci slack channel one second ago. Looks
> like it was introduced with Matt's last merge.
>
>
> > On Jul 29, 2022, at 5:37 PM,
On Wed, 27 Jul 2022, Satish Balay via petsc-dev wrote:
> Maybe should try without hwloc...
So this helps! i.e build with:
$ ./configure --with-debugging=0 --download-mpich --with-hwloc=0 && make
>>>
balay@p1 /home/balay/petsc/src/ksp/ksp/tests (main =)
$ sleep 30; time
"sleep 30; strace ./ex39" shows an extra pause while reading the following file
(on my laptop):
balay@p1 /home/balay
$ sleep 10; time cat /sys/bus/pci/devices/:00:01.0/config; time cat
/sys/bus/pci/devices/:00:01.0/config
�00���
real0m1.271s
user0m0.000s
sys
I'm seeing this behavior on a laptop - but not desktop [both F36] (with both
mpich and openmpi buids)
laptop/mpich
balay@p1 /home/balay/petsc/src/ksp/ksp/tests (main =)
$ sleep 30; time ./ex39; time ./ex39
real0m1.709s
user0m0.079s
sys 0m0.042s
real0m0.116s
user
Fande,
You can use the hash for this - i.e 477e44bbb558b1357d86363677accbb4bcdfaabc
in moose builds/CI - and see if that works
Satish
On Tue, 19 Jul 2022, Satish Balay via petsc-dev wrote:
> Created MR with your patch to release
> https://gitlab.com/petsc/petsc/-/merge_request
Created MR with your patch to release
https://gitlab.com/petsc/petsc/-/merge_requests/5447
Can merge this into release-3.16 as-well.
Satish
On Tue, 19 Jul 2022, Satish Balay via petsc-dev wrote:
> Ok - this issue persists in main branch
>
> reproducible [on M1 mac] with:
>
&
Ok - this issue persists in main branch
reproducible [on M1 mac] with:
./configure --with-mpi=0 --download-fblaslapack --with-debugging=no
Satish
On Tue, 19 Jul 2022, Barry Smith wrote:
>
>Urgg, I was sure we saw it recently and "fixed" it but searches on my
> machine and googling don't
On Tue, 19 Jul 2022, Fande Kong wrote:
> On Tue, Jul 19, 2022 at 12:22 PM Satish Balay wrote:
>
> > Barry,
> >
> > Which commit in 3.17 fixed this?
> >
> > Fande,
> >
> > If I add a patch to branch "release-3.16" - would that get used? [as there
> > won't be any new 3.16 tarballs]
> >
>
> Yes,
>>>
Strumpack requires the LAPACK routine dlapmr(), the current Lapack libraries
['liblapack.a', 'libblas.a'] does not have it
Try using --download-fblaslapack=1 option
<<<
Ok - so strumpack can't use vecLb
Satish
On Tue, 19 Jul 2022, Satish Balay via petsc-dev wrote:
also fail?
Satish
On Tue, 19 Jul 2022, Satish Balay via petsc-dev wrote:
> Barry,
>
> Which commit in 3.17 fixed this?
>
> Fande,
>
> If I add a patch to branch "release-3.16" - would that get used? [as there
> won't be any new 3.16 tarballs]
>
> BTW:
Barry,
Which commit in 3.17 fixed this?
Fande,
If I add a patch to branch "release-3.16" - would that get used? [as there
won't be any new 3.16 tarballs]
BTW: Any particular reason to use fblaslapack - instead of [default] veclib on
Mac?
Satish
On Tue, 19 Jul 2022, Fande Kong wrote:
> Hi
Dear PETSc users,
The patch release petsc-3.17.3 is now available for download.
http://www.mcs.anl.gov/petsc/download/index.html
Satish
Dear PETSc users,
The patch release petsc-3.17.2 is now available for download.
http://www.mcs.anl.gov/petsc/download/index.html
Satish
On Wed, 25 May 2022, Barry Smith wrote:
>
>
> > On May 25, 2022, at 12:06 PM, Satish Balay wrote:
> >
> > On Wed, 25 May 2022, Matthew Knepley wrote:
> >
> >> On Wed, May 25, 2022 at 11:55 AM Barry Smith wrote:
> >>
> >>>
> >>> It would be nice if when people received MR review requests
On Wed, 25 May 2022, Matthew Knepley wrote:
> On Wed, May 25, 2022 at 11:55 AM Barry Smith wrote:
>
> >
> > It would be nice if when people received MR review requests it indicated
> > if the review was trivial and could be done in a minute or two. Then maybe
> > quick ones could flow through
On Wed, 4 May 2022, Patrick Sanan wrote:
> Unlike most previous docs changes, this has only been done on the main
> branch. So, **until PETSc 3.18 is released, make documentation MRs to main**,
> unless fixing something particularly critical on the release branch, or
> making a change which
Dear PETSc users,
The patch release petsc-3.17.1 is now available for download.
http://www.mcs.anl.gov/petsc/download/index.html
Satish
Hm we reverted all fortran examples to use CHKERRQ(). [from PetscCall] so
presumably CHKERRQ() is still the preferred interface from fortran?
Satish
On Tue, 26 Apr 2022, Jacob Faibussowitsch wrote:
> Hi Glenn,
>
> `PetscCall()` is the future, apologies for the confusion.
>
> `CHKERRQ()` was
Perhaps there are already some political decisions made. Since PETSc is part of
xsdk - we are to commited to contirbute to it.
But then when evaluating MRs - its hard to rememer how to enforce some of these
commitments. [so for improving CI is the primary suggestion - and only at the
xsdk
erlu_dist then finalizing PETSc then finalizing
> dealii.
>
>
>
> > On Apr 3, 2022, at 1:15 PM, Satish Balay via petsc-dev
> > wrote:
> >
> > This issue comes up in xsdk. most packages [superlu_dist, hypre, petsc,
> > trilinos - and
there is certainly frustration with changes.
And then there could be real issues. If similar major changes land in sept
release [at the last minite] in any critical packages [that others packages
don't quickly add it to their own sept release ] - that might break things in a
way that xsdk
This issue comes up in xsdk. most packages [superlu_dist, hypre, petsc,
trilinos - and a bunch of others] attempt to make a release in sept [ECP
milestone].
But then there are non-ecp packages that don't do that - and isues come up [for
ex: dealii usually has an earlier release - that has a
On Sun, 3 Apr 2022, Barry Smith wrote:
>
>
> > On Apr 3, 2022, at 12:24 PM, Satish Balay wrote:
> >
> >> If we had this attitude with the external packages PETSc uses we would
> >> have to stop using most of the packages/*.py.
> >
> > Sure one can take extreme view on both sides. [no
> If we had this attitude with the external packages PETSc uses we would have
> to stop using most of the packages/*.py.
Sure one can take extreme view on both sides. [no change, vs won't hesitate to
change] - having a manageable (minimal) change is harder to do.
I would point out that most
On Sun, 3 Apr 2022, Satish Balay via petsc-dev wrote:
> Just noticed - CHKERRQ() got removed from fortran interface - breaking
> pflotran
>
> https://gitlab.com/xsdk-project/spack-xsdk/-/jobs/2285145624
>
> [also CHKERRABORT]. Perhaps they can be added back in.
>
>
Note this is not just 'users should update their code' issue.
- all packages (that use petsc) would need to do this update
- and this update doesn't always happen - so pakages will stay at old release -
some might not
- so now we cant build PETSc with both these packages together.
this type
On Tue, 29 Mar 2022, Junchao Zhang wrote:
> Also, it looks we need a 64-bit CI job on Mac.
pushed a CI update to https://gitlab.com/petsc/petsc/-/merge_requests/5050
Satish
On Tue, 29 Mar 2022, Junchao Zhang wrote:
> On Tue, Mar 29, 2022 at 4:59 PM Satish Balay via petsc-dev <
> petsc-dev@mcs.anl.gov> wrote:
>
> > We do have such builds in CI - don't know why CI didn't catch it.
> >
> > $ grep with-64-bit-indices=1 *.py
> >
I'm not sure why we have PetscSFCount - and not always use MPI_Count.
Maybe this would work?
Perhaps Junchao can clarify
Satish
---
diff --git a/src/vec/is/sf/impls/basic/neighbor/sfneighbor.c
b/src/vec/is/sf/impls/basic/neighbor/sfneighbor.c
index 5dc2e8c0b2..10f42fc302 100644
---
We do have such builds in CI - don't know why CI didn't catch it.
$ grep with-64-bit-indices=1 *.py
arch-ci-freebsd-cxx-cmplx-64idx-dbg.py: '--with-64-bit-indices=1',
arch-ci-linux-cuda-double-64idx.py:'--with-64-bit-indices=1',
arch-ci-linux-cxx-cmplx-pkgs-64idx.py:
What MPI is this? How to reproduce?
Perhaps its best if you can send the relevant logs.
The likely trigger code in sfneighbor.c:
/* A convenience temporary type */
#if defined(PETSC_HAVE_MPI_LARGE_COUNT) && defined(PETSC_USE_64BIT_INDICES)
typedef PetscInt PetscSFCount;
#else
· created 2 days ago by Barry Smith v3.17-release
dmnetwork rebalance vertices
!4945 · created 2 weeks ago by Getnet Betrie v3.17-release
On Thu, 3 Mar 2022, Satish Balay via petsc-dev wrote:
> All,
>
> Its time for another PETSc release - due end of March.
>
> F
Dear PETSc users,
The patch release petsc-3.16.5 is now available for download.
https://petsc.org/release/download/
Satish
All,
Its time for another PETSc release - due end of March.
For this release [3.17], lets work with the following dates:
- feature freeze: March 28 say 5PM EST
- release: March 30 say 5PM EST
Merges after freeze should contain only fixes that would normally be acceptable
to "release"
Dear PETSc users,
The patch release petsc-3.16.4 is now available for download.
https://petsc.org/release/download/
Satish
The change is at https://gitlab.com/petsc/petsc/-/merge_requests/4770
Satish
On Thu, 27 Jan 2022, Satish Balay via petsc-dev wrote:
> And the source inside include don't get built.
>
> I guess the fix is to switch these stubs to custom [and move the sources to
> src/sys/loggin
And the source inside include don't get built.
I guess the fix is to switch these stubs to custom [and move the sources to
src/sys/logging/ftn-custom/]
Will do.
Satish
On Thu, 27 Jan 2022, Stefano Zampini wrote:
> This is a bug and it should be fixed
>
> Il giorno gio 27 gen 2022 alle ore
Dear PETSc users,
The patch release petsc-3.16.3 is now available for download.
https://petsc.org/release/download/
Satish
The box is rebooted now.
Satish
On Mon, 13 Dec 2021, Matthew Knepley wrote:
> https://gitlab.com/petsc/petsc/-/jobs/1879771695
>
> Thanks,
>
> Matt
>
>
kout origin/main
> >> 1027 ./config/examples/arch-olcf-spock.py && make
> >> 1028 MPIR_CVAR_GPU_EAGER_DEVICE_MEM=0 MPICH_GPU_SUPPORT_ENABLED=1
> >> MPICH_SMP_SINGLE_COPY_MODE=CMA make check
> >>
> >> Satish
> >>
> >> On Fri, 10 Dec 2021, Satis
Dec 2021, Satish Balay via petsc-dev wrote:
> Works for me [per instructions in balay/update-spock,
> config/examples/arch-olcf-spock.py] with main - without these additional
> options
>
> I'll go ahead and merge in balay/update-spock
>
> Satish
>
> -
>
>
Works for me [per instructions in balay/update-spock,
config/examples/arch-olcf-spock.py] with main - without these additional options
I'll go ahead and merge in balay/update-spock
Satish
-
1009 git fetch -p
1015 module load emacs
1016 module load rocm/4.3.0
1018 git reset --hard
My build is with xcode clang - not brew clang
Satish
On Thu, 9 Dec 2021, Mark Adams wrote:
> Mpich seems to give the same error.
> I use clang 13.0. I think I get that from homebrew.
> Should I try something like:
> brew install llvm@12
>
> I see:
>
> (conda_env) 07:50 adams/fix_mat_ex5k=
This build goes through fine for me. [with petsc/main]
xpro:petsc balay$ sw_vers
ProductName:Mac OS X
ProductVersion: 10.15.7
BuildVersion: 19H1519
xpro:petsc balay$ clang --version
Apple clang version 12.0.0 (clang-1200.0.32.2)
xpro:petsc balay$ ./configure --download-mpich --with-fc=0
perhaps "dtruss -f" ?
https://stackoverflow.com/questions/1925978/equivalent-of-strace-feopen-command-on-mac-os-x
balay@ypro petsc % dtruss -f ./configure
dtrace: system integrity protection is on, some features will not be available
dtrace: failed to initialize dtrace: DTrace requires
On Tue, 23 Nov 2021, Matthew Knepley wrote:
> On Tue, Nov 23, 2021 at 12:56 PM Matthew Knepley wrote:
>
> > On Tue, Nov 23, 2021 at 12:29 PM Satish Balay wrote:
> >
> >> The primary difference I can spot [as you say] is the older xcode you
> >> have. Eventhough it says the same version of flex
The primary difference I can spot [as you say] is the older xcode you have.
Eventhough it says the same version of flex - perhaps its buggy?
Apple clang version 11.0.3 (clang-1103.0.32.59)
vs
Apple clang version 12.0.0 (clang-1200.0.32.2)
>
On Tue, 23 Nov 2021, Matthew Knepley wrote:
> On Tue, Nov 23, 2021 at 11:28 AM Satish Balay wrote:
>
> > Well we don't have this issue on our (macos) CI boxes where both c2html
> > and scotch build and run daily [in CI]
> >
> > what 'flex' are you using? And why does it behave differently on
On Tue, 23 Nov 2021, Matthew Knepley wrote:
> On Tue, Nov 23, 2021 at 11:28 AM Satish Balay wrote:
>
> > Well we don't have this issue on our (macos) CI boxes where both c2html
> > and scotch build and run daily [in CI]
> >
> > what 'flex' are you using? And why does it behave differently on
Better yet.. [from Junchao]
export CRAY_ACCEL_TARGET=host
Satish
On Fri, 5 Nov 2021, Mark Adams wrote:
> Bingo!
>
> On Fri, Nov 5, 2021 at 12:54 PM Satish Balay wrote:
>
> > Yeah remove [C,CPP,CXX,CXXPP,F] FLAGS
> >
> > CPP defaults to '$CC -E' - so with "--with-cc='cc -mp=gpu'" - it
Yeah remove [C,CPP,CXX,CXXPP,F] FLAGS
CPP defaults to '$CC -E' - so with "--with-cc='cc -mp=gpu'" - it should use "cc
-mp=gpu -E"
Satish
On Fri, 5 Nov 2021, Mark Adams wrote:
> How about CPP flags?
>
> On Fri, Nov 5, 2021 at 12:29 PM Satish Balay wrote:
>
> > I guess another way to deal
I guess another way to deal with this is: not use CFLAGS etc..
--with-cc='cc -mp=gpu' --with-cxx='CC -mp=gpu' --with-fc='ftn -mp=gpu'
Satish
On Fri, 5 Nov 2021, Mark Adams wrote:
> Yes, thanks.
> I emailed the NERSc person and told him where we are and that we could fix
> this manually, but
For now - you could manually edit petscvariables and remove -mp=gpu from it.
Its primarily required to make configure happy.
Satish
On Thu, 4 Nov 2021, Barry Smith wrote:
>
>This comes from the persistent problem with PETSc's make system using too
> many flags for compiling CUDA that
Multiple e-mail threads on the same issue (:
As suggested in my earlier thread - add -mp=gpu to both CPPFLAGS and CFLAGS [or
LDFLAGS]
Satish
---
Executing: cc -o /tmp/petsc-Vvs8_T/config.setCompilers/conftest -g
-DLANDAU_DIM=2 -DLANDAU_MAX_SPECIES=10 -DLANDAU_MAX_Q=4
Then you can try:
CPPFLAGS=-mp-gpu
CFLAGS=-mp-gpu
Satish
On Thu, 4 Nov 2021, Mark Adams wrote:
> But I can get rid of that with: cc -E -mp-gpu
> I expect that is what they will say.
>
> On Thu, Nov 4, 2021 at 1:40 PM Satish Balay wrote:
>
> > I think we went through this issue before.
> >
>
I think we went through this issue before.
nvc is the 'c' compiler. And for some reason its giving 'cuda' warnings.
I think you might have switched progenv last time [and avoided this compiler]
You can try using this compiler manually - on simple code - and then seek help
from the admins on
On Thu, 4 Nov 2021, Mark Adams wrote:
> Does anyone know if PETSc calls nvcc and hence can add flags to the
> invocation? nvcc wants a flag like -mp=gpu but I don't know if we do that
> or a compiler wrapper in the environment.
$ ./configure --help |grep CUDA
--CUDAC=
Specify the
Dear PETSc users,
The patch release petsc-3.16.1 is now available for download.
https://petsc.org/release/download/
Satish
Should be fixed in latest main - so you can try starting a new pipeline
Satish
On Wed, 20 Oct 2021, Mark Adams wrote:
>
>
Fix at https://gitlab.com/petsc/petsc/-/merge_requests/4402
thanks,
Satish
On Sat, 2 Oct 2021, Jacob Faibussowitsch wrote:
> Unrelated to the below (still reading the configure.log) but it looks like
> there’s a bug in the cuda compiler search:
>
> TESTING: checkCUDACompiler from
>
BTW: LIBS is more appropriate as its a difference of:
gcc -lstdc++ ex19.o -lpetsc
vs
gcc ex19.o -lpetsc -lstdc++
i.e
$CLINKER $CC_LINKER_FLAGS $OBJ $PETSC_LIB $LIBS
$FLINKER $FC_LINKER_FLAGS $OBJ $PETSC_LIB $LIBS
Satish
On Sat, 2 Oct 2021, Satish Balay via petsc-dev wrote:
> --with-c
--with-clib-autodetect=0 --with-fortranlib-autodetect=0
--with-cxxlib-autodetect=0
--CC_LINKER_FLAGS="-Wl,-z,relro -Wl,--as-needed -Wl,-z,now
-specs=/usr/lib/rpm/redhat/redhat-hardened-ld
-specs=/usr/lib/rpm/redhat/redhat-annobin-cc1 "
--FC_LINKER_FLAGS="-Wl,-z,relro -Wl,--as-needed
1 - 100 of 442 matches
Mail list logo
