[petsc-users] PETSc options

[Mark Adams]

I don't know why this should have changed, but you can either not feed -v
to PETSc (a pain probably), use PETSc's getOptions methods instead of
Fortran's,  or make a dummy call PETSc's methods in addition to yours.

Hope this helps,
Mark

On Mon, May 6, 2024 at 1:04 AM Adrian Croucher <a.croucher at auckland.ac.nz>
wrote:

> hi, My code has some optional command line arguments -v and -h for output
> of version number and usage help. These are processed using Fortran's
> get_command_argument(). Since updating PETSc to version 3. 21, I get some
> extra warnings after the
> ZjQcmQRYFpfptBannerStart
> This Message Is From an External Sender
> This message came from outside your organization.
>
> ZjQcmQRYFpfptBannerEnd
>
> hi,
>
> My code has some optional command line arguments -v and -h for output of
> version number and usage help. These are processed using Fortran's
> get_command_argument().
>
> Since updating PETSc to version 3.21, I get some extra warnings after
> the output:
>
> acro018 at EN438880:~$ waiwera -v
> 1.5.0b1
> WARNING! There are options you set that were not used!
> WARNING! could be spelling mistake, etc!
> There is one unused database option. It is:
> Option left: name:-v (no value) source: command line
>
> That didn't used to happen. What should I do to make them go away?
>
> Regards, Adrian
>
> --
> Dr Adrian Croucher
> Senior Research Fellow
> Department of Engineering Science
> Waipapa Taumata Rau / University of Auckland, New Zealand
> email: a.croucher at auckland.ac.nz
> tel: +64 (0)9 923 4611
>
>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.mcs.anl.gov/pipermail/petsc-users/attachments/20240506/26e989e3/attachment.html>