On 7/1/24 6:53 PM, Stefano Zampini wrote:> Since you said "your
package", I have a few questions:
- why do your users need to know how to compile with PETSc?
I provide two main packages: petsc and petsc-devel. petsc-devel contains
header files, symlinks to dynamic library & more. petsc-devel
On 7/1/24 6:22 PM, Satish Balay wrote:
And for your desired use case: "I need to specify flags to PETSc build - and they
should not bleed to dependent pkgs" I've indicated one mode for this.
i.e - do not specify them with configure - only list them with make.
./configure
make CFLAGS='only-for
>
>
>
> This is not a choice I get to make. The users of my package may choose
> to use PETSc however they want. And /usr/share/petsc/Makefile.user or
> /usr/share/petsc/CMakeLists.txt are officially supported ways of using
> PETSc, so deciding to ignore these use cases and leaving junk flags in
>
I have added two MR to hopefully improve PETSc usability based on your issues
https://urldefense.us/v3/__https://gitlab.com/petsc/petsc/-/merge_requests/7663__;!!G_uCfscf7eWS!efrDwkgUkc276It23vyi4kUxZ3ieab1AgseqAOCvE-K9-nLNjd6aad4rmdaRExARms_zfeExsNtm5lRx_b5ezSM$

Add information to template
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
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
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.
I admit it is not so standard, but Satish always opposed this.
No need to hack the buildsystem, just use COPTFLAGS
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
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:
> > We have had well over a decade of debates on this issue. I would
> like to see a CFLAGS+=extra_flags option but that has been resisted.
> Instead Satish can tel
Thank you for your reply!
On 7/1/24 4:14 PM, Barry Smith wrote:
We have had well over a decade of debates on this issue. I would like to
see a CFLAGS+=extra_flags option but that has been resisted. Instead Satish can
tell you how to get what you want.
This is unfortunate. I assume that p
> On 1 Jul 2024, at 4:37 PM, maitri ksh wrote:
>
> This Message Is From an External Sender
> This message came from outside your organization.
> I need to export complex vectors data from PETSc and read them in MATLAB.
> However, I am encountering some issues with the data format and
> interp
I need to export complex vectors data from PETSc and read them in MATLAB.
However, I am encountering some issues with the data format and
interpretation in MATLAB.
code-snippet of the vector data export section:
// Assemble the vectors before exporting
ierr = VecAssemblyBegin(f); CHKERRQ(ierr);
ie
On Mon, Jul 1, 2024 at 9:48 AM Blauth, Sebastian <
sebastian.bla...@itwm.fraunhofer.de> wrote:
> Dear Matt,
>
>
>
> thanks a lot for your help. Unfortunately, for me these extra options do
> not have any effect, I still get the “u” and “p” fieldnames. Also, this
> would not help me to get rid of t
> On Jul 1, 2024, at 5: 21 AM, meator wrote: > > Hello, > > I am currently packaging PETSc and have noticed some peculiar behavior when attempting to override CFLAGS, CXXFLAGS, and FFLAGS. > >
ZjQcmQRYFpfptBannerStart
This Message Is From an External Sender
Dear Matt,
thanks a lot for your help. Unfortunately, for me these extra options do not
have any effect, I still get the “u” and “p” fieldnames. Also, this would not
help me to get rid of the “c” fieldname – on that level of the fieldsplit I am
basically using your approach already, and stil
On Fri, Jun 28, 2024 at 4:05 AM Blauth, Sebastian <
sebastian.bla...@itwm.fraunhofer.de> wrote:
> Hello everyone,
>
>
>
> I have a question regarding the naming convention using PETSc’s
> PCFieldsplit. I have been following
> https://urldefense.us/v3/__https://lists.mcs.anl.gov/pipermail/petsc-use
On Mon, Jul 1, 2024 at 1:43 AM MIGUEL MOLINOS PEREZ wrote:
> Dear Matthey,
>
> Sorry for the late response.
>
> Yes, I get output when I run the example mentioned by Barry.
>
> The output directory should not be an issue since with the exact same
> configuration works for hdf5 but not for vtk/vts
Hello,
I am currently packaging PETSc and have noticed some peculiar behavior
when attempting to override CFLAGS, CXXFLAGS, and FFLAGS.
Firstly, when calling ./configure with CFLAGS="args" as its argument, it
seems to completely override the flag detection system in
config/BuildSystem/config
18 matches
Mail list logo
