Hi Vasileios,
Any reason to use PETSc-dev? Do you look for a new functionality that is
not available in the current release? Some of PETSc APIs may get updated
when switch from a low version to a high one or dev.
Here are updated APIs in petsc-dev
https://www.mcs.anl.gov/petsc/documentation/chan
On Wed, Apr 5, 2017 at 9:03 AM, Vasileios Vavourakis
wrote:
> Hi Fande,
>
> No particular reason for using the PETSc-dev - frankly I didn't notice I
> was using it.
> What would you recommend me to do? Should I download the latest or a
> reasonably previous stable version?
>
We generally recomme
Hi Fande,
No particular reason for using the PETSc-dev - frankly I didn't notice I
was using it.
What would you recommend me to do? Should I download the latest or a
reasonably previous stable version?
However, I am now checking / running the installation of a previous PETSc
version (petsc-3.7.2;
Indeed, very strange error.
To answer your question about PETSc version; I employed the following
commit:
fbfa34dc2ebfea5502b6dc1528c107aa61ca96c8
On 5 April 2017 at 15:17, John Peterson wrote:
>
>
> On Wed, Apr 5, 2017 at 2:39 AM, Vasileios Vavourakis
> wrote:
>
>> dear all,
>>
>> after pull
On Wed, Apr 5, 2017 at 8:23 AM, Jed Brown wrote:
> John Peterson writes:
>
> > On Wed, Apr 5, 2017 at 2:39 AM, Vasileios Vavourakis
> > wrote:
> >
> >> dear all,
> >>
> >> after pulling the newest version of libmesh (commit
> >> dbcd57f5f718a088a19b9be38f162b997ec8f97c) and configuring the libr
On Wed, Apr 5, 2017 at 2:39 AM, Vasileios Vavourakis
wrote:
> dear all,
>
> after pulling the newest version of libmesh (commit
> dbcd57f5f718a088a19b9be38f162b997ec8f97c) and configuring the library:
>
> START ==
> ./configure --enable-everything --with-methods="opt" \
>
dear all,
after pulling the newest version of libmesh (commit
dbcd57f5f718a088a19b9be38f162b997ec8f97c) and configuring the library:
START ==
./configure --enable-everything --with-methods="opt" \
--enable-petsc PETSC_DIR=/Users/vasvav/Programs/petsc
PETSC_ARCH=arch-darwin
