Open MPI logo

Open MPI Development Mailing List Archives

  |   Home   |   Support   |   FAQ   |   all Development mailing list

Subject: Re: [OMPI devel] vt compiler warnings and errors
From: Jeff Squyres (jsquyres_at_[hidden])
Date: 2008-01-31 13:10:36


Ah -- I didn't notice this before -- do you have a configure script
committed to SVN? If so, this could be the problem.

Whether what Tim sees happens or not will depend on the timestamps
that SVN puts on configure and all of the files dependent upon
configure (Makefile.in, Makefile, ...etc.) in the VT tree. If some of
them have "bad" timestamps, then the dependencies in the Makefiles can
end up re-running VT's configure, re-create configure, etc.

Is there a way to get OMPI's autogen to also autogen the VT software?
This would ensure one, consistent set of timestamps (not dependent
upon what timestamps SVN wrote to your filesystem for these sensitive
files).

On Jan 31, 2008, at 12:36 PM, Matthias Jurenz wrote:

> Hi Tim,
>
> that seems wrong for me, too. I could not reproduce this on my
> computer.
> The VT-integration comes with an own configure script, which will
> not created by the OMPI's autogen.sh.
> I have not really an idea what's going wrong... I suppose, the
> problem is that you use another version
> of the Autotools as I have used to bootstap VT ?!? The VT's
> configure script was created by following
> version of the Autotools:
>
> autoconf 2.61, automake 1.10, libtool 1.5.24.
>
> Which version of the Autotools you are using to boostrap OpenMPI ?
>
>
> Matthias
>
>
> On Do, 2008-01-31 at 08:09 -0500, Tim Prins wrote:
>>
>> Hi Matthias,
>>
>> I just noticed something else that seems odd. On a fresh checkout,
>> I did
>> a autogen and configure. Then I type 'make clean'. Things seem to
>> progress normally, but once it gets to ompi/contrib/vt/vt/extlib/
>> otf, a
>> new configure script gets run.
>>
>> Specifically:
>> [tprins_at_sif test]$ make clean
>> <lots of output>
>> Making clean in otf
>> make[5]: Entering directory
>> `/san/homedirs/tprins/sif/test/ompi/contrib/vt/vt/extlib/otf'
>> cd . && /bin/sh
>> /u/tprins/sif/test/ompi/contrib/vt/vt/extlib/otf/missing --run
>> automake-1.10 --gnu
>> cd . && /bin/sh /u/tprins/sif/test/ompi/contrib/vt/vt/extlib/otf/
>> missing
>> --run autoconf
>> /bin/sh ./config.status --recheck
>> running CONFIG_SHELL=/bin/sh /bin/sh ./configure --with-zlib-lib=-lz
>> --prefix=/usr/local --exec-prefix=/usr/local --bindir=/usr/local/bin
>> --libdir=/usr/local/lib --includedir=/usr/local/include
>> --datarootdir=/usr/local/share/vampirtrace
>> --datadir=${prefix}/share/${PACKAGE_TARNAME}
>> --docdir=${prefix}/share/${PACKAGE_TARNAME}/doc --cache-file=/dev/
>> null
>> --srcdir=. CXXFLAGS=-g -Wall -Wundef -Wno-long-long -finline-
>> functions
>> -pthread LDFLAGS= LIBS=-lnsl -lutil -lm CPPFLAGS= CFLAGS=-g -Wall
>> -Wundef -Wno-long-long -Wsign-compare -Wmissing-prototypes
>> -Wstrict-prototypes -Wcomment -pedantic
>> -Werror-implicit-function-declaration -finline-functions
>> -fno-strict-aliasing -pthread FFLAGS= --no-create --no-recursion
>> checking build system type... x86_64-unknown-linux-gnu
>> <configure output>
>> <rest of make clean>
>>
>> Not sure if this is expected behavior, but it seems wrong to me.
>>
>> Thanks,
>>
>> Tim
>>
>> Matthias Jurenz wrote:
>> > Hello,
>> >
>> > all three VT related errors which MTT reported should be fixed now.
>> >
>> > 516:
>> > The fix from George Bosilca at this morning should work on MacOS
>> PPC.
>> > Thanks!
>> >
>> > 517:
>> > The compile error occurred due to a missing header include.
>> > Futhermore, the compiler warnings should be also fixed.
>> >
>> > 518:
>> > I have added a check whether MPI I/O is available and add the
>> > corresponding VT's
>> > configure option to enable/disable MPI I/O support. Therefor I
>> used the
>> > variable
>> > "define_mpi_io" from 'ompi/mca/io/configure.m4'. Is that o.k. or
>> should
>> > I use another
>> > variable ?
>> >
>> >
>> > Matthias
>> >
>> >
>> > On Di, 2008-01-29 at 09:19 -0500, Jeff Squyres wrote:
>> >> I got a bunch of compiler warnings and errors with VT on the PGI
>> >> compiler last night -- my mail client won't paste it in
>> nicely. :-(
>> >>
>> >> See these MTT reports for details:
>> >>
>> >> - On Absoft systems:
>> >> http://www.open-mpi.org/mtt/index.php?do_redir=516
>> >> - On Cisco systems:
>> >> With PGI compilers:
>> >> http://www.open-mpi.org/mtt/index.php?do_redir=517
>> >> With GNU compilers:
>> >> http://www.open-mpi.org/mtt/index.php?do_redir=518
>> >>
>> >> The output may be a bit hard to read -- for MTT builds, we
>> separate
>> >> the stdout and stderr into 2 streams. So you kinda have to
>> merge them
>> >> in your head; sorry...
>> >>
>> > --
>> > Matthias Jurenz,
>> > Center for Information Services and
>> > High Performance Computing (ZIH), TU Dresden,
>> > Willersbau A106, Zellescher Weg 12, 01062 Dresden
>> > phone +49-351-463-31945, fax +49-351-463-37773
>> >
>> >
>> >
>> ------------------------------------------------------------------------
>> >
>> > _______________________________________________
>> > devel mailing list
>> > devel_at_[hidden]
>> > http://www.open-mpi.org/mailman/listinfo.cgi/devel
>>
>> _______________________________________________
>> devel mailing list
>> devel_at_[hidden]
>> http://www.open-mpi.org/mailman/listinfo.cgi/devel
>>
> --
> Matthias Jurenz,
> Center for Information Services and
> High Performance Computing (ZIH), TU Dresden,
> Willersbau A106, Zellescher Weg 12, 01062 Dresden
> phone +49-351-463-31945, fax +49-351-463-37773
> _______________________________________________
> devel mailing list
> devel_at_[hidden]
> http://www.open-mpi.org/mailman/listinfo.cgi/devel

-- 
Jeff Squyres
Cisco Systems