Hmm, I think I’ll do option 1). I’m more familiar with PETSc/SLEPc than
libmesh, so I think that it’ll be simpler to stick to the master branch. Thanks
for the indications!
> On 01 Jul 2015, at 16:19, John Peterson wrote:
>
>
>
> On Wed, Jul 1, 2015 at 3:37 AM, Thiago Milanetto Schlittler
On Wed, Jul 1, 2015 at 3:37 AM, Thiago Milanetto Schlittler <
[email protected]> wrote:
> Thanks! This seems to do the trick, at least for the installation. The
> “make” and “make install” steps work with no problems, but I’m getting an
> error during the “make check” step. The failed test outpu
Thanks! This seems to do the trick, at least for the installation. The “make”
and “make install” steps work with no problems, but I’m getting an error during
the “make check” step. The failed test output is given below. Should I be
worried by it?
Thiago
On Tue, Jun 30, 2015 at 8:12 AM, Thiago Milanetto Schlittler <
[email protected]> wrote:
> I’m using OpenMPI 1.7.5 (installed through MacPorts) and PETSc / SLEPc
> 3.6.0 (installed “by hand” with MPI compilers). The configure summary is
> given below.
>
>
> --- SU
Hello!
I’m trying to install libmesh on my computer (OS X version 10.10.3) and I’m
having a series of MPI errors during the compilation:
src/base/libmesh.C:492:24: error: assigning to 'MPI_Comm' (aka
'ompi_communicator_t *')
from incompatible type 'int'
PETSC_COMM_WORLD = libMes
I'll install the 5.x version since I am starting with it. Thanks.
On Thu, May 15, 2014 at 4:00 PM, John Peterson wrote:
>
>
>
> On Thu, May 15, 2014 at 2:51 PM, Miguel Angel Salazar de Troya <
> [email protected]> wrote:
>
>> The problem was that the environment variable PETS_ARCH was no
On Thu, May 15, 2014 at 2:51 PM, Miguel Angel Salazar de Troya <
[email protected]> wrote:
> The problem was that the environment variable PETS_ARCH was not correctly
> set. I could compile and run all the tests in make check. Sorry for all the
> problems.
>
> Now I would like to install it
The problem was that the environment variable PETS_ARCH was not correctly
set. I could compile and run all the tests in make check. Sorry for all the
problems.
Now I would like to install it with VTK. I have version 6.1 installed in my
computer. I have the options
--enable-vtk --with-vtk-include=/
On Thu, May 15, 2014 at 10:46 AM, Miguel Angel Salazar de Troya <
[email protected]> wrote:
> I have seen in the configure output this message
>
> checking /home/miguel/petsc-3.4.4/include/petscversion.h usability... yes
> checking /home/miguel/petsc-3.4.4/include/petscversion.h presence...
I have seen in the configure output this message
checking /home/miguel/petsc-3.4.4/include/petscversion.h usability... yes
checking /home/miguel/petsc-3.4.4/include/petscversion.h presence... yes
checking for /home/miguel/petsc-3.4.4/include/petscversion.h... yes
<<< Warning: configuring in serial
This is a bit embarrasing, but it worked because I was compiling just
another directory. Side effects of 3 pm. It doesn't work yet, Same MPI
error. I deleted the libmesh I had installed in /usr/local/ and the source
directory, downloaded it again, configured it with the same settings than
before an
On Wed, 14 May 2014, Miguel Angel Salazar de Troya wrote:
> That worked. Thanks a lot!
Glad to hear!
Sorry for all the trouble, and thanks for the reports.
---
Roy
--
"Accelerate Dev Cycles with Automated Cross-Browser
That worked. Thanks a lot!
On Wed, May 14, 2014 at 3:24 PM, Roy Stogner wrote:
>
>
> On Wed, 14 May 2014, Miguel Angel Salazar de Troya wrote:
>
> In the directory where libmesh is installed (/usr/local/libmesh/include),the
>> file libmesh_config.h has this:
>>
>> /* Flag indicating whether or
On Wed, 14 May 2014, Miguel Angel Salazar de Troya wrote:
> In the directory where libmesh is installed (/usr/local/libmesh/include),the
> file libmesh_config.h has this:
> /* Flag indicating whether or not MPI is available */
> #ifndef LIBMESH_HAVE_MPI
> #define LIBMESH_HAVE_MPI 1
> #endif
>
In the directory where libmesh is installed (/usr/local/libmesh/include),
the file libmesh_config.h has this:
/* Flag indicating whether or not MPI is available */
#ifndef LIBMESH_HAVE_MPI
#define LIBMESH_HAVE_MPI 1
#endif
whereas in the directory where I have the source code to compile
(/home/mi
On Wed, 14 May 2014, Miguel Angel Salazar de Troya wrote:
mpi.. : yes
Double check for me that LIBMESH_HAVE_MPI is defined in
libmesh_config.h?
---
Roy--
"Accelerate Dev Cycles with Autom
On Wed, May 14, 2014 at 1:52 PM, Miguel Angel Salazar de Troya <
[email protected]> wrote:
> This is how I configure it:
>
> ./configure --enable-mpi --enable-amr --enable-vsmoother --enable-dirichlet
> --enable-nodeconstraint --enable-parmesh --enable-pfem --enable-ifem
> --enable-second
This is how I configure it:
./configure --enable-mpi --enable-amr --enable-vsmoother --enable-dirichlet
--enable-nodeconstraint --enable-parmesh --enable-pfem --enable-ifem
--enable-second --enable-examples --enable-boost --enable-petsc
--enable-periodic --enable-tetgen --enable-triangle --enable
On Wed, 14 May 2014, Miguel Angel Salazar de Troya wrote:
> src/base/libmesh.C:477:24: error: invalid conversion from 'int' to
> 'MPI_Comm {aka ompi_communicator_t*}' [-fpermissive]
> PETSC_COMM_WORLD = libMesh::GLOBAL_COMM_WORLD;
It looks as if somehow you're using MPI-configured PETSc bu
I forgot to mention that I have mpich installed with a different petsc
version, inside of the petsc directory (I used the --download-mpich
option).
On Wed, May 14, 2014 at 2:34 PM, Miguel Angel Salazar de Troya <
[email protected]> wrote:
> Thanks for your response. Now I get this error:
Thanks for your response. Now I get this error:
In file included from /home/miguel/petsc-3.4.4/include/petscsys.h:105:0,
from /home/miguel/petsc-3.4.4/include/petscbag.h:4,
from /home/miguel/petsc-3.4.4/include/petsc.h:5,
from ./include/libmesh/pe
If you don't need the exodus fortran wrappers (and if you're not sure, you
likely don't), you can disable that feature easily enough:
$ ./configure --help | grep exod
--enable-exodus build with ExodusII API support
--enable-exodus-fortran build with ExodusII Fortran API support
so
On Wed, May 14, 2014 at 11:15 AM, Miguel Angel Salazar de Troya <
[email protected]> wrote:
> I obtained the same error, then I also included mpif77
>
> --with-f77=/home/miguel/petsc-3.4.4/arch-linux2-c-debug/bin/mpif77
>
> and I obtained this
>
> make[2]: Entering directory
> `/home/miguel
I obtained the same error, then I also included mpif77
--with-f77=/home/miguel/petsc-3.4.4/arch-linux2-c-debug/bin/mpif77
and I obtained this
make[2]: Entering directory
`/home/miguel/libmesh/contrib/exodusii/5.22b/exodus'
PPF77forbind/src/libdbg_la-addrwrap.lo
On Wed, May 14, 2014 at 10:58 AM, Miguel Angel Salazar de Troya <
[email protected]> wrote:
> Thanks for your quick response. I attached the makecheck.log to my first
> email. I changed the compilers to mpi. These are included in the petsc
> directory (I downloaded it from the configure opt
Thanks for your quick response. I attached the makecheck.log to my first
email. I changed the compilers to mpi. These are included in the petsc
directory (I downloaded it from the configure options in petsc) My
./configure command line appears as follows:
./configure --enable-mpi --enable-amr --en
On Wed, 14 May 2014, Miguel Angel Salazar de Troya wrote:
> I am using petsc 3.4-4 and gcc 4.7. I have gcc 4.8 installed by default, by
> I thought I would change to 4.7 since it is the last version you guys
> tested libmesh with (as it appears in the website).
Gah, thanks for the information.
On Wed, May 14, 2014 at 10:14 AM, Miguel Angel Salazar de Troya <
[email protected]> wrote:
> Hello everybody
>
> I am struggling trying to compile Libmesh properly. I attach the config log
> and the log from the make check. These are the ./configure options I start
> with:
>
> ./configure
Hello everybody
I am struggling trying to compile Libmesh properly. I attach the config log
and the log from the make check. These are the ./configure options I start
with:
./configure --enable-amr --enable-vsmoother --enable-dirichlet
--enable-nodeconstraint --enable-parmesh --enable-pfem --enab
29 matches
Mail list logo
