Re: [Libmesh-users] compiling libmesh on Cray

2013-08-21 Thread Jim Fonseca
Many thanks for everyone's help with this. It is resolved now and your suggestions sent me down the right path. >From Blue Waters support: Static linking is and has been the default on BW when compiling applications for the CPUs. For the GPUs, when you load the cudatoolkit module, it sets XTPE_LIN

Re: [Libmesh-users] compiling libmesh on Cray

2013-08-21 Thread Jim Fonseca
Hi John, Here is the config.log. Many thanks for the suggestions--I will look into those. Thanks, Jim On Wed, Aug 21, 2013 at 2:03 PM, John Peterson wrote: > > > On Wed, Aug 21, 2013 at 12:59 PM, John Peterson wrote: > >> >> >> >> On Wed, Aug 21, 2013 at 12:56 PM, John Peterson >> wrote: >> >

Re: [Libmesh-users] compiling libmesh on Cray

2013-08-21 Thread John Peterson
On Wed, Aug 21, 2013 at 12:59 PM, John Peterson wrote: > > > > On Wed, Aug 21, 2013 at 12:56 PM, John Peterson > wrote: > > > > > > > > > > On Wed, Aug 21, 2013 at 11:42 AM, Jim Fonseca > wrote: > >> > >> Hi John, > >> From make V=1 > >> > >> > > Thanks. > > > > So I guess my next question is: w

Re: [Libmesh-users] compiling libmesh on Cray

2013-08-21 Thread John Peterson
On Wed, Aug 21, 2013 at 12:56 PM, John Peterson wrote: > > > > > On Wed, Aug 21, 2013 at 11:42 AM, Jim Fonseca wrote: >> >> Hi John, >> From make V=1 >> >> > Thanks. > > So I guess my next question is: what does "CC" do on Cray when you try to use it for linking? Does it need to be passed a '-sh

Re: [Libmesh-users] compiling libmesh on Cray

2013-08-21 Thread John Peterson
On Wed, Aug 21, 2013 at 11:42 AM, Jim Fonseca wrote: > Hi John, > From make V=1 > > make[1]: Entering directory > `/mnt/b/projects/sciteam/jna/NEMO5_PETSc3.4_no_MAGMA_new_libmesh/libs/libmesh/libmesh' > /bin/sh ./libtool --tag=CXX --mode=link CC -O2 -felide-constructors > -funroll-loops -fstr

Re: [Libmesh-users] compiling libmesh on Cray

2013-08-21 Thread Jim Fonseca
Hi John, >From make V=1 make[1]: Entering directory `/mnt/b/projects/sciteam/jna/NEMO5_PETSc3.4_no_MAGMA_new_libmesh/libs/libmesh/libmesh' /bin/sh ./libtool --tag=CXX --mode=link CC -O2 -felide-constructors -funroll-loops -fstrict-aliasing -Wdisabled-optimization -fopenmp-o getpot_parse-

Re: [Libmesh-users] compiling libmesh on Cray

2013-08-21 Thread John Peterson
On Wed, Aug 21, 2013 at 9:07 AM, Jim Fonseca wrote: > Hi John, > Yes, it's an email issue. Screenshot attached. > I see. I think it might help if we could see the actual output of libtool, so would you try running 'make V=1' and sending the output? On my machine, for instance, that prints: lib

Re: [Libmesh-users] compiling libmesh on Cray

2013-08-21 Thread Jim Fonseca
Hi John, Yes, it's an email issue. Screenshot attached. Thanks, Jim On Wed, Aug 21, 2013 at 9:49 AM, John Peterson wrote: > This could be an email parsing bug, but I noticed: > > > On Wed, Aug 21, 2013 at 8:41 AM, Jim Fonseca wrote: > >> >> $ /bin/sh ./libtool --silent --tag=CXX --mode=link

Re: [Libmesh-users] compiling libmesh on Cray

2013-08-21 Thread John Peterson
This could be an email parsing bug, but I noticed: On Wed, Aug 21, 2013 at 8:41 AM, Jim Fonseca wrote: > > $ /bin/sh ./libtool --silent --tag=CXX --mode=link CC -O2 > -felide-constructors -funroll-loops -fstrict-aliasing > -Wdisabled-optimization -fopenmp-o getpot_parse-opt > src/apps/

Re: [Libmesh-users] compiling libmesh on Cray

2013-08-21 Thread Jim Fonseca
Thanks Ben, Could you please take a look at where it is failing (config.log attached). For 0.9.2.1 Here is the line that's failing from make -n and the output when I run it. I've $ /bin/sh ./libtool --silent --tag=CXX --mode=link CC -O2 -felide-constructors -funroll-loops -fstrict-aliasing -W

Re: [Libmesh-users] compiling libmesh on Cray

2013-08-20 Thread Jim Fonseca
yes, we are doing make install. but your explanation helped to resolve that issue--thanks! Unfortunately I see I've created a problem with two different discussions on the same thread but at least that first one is solved. Still looking into the dynamic build issue...trying to narrow it down... J

Re: [Libmesh-users] compiling libmesh on Cray

2013-08-20 Thread Kirk, Benjamin (JSC-EG311)
On Aug 20, 2013, at 2:06 PM, Jim Fonseca wrote: > Related questions: is netcdf required? I am trying with it disabled now. > Also, why does the netcdf shared library end up in > (contrib/netcdf/v4/liblib/.libs/libnetcdf.so.7) when all other libraries > seems to be .libs or contrib/.libs? > > Th

Re: [Libmesh-users] compiling libmesh on Cray

2013-08-20 Thread Jim Fonseca
Hi John, No, we are doing dynamic linking. Blue Waters supports dynamic linking and in our development phase, it seems to cause us fewer headaches, so we are not concerned about advantages of static linking right now. I'm pretty sure I was able to do this same configuration with a libmesh developm

Re: [Libmesh-users] compiling libmesh on Cray

2013-08-20 Thread John Peterson
Are you wanting to build statically on the Cray? (That is, are you already configuring with --enable-static --disable-shared?) If so, this might be related to a similar problem we faced on BG/Q, and there is an -all-static flag that can be passed to the link mode of libtool that might help out.

Re: [Libmesh-users] compiling libmesh on Cray

2013-08-20 Thread Jim Fonseca
Hi Minq, Did you ever get this resolved? I am facing the same problem. Thanks, Jim On Wed, Jul 10, 2013 at 5:55 PM, Minq Q wrote: > Hi, > > I am trying to compile libmesh on Cray XE6. Using GNU compiler. > > Then I got an error: > > CC ncgentab.o > CCLD ncgen3 > /usr/bin/ld: attem