Re: [OMPI devel] vt compiler warnings and errors
Hi Everbody, we discussed this issue here a lot. Indeed, we were putting the contents of the VampirTrace tarball to the trunk (via the vendor branch stuff). Then again, this is no virtue by itself, is it? So we agree to removing the configure scripts from the SVN and having it created by the autogen script. This might resolve possible problems because of differing autoconf versions etc. See/hear you at the telco, Andreas On Friday 01 February 2008, Jeff Squyres wrote: > On Feb 1, 2008, at 5:35 AM, Ralf Wildenhues wrote: > > These files do not belong in SVN, they are generated by aclocal: > > ompi/contrib/vt/vt/extlib/otf/aclocal.m4 > > ompi/contrib/vt/vt/aclocal.m4 > > I think both of these have their own configure scripts, meaning that > they were autoconfed/automaked/whatever before they were put into OMPI. > > And in hindsight, this fits in with exactly what our original goal > was: take a VT tarball and dump it into OMPI's SVN. Doh! > > So I think the question still remains: can we hook VT's autoconf (et > al.) requirements into the top-level autogen.sh so that the trunk copy > of vt doesn't have configure/aclocal.m4/etc. and OMPI's top-level > autogen.sh will create them? -- Dipl. Math. Andreas Knuepfer, Center for Information Services and High Performance Computing (ZIH), TU Dresden, Willersbau A114, Zellescher Weg 12, 01062 Dresden phone +49-351-463-38323, fax +49-351-463-37773 signature.asc Description: This is a digitally signed message part.
Re: [OMPI devel] vt compiler warnings and errors
VT guys -- any thoughts on this? On Feb 1, 2008, at 8:10 AM, Jeff Squyres wrote: On Feb 1, 2008, at 5:35 AM, Ralf Wildenhues wrote: These files do not belong in SVN, they are generated by aclocal: ompi/contrib/vt/vt/extlib/otf/aclocal.m4 ompi/contrib/vt/vt/aclocal.m4 I think both of these have their own configure scripts, meaning that they were autoconfed/automaked/whatever before they were put into OMPI. And in hindsight, this fits in with exactly what our original goal was: take a VT tarball and dump it into OMPI's SVN. Doh! So I think the question still remains: can we hook VT's autoconf (et al.) requirements into the top-level autogen.sh so that the trunk copy of vt doesn't have configure/aclocal.m4/etc. and OMPI's top-level autogen.sh will create them? -- Jeff Squyres Cisco Systems ___ devel mailing list de...@open-mpi.org http://www.open-mpi.org/mailman/listinfo.cgi/devel -- Jeff Squyres Cisco Systems
Re: [OMPI devel] vt compiler warnings and errors
On Feb 1, 2008, at 5:35 AM, Ralf Wildenhues wrote: These files do not belong in SVN, they are generated by aclocal: ompi/contrib/vt/vt/extlib/otf/aclocal.m4 ompi/contrib/vt/vt/aclocal.m4 I think both of these have their own configure scripts, meaning that they were autoconfed/automaked/whatever before they were put into OMPI. And in hindsight, this fits in with exactly what our original goal was: take a VT tarball and dump it into OMPI's SVN. Doh! So I think the question still remains: can we hook VT's autoconf (et al.) requirements into the top-level autogen.sh so that the trunk copy of vt doesn't have configure/aclocal.m4/etc. and OMPI's top-level autogen.sh will create them? -- Jeff Squyres Cisco Systems
Re: [OMPI devel] vt compiler warnings and errors
* Jeff Squyres wrote on Thu, Jan 31, 2008 at 07:10:36PM CET: > Ah -- I didn't notice this before -- do you have a configure script > committed to SVN? If so, this could be the problem. > > On Do, 2008-01-31 at 08:09 -0500, Tim Prins wrote: [...] > >> [tprins@sif test]$ make clean > >> > >> 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 [...] These files do not belong in SVN, they are generated by aclocal: ompi/contrib/vt/vt/extlib/otf/aclocal.m4 ompi/contrib/vt/vt/aclocal.m4 Cheers, Ralf
Re: [OMPI devel] vt compiler warnings and errors
Hi everybody, now this is an interesting effect. After a fresh checkout all files have the actual time, haven't they? Is the timestamp explicitly saved somewhere? Could it be, that this is newer than Tim's local time yesterday? Maybe the system time is not set to UTC or something like this? If so, then it should be possible to reproduce this today. Could you give it a try, Tim? Another cause could be slight differences in files' times because one is checked out earlier than the other. However, OTF's configure ran before during the first global configure. Therefore, all files' timestamps should be correct after this. So I don't believe in this explanation. What do you think? -- Dipl. Math. Andreas Knuepfer, Center for Information Services and High Performance Computing (ZIH), TU Dresden, Willersbau A114, Zellescher Weg 12, 01062 Dresden phone +49-351-463-38323, fax +49-351-463-37773 signature.asc Description: This is a digitally signed message part.
Re: [OMPI devel] vt compiler warnings and errors
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@sif test]$ make clean
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
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
> de...@open-mpi.org
> http://www.open-mpi.org/mailman/listinfo.cgi/devel
___
devel mailing list
de...@open-mpi.org
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
Re: [OMPI devel] vt compiler warnings and errors
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@sif test]$ make clean
>
> 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
>
>
>
> 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
> > de...@open-mpi.org
> > http://www.open-mpi.org/mailman/listinfo.cgi/devel
>
> ___
> devel mailing list
> de...@open-mpi.org
> 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
smime.p7s
Description: S/MIME cryptographic signature
Re: [OMPI devel] vt compiler warnings and errors
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@sif test]$ make clean
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
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
de...@open-mpi.org
http://www.open-mpi.org/mailman/listinfo.cgi/devel
Re: [OMPI devel] vt compiler warnings and errors
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 smime.p7s Description: S/MIME cryptographic signature
Re: [OMPI devel] vt compiler warnings and errors
On Jan 29, 2008, at 9:24 AM, Tim Prins wrote: - 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 Note that this last link points to the IU failures when configuring with '--disable-mpi-io' which I reported earlier this morning. Oops! My bad -- Tim's right. Note that there are a lot of compiler warnings in there, but that might be a side effect of the IO layer being disabled. -- Jeff Squyres Cisco Systems
Re: [OMPI devel] vt compiler warnings and errors
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 Note that this last link points to the IU failures when configuring with '--disable-mpi-io' which I reported earlier this morning. Tim
[OMPI devel] vt compiler warnings and errors
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... -- Jeff Squyres Cisco Systems
