|
From: <jt...@cs...> - 2007-12-13 23:01:50
|
Greetings,
I have successfully built and used valgrind on just about every supported
platform and really appreciate the ease with which I'm able to do it, even
the latest version, 3.3.0. On one machine however, I've run into
problems. I believe I had the same trouble with 3.2.3. I'm not sure if
the problem is valgrind's or something machine specific. You tell me:
gmake[2]: Entering directory
`/mnt/cfs/pkgs/PTOOLS/src/valgrind-3.3.0/auxprogs'
mpicc -g -O -fno-omit-frame-pointer -Wall -fpic -shared -m64 \
-I../include \
-o libmpiwrap-AMD64_LINUX.so libmpiwrap.c
/usr/bin/ld:
/usr/local/topspin/mpi/mvapich-0.9.8-2/gnu/lib/libmpich.a(getcount.o):
relocation R_X86_64_32 against `a local symbol' can not be used when
making a shared object; recompile with -fPIC
/usr/local/topspin/mpi/mvapich-0.9.8-2/gnu/lib/libmpich.a: could not read
symbols: Bad value
collect2: ld returned 1 exit status
gmake[2]: *** [libmpiwrap-AMD64_LINUX.so] Error 1
gmake[2]: Leaving directory
`/mnt/cfs/pkgs/PTOOLS/src/valgrind-3.3.0/auxprogs'
gmake[1]: *** [all-recursive] Error 1
gmake[1]: Leaving directory `/mnt/cfs/pkgs/PTOOLS/src/valgrind-3.3.0'
gmake: *** [all] Error 2
[thomasj@jaws-login3 valgrind-3.3.0]$ uname -a
Linux jaws-login3.local 2.6.9-55.0.9.EL_lustre.1.4.11.1_perfctr.2.6.29smp
#37 SMP Sat Oct 27 01:03:31 PDT 2007 x86_64 x86_64 x86_64 GNU/Linux
I've tried adding -fPIC to the compile flags, but I'm wondering if the
compile wants the MPI libs to be compiled with -fPIC (other programs seems
to compile fine on this machine, on the other hand, valgrind compiles fine
on other machines)?? Anyway, does anyone have an idea of the problem?
Apologies in advance if the answer is obvious :)
Thanks,
JT
|
|
From: jimc <jim...@gm...> - 2007-12-13 23:12:42
|
jt...@cs... wrote: > Greetings, > ... > problems. I believe I had the same trouble with 3.2.3. I'm not sure if > the problem is valgrind's or something machine specific. You tell me: > > skimming, it looks like *yesterdays* thread - "Problem building valgrind 3.3.0" |
|
From: Julian S. <js...@ac...> - 2007-12-13 23:20:41
|
It's definitely something along those lines. See a couple of days ago on this list, "[Valgrind-users] Problem building valgrind 3.3.0" (Wed 12 Dec). If you can live without the MPI wrapper library, redo the configure with --without-mpicc. J On Friday 14 December 2007 00:01, jt...@cs... wrote: > Greetings, > > I have successfully built and used valgrind on just about every supported > platform and really appreciate the ease with which I'm able to do it, even > the latest version, 3.3.0. On one machine however, I've run into > problems. I believe I had the same trouble with 3.2.3. I'm not sure if > the problem is valgrind's or something machine specific. You tell me: > > gmake[2]: Entering directory > `/mnt/cfs/pkgs/PTOOLS/src/valgrind-3.3.0/auxprogs' > mpicc -g -O -fno-omit-frame-pointer -Wall -fpic -shared -m64 \ > -I../include \ > -o libmpiwrap-AMD64_LINUX.so libmpiwrap.c > /usr/bin/ld: > /usr/local/topspin/mpi/mvapich-0.9.8-2/gnu/lib/libmpich.a(getcount.o): > relocation R_X86_64_32 against `a local symbol' can not be used when > making a shared object; recompile with -fPIC > /usr/local/topspin/mpi/mvapich-0.9.8-2/gnu/lib/libmpich.a: could not read > symbols: Bad value > collect2: ld returned 1 exit status > gmake[2]: *** [libmpiwrap-AMD64_LINUX.so] Error 1 > gmake[2]: Leaving directory > `/mnt/cfs/pkgs/PTOOLS/src/valgrind-3.3.0/auxprogs' > gmake[1]: *** [all-recursive] Error 1 > gmake[1]: Leaving directory `/mnt/cfs/pkgs/PTOOLS/src/valgrind-3.3.0' > gmake: *** [all] Error 2 > [thomasj@jaws-login3 valgrind-3.3.0]$ uname -a > Linux jaws-login3.local 2.6.9-55.0.9.EL_lustre.1.4.11.1_perfctr.2.6.29smp > #37 SMP Sat Oct 27 01:03:31 PDT 2007 x86_64 x86_64 x86_64 GNU/Linux > > I've tried adding -fPIC to the compile flags, but I'm wondering if the > compile wants the MPI libs to be compiled with -fPIC (other programs seems > to compile fine on this machine, on the other hand, valgrind compiles fine > on other machines)?? Anyway, does anyone have an idea of the problem? > Apologies in advance if the answer is obvious :) > > Thanks, > JT > > ------------------------------------------------------------------------- > SF.Net email is sponsored by: > Check out the new SourceForge.net Marketplace. > It's the best place to buy or sell services > for just about anything Open Source. > http://ad.doubleclick.net/clk;164216239;13503038;w?http://sf.net/marketplac >e _______________________________________________ > Valgrind-users mailing list > Val...@li... > https://lists.sourceforge.net/lists/listinfo/valgrind-users |