Thanks Brian, I was just following the install notes on the cvs page.
Although during the build I get an error about my CFLAGS statement.
It rewrote: CFLAGS=-fastsse -tp k8-64 as: CFLAGS= k8-64 -tp -fastsse
during the remove opt flags statement. Which caused errors for the compiler
;o) The only way I can then pass those flags is to do a -tp=k8-64, which
thankfully is acceptable with pgi for the -tp command, however it may or
may not work with all supported flags. So just an fyi to ayone who runs
with pgi.
Jeff,
LAM compiles and runs the tests from last nights nightly of 7.1a fine.
Hurm... now to debug some f77 that uses cray pointers..... Wish that was
easier!
Doug
At 10:57 AM 6/18/2003 -0500, you wrote:
>It looks like you tried to run the Autotools on a nightly tarball. There
>was an error (now fixed) in one of the Makefile.ams such that a needed .m4
>file wasn't included in the distribution.
>
>But you shouldn't need to run the autotools (or autogen.sh) on the nightly
>tarballs - the configuration files should already be setup. ./configure ;
>make ; make install should be all you need.
>
>Brian
>
>
>
>On Wed, 18 Jun 2003, Doug Farley wrote:
>
> > Heres with the build of todays cvs fresh version of 7.
> >
> > Flags:
> >
> > CC=/opt/pgi/linux86-64/5.0-beta2/bin/pgcc
> > LDFALGS=-stack 10000000,5000000
> > FFLAGS=-fastsse -tp k8-64
> > FC=/opt/pgi/linux86-64/5.0-beta2/bin/pgf90
> > CFLAGS=-fastsse -tp k8-64
> > CXX=/opt/pgi/linux86-64/5.0-beta2/bin/pgCC
> > CXXFLAGS=-fastsse -tp k8-64
> >
> > ./configure --prefix /usr/local/lam71a1-pgi64 --with-rpi=sysv
> > --with-trillium --disable-tv-queue
> >
> >
> > However, I get this error.
> >
> >
> ============================================================================
> > == Final top-level LAM configuration
> >
> ============================================================================
> >
> > *** GNU libtool setup
> > checking for non-GNU ld... /usr/bin/ld
> > checking if the linker (/usr/bin/ld) is GNU ld... yes
> > checking for /usr/bin/ld option to reload object files... -r
> > checking for BSD-compatible nm... /usr/bin/nm -B
> > checking how to recognise dependant libraries... pass_all
> > checking command to parse /usr/bin/nm -B output... ok
> > checking dlfcn.h usability... yes
> > checking dlfcn.h presence... yes
> > checking for dlfcn.h... yes
> > checking for ranlib... ranlib
> > checking for strip... strip
> > checking for objdir... .libs
> > checking for /opt/pgi/linux86-64/5.0-beta2/bin/pgcc option to produce
> > PIC... none
> > checking if /opt/pgi/linux86-64/5.0-beta2/bin/pgcc static
> flag works... yes
> > checking if /opt/pgi/linux86-64/5.0-beta2/bin/pgcc supports -c -o
> file.o... yes
> > checking if /opt/pgi/linux86-64/5.0-beta2/bin/pgcc supports -c -o
> > file.lo... yes
> > checking whether the linker (/usr/bin/ld) supports shared libraries... yes
> > checking how to hardcode library paths into programs... immediate
> > checking whether stripping libraries is possible... yes
> > checking dynamic linker characteristics... GNU/Linux ld.so
> > checking if libtool supports shared libraries... no
> > checking whether to build shared libraries... no
> > checking whether to build static libraries... yes
> > creating libtool
> >
> > *** Miscellaneous final setup
> > checking if want extra wrapper compiler LDFLAGS... no (shared libs
> disabled)
> > ./configure: line 22732: syntax error near unexpected token `$CFLAGS'
> > ./configure: line 22732: ` LAM_MAKE_STRIPPED_FLAGS($CFLAGS)'
> >
> > And I get that without including either of these: --with-trillium
> > --disable-tv-queue, and with --with-rpi=tcp as well. I'm not too sure
> > whats wrong with lines ~22732.
> >
> > That line in question is the blank line before the following:
> >
> > if test "$WANT_TV" = "yes"; then
> > LAM_MAKE_STRIPPED_FLAGS($CFLAGS)
> > CFLAGS_WITHOUT_OPTFLAGS="$s_result"
> > if test "$with_tv_debug_flags" != ""; then
> > TOTALVIEW_DEBUG_FLAGS="$with_tv_debug_flags"
> > else
> > TOTALVIEW_DEBUG_FLAGS="-g"
> > fi
> > else
> > CFLAGS_WITHOUT_OPTFLAGS="$CFLAGS"
> > TOTALVIEW_DEBUG_FLAGS=
> > fi
> >
> > However grepping for 'LAM_MAKE_STRIPPED_FLAGS' in the lam dir finds that
> > the acinclude.m4 references
> > "acinclude.m4:63:sinclude(config/lam_make_stripped_flags.m4)"
> >
> > Although, no where in my $LAMBUILDDIR/config/ is there a file with such a
> > name, or an included function.
> >
> >
> > Hope this helps some.
> >
> >
> > Doug
> >
> >
> >
> >
> >
> > At 10:38 AM 6/17/2003 -0400, you wrote:
> > >On Tue, 17 Jun 2003, Doug Farley wrote:
> > >
> > > > Just to let the community know since i've not seen any msg's about it.
> > > > I have just built 6.5.8 (For comparability between previous runs w/
> > > > 6.5.8 results) with the beta pgi compilers for the AMD Opteron, they
> > > > appear to be running fine at the moment (good old mpi hello world). I
> > > > will have one of my large test cases built by the end of the day, and
> > > > should have some comparable performance. I hope to also have the
> > > > gcc33-64 version built later, however thats not as high as a priority.
> > >
> > >Great -- thanks for the report!
> > >
> > >Would you mind giving the 7.0 tree a whirl as well? We've been promising
> > >the release of 7.0 for a little while and are in the midst of fixing the
> > >(hopefully) last buglets. There's lots more features (and some
> > >performance enhancements) in the 7.0 tree. There's also an extensive user
> > >guide in the 7.0 tarball that talks about all of the new stuff.
> > >
> > >See http://www.lam-mpi.org/beta/ for 7.0 beta tarballs or
> > >http://www.lam-mpi.org/cvs/ for daily CVS snapshots. The CVS snapshots
> > >are marked "7.1", but there's been very little divergence so far --
> > >they're effectively still 7.0.
> > >
> > >--
> > >{+} Jeff Squyres
> > >{+} jsquyres_at_[hidden]
> > >{+} http://www.lam-mpi.org/
> > >_______________________________________________
> > >This list is archived at http://www.lam-mpi.org/MailArchives/lam/
> >
> > ==============================
> > Doug Farley
> >
> > Data Analysis and Imaging Branch
> > Systems Engineering Competency
> > NASA Langley Research Center
> >
> > < D.L.FARLEY_at_[hidden] >
> > < Phone +1 757 864-8141 >
> >
> > _______________________________________________
> > This list is archived at http://www.lam-mpi.org/MailArchives/lam/
> >
>
>--
> Brian Barrett
> LAM/MPI developer and all around nice guy
> Have a LAM/MPI day: http://www.lam-mpi.org/
>_______________________________________________
>This list is archived at http://www.lam-mpi.org/MailArchives/lam/
==============================
Doug Farley
Data Analysis and Imaging Branch
Systems Engineering Competency
NASA Langley Research Center
< D.L.FARLEY_at_[hidden] >
< Phone +1 757 864-8141 >
|
