Yes, it builds a static lib. I guess I could have also added
"--with-shared-libraries=0", just to be sure. Anyway I have that option in
my "production" installation of PETSc (among other flags related to third
party libraries, which I temporarily disabled to keep things as simple as
possible), but
There is a native autotools installation, but running autoreconf -iv
--force, configure again and make again does not fix the "-WF,-D" part.
It's no big deal anyway for me in this moment, there is just one file
affected (contrib/exodusii/v5.22/exodus/forbind/src/libdbg_la-addrwrap.lo)
On Sat, Nov
> On Nov 2, 2013, at 5:13 AM, Francesco Ballarin
> wrote:
>
> Hi John,
> thanks.
>
> a) I tried building PETSc with --with-clanguage=cxx as you suggested, my
> configure options are now
> ===
> ./configure --with-mpi-dir=/bgsys/drivers/ppcfloor/comm/xl/
> --with-clanguage=cxx
> --with-blas
> On Nov 2, 2013, at 5:13 AM, Francesco Ballarin
> wrote:
>
> Hi John,
> thanks.
>
> a) I tried building PETSc with --with-clanguage=cxx as you suggested, my
> configure options are now
Sorry, didn't mean to suggest _trying_ this, it shouldn't be necessary. Was
just wondering if this was
On Nov 1, 2013, at 11:35 PM, "John Peterson" wrote:
> Why on earth would IBM do this? It differs from literally every other
> compiler that I've ever seen. I don't know if there's a built-in autoconf
> test for "how to #define stuff on the compile line" but that seems like
> that's what we'd
Hi John,
thanks.
a) I tried building PETSc with --with-clanguage=cxx as you suggested, my
configure options are now
===
./configure --with-mpi-dir=/bgsys/drivers/ppcfloor/comm/xl/
--with-clanguage=cxx
--with-blas-lapack-lib=/opt/ibmmath/essl/5.1/lib64/libesslbg.a
--with-make-np=8 --prefix=$PETSC_I
On Fri, Nov 1, 2013 at 1:34 PM, Francesco Ballarin <
francesco.balla...@polimi.it> wrote:
> Dear libMesh developers,
> I'm having some troubles compiling libMesh on a BG/Q architecture with XL
> compilers. I would like to report some issues and ask for your help.
>
>
> 1. The first issue I ran int
I recommend using gcc - that worked fine for me on Mira (BG/Q at Argonne).
Derek
Sent from my iPhone
> On Nov 1, 2013, at 2:34 PM, Francesco Ballarin
> wrote:
>
> Dear libMesh developers,
> I'm having some troubles compiling libMesh on a BG/Q architecture with XL
> compilers. I would like to
Dear libMesh developers,
I'm having some troubles compiling libMesh on a BG/Q architecture with XL
compilers. I would like to report some issues and ask for your help.
1. The first issue I ran into has been that xlc was not properly detected.
It sufficed to change line 294 of m4/compiler.m4 in
is
