|
From: James <ja...@ch...> - 2009-02-02 18:24:30
|
Hi,
I'm trying to install the latest release of Valgrind (3.4.0) on my
machine, which
has an Intel Core2 Duo processor running SUSE 11.0 (64 bit), but am
getting errors
in configuration and compilation.
First, when I do the configure, I get messages
VG_ARCH_MAX = amd64
VG_ARCH_PRI = amd64
Primary build target: AMD64_LINUX
Secondary build target: X86_LINUX
The machine has an Intel Core2 Duo processor, not AMD. I don't see any
options in
the configure or any of the included files that would change it. How do I
get it
configured for the correct architecture?
Second, I tried to do a make anyway, on the chance that it might work for
my particular
problem even with the wrong architecture, but I get a number of warnings
about casting
pointer to integer of different size, then a final error
/usr/lib64/gcc/x86_64-suse-linux/4.3/../../../../x86_64-suse-linux/bin/ld:
/opt/mpich2/lib/libmpich.a(comm_rank.o): relocation R_X86_64_32 against
`a local symbol'
can not be used when making a shared object; recompile with -fPIC
/opt/mpich2/lib/libmpich.a: could not read symbols: Bad value
collect2: ld returned 1 exit status
which aborts the compilation.
Any suggestions on how I can get Valgrind to compile & install? The
problem I need to use
Valgrind on doesn't use MPI, BTW, so that part could just be skipped if
there's a way to
do it.
Thanks,
James
|
|
From: Tom H. <to...@co...> - 2009-02-02 18:42:29
|
James wrote: > First, when I do the configure, I get messages > > VG_ARCH_MAX = amd64 > VG_ARCH_PRI = amd64 > > Primary build target: AMD64_LINUX > Secondary build target: X86_LINUX > > The machine has an Intel Core2 Duo processor, not AMD. I don't see any > options in > the configure or any of the included files that would change it. How do I > get it > configured for the correct architecture? AMD64 is just the name we use for the 64 bit x86 architecture, which was after all created by AMD. It works just fine on 64 bit Intel processors. > /usr/lib64/gcc/x86_64-suse-linux/4.3/../../../../x86_64-suse-linux/bin/ld: > /opt/mpich2/lib/libmpich.a(comm_rank.o): relocation R_X86_64_32 against > `a local symbol' > can not be used when making a shared object; recompile with -fPIC > /opt/mpich2/lib/libmpich.a: could not read symbols: Bad value > collect2: ld returned 1 exit status > > which aborts the compilation. See Julian's email of a few hours ago - either uninstall mpicc or configure --with-mpicc=/some/path/which/does/not/exist to stop it trying to build the mpi wrappers. Either that or you will need to find a shared library version of the mpich library as you can't link a static library into a shared library on amd64. Tom -- Tom Hughes (to...@co...) http://www.compton.nu/ |