gt; ../../../../../../ompi/contrib/vt/vt/vtlib/vt_cudart.c:2439:14: error:
> conflicting types for 'cudaMemcpyFromSymbolAsync'
> /usr/local/cuda/include/cuda_runtime_api.h:4032:39: note: previous
> declaration of 'cudaMemcpyFromSymbolAsync' was here
> ../../../../../../omp
Please keep all three accounts from Dresden.
> Dresden
> =
> knuepfer: Andreas Knuepfer **NO COMMITS IN
> LAST YEAR**
> bwesarg: Bert Wesarg **NO COMMITS IN LAST YEAR**
> jurenz: Matthias Jurenz
>
--
Dr. rer. nat. Andreas Knüpfer
Senior Scientist
T
On Tuesday 28 April 2009, Terry Dontje wrote:
> Has anyone tested running a simple program compiled with mpicc-vt that
> was built on RHEL 5.1 or SLES-10 with gcc under 32 bits?
>
> I am seeing the following errors when running compiled code:
> VampirTrace: BFD: bfd_get_file_flags(): failed
>
>
Hi everybody,
News from the vampir trace integration at last. The current vampir trace
release is included in the TMP tree of the OpenMPI SVN. Now, autoconf scripts
need to be added.
Then the build procedure will look like this:
1) run global OpenMPI configure script
2) the global configure
Finally, VampirTrace is usable from within OpenMPI. From the
tmp/vt-integration/ repository you can get an extended OMPI version:
#> svn co http://svn.open-mpi.org/svn/ompi/tmp/vt-integration
#> cd vt-integration
#> ./autogen.sh
#> ./configure --prefix=/tmp/openmpi_with_vampirtrace/
#> make
#> ma
On Friday 21 September 2007, Jeff Squyres wrote:
> Per an idea that came up recently, can we make it so that ompi_info
> reports the version of VT that is integrated into Open MPI?
good idea, we'll pick it up real soon
Andreas
--
Dipl. Math. Andreas Knuepfer,
Center for Information Services an
Hi Jeff, hi everybody,
quite a few things to comment on. hope i catch them all:
- yes, we might move vanmpirtrace to ./ompi/contrib/vampirtrace/, why not. but
since we agreed on the current location ./tracing/vampirtrace/ we should not
rush it just because another software is coming to openmpi,
Hi Jeff,
unfortunately, we're unable to reproduce this error. Could you pass some more
information about your configure command line? This was done with gcc 4.2 on
mac os X, wasn't it?
Thanks, Andreas
On Tuesday 08 January 2008, Jeff Squyres wrote:
> From today's head (r17068):
>
> Making all
Hi everybody,
the vampirtrace integration arrived at the trunk today. There seems to be one
issue already, but we'll fix this asap.
As a general hint, this is how to completely disable anything we integrated:
configure --enable-contrib-no-build=vt ...
Then again, we'd like to see all t
On Tuesday 29 January 2008, George Bosilca wrote:
> Look like VT do not correctly compute dependencies. A static build
> will fails if libz.a is not installed on the system.
>
> /usr/bin/ld: cannot find -lz
> collect2: ld returned 1 exit status
> make[5]: *** [vtfilter] Error 1
>
>george.
>
th
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
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
Hi Josh, hi everybody,
we'd like to have VampirTrace enabled by default -- well, of course we do ;)
Our main reason is the potential users: As soon as they want to use our tool
they want to use it with the same configuration as the default Open MPI
installation. Making the administrator re-inst
On Monday 11 February 2008, Josh Hursey wrote:
> I've been noticing another problem with the VT integration. If you do
> a "./configure --enable-contrib-no-build=vt" a subsequent 'make
> distclean' will fail in contrib/vt. The 'make distclean' will succeed
> with VT enabled (default).
>
hm, tricky
The VampirTrace integration is already in the trunk. It should be mentioned as
complete somewhere in the misc section.
Andreas
signature.asc
Description: This is a digitally signed message part.
On Thursday 28 February 2008, Jeff Squyres wrote:
> I can't remember if I posted about this before or not -- should we
> disable trunk/VT building by default while the configuration issues
> are being worked out?
Which config issues are you refering to? Is it about the 'make distclean' that
fails
On Thursday 10 April 2008, Swati Kher wrote:
>
> 2) If vampire trace by default is built with openmpi, if I set
> VT_CC flag for compiling my application, where I can view ".vtf" files
> after a parallel run ?
>
Let me answer the second question.
First of all, there is no default VT_CC flag
17 matches
Mail list logo
