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 au
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
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/wh
* 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
> >>
> >> Mak
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? I
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
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 Aut
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
On Jan 29, 2008, at 12:13 PM, Matthias Jurenz wrote:
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
shoul
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 add
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
wi
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 P
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:
htt
13 matches
Mail list logo
