|
From: Vrijendra G. <vri...@gm...> - 2008-07-30 06:40:01
|
Hi Folks,
I get following error on a make:
--snip--
mpicc -g -O -fno-omit-frame-pointer -Wall -fpic -shared -m64 \
-I../include \
-o libmpiwrap-AMD64_LINUX.so libmpiwrap.c
/usr/bin/ld: /usr/lib64/libmpi.a(laminit.o): relocation R_X86_64_32S against
`lam_mpi_comm_world' can not be used when making a shared object; recompile
with -fPIC
/usr/lib64/libmpi.a: could not read symbols: Bad value
collect2: ld returned 1 exit status
mpicc: No such file or directory
make[2]: *** [libmpiwrap-AMD64_LINUX.so] Error 1
make[2]: Leaving directory `/root/vrigo/valgrind/valgrind-3.3.1/auxprogs'
make[1]: *** [all-recursive] Error 1
make[1]: Leaving directory `/root/vrigo/valgrind/valgrind-3.3.1'
make: *** [all] Error 2
--snip--
I have downloaded the valgrind-3-3-1.tar.bz2
from //www.valgrind.org/downloads/valgrind-3.3.1.tar.bz2, run configure
without any options and did a make (also without any options)?
Can someone please help?
My system is a RHEL4 on Intel Xeon.
--snip--
[root@thorpc251 valgrind-3.3.1]# cat /etc/redhat-release
Red Hat Enterprise Linux AS release 4 (Nahant Update 3)
[root@thorpc251 valgrind-3.3.1]# cat /proc/cpuinfo
processor : 0
vendor_id : GenuineIntel
cpu family : 15
model : 3
model name : Intel(R) Xeon(TM) CPU 2.80GHz
stepping : 4
cpu MHz : 2793.085
cache size : 1024 KB
physical id : 0
siblings : 2
--snip--
thanks!
Vrijendra
|
|
From: Julian S. <js...@ac...> - 2008-07-30 06:52:27
|
The build system is getting confused by your MPI implementation. Try rerunning configure with --with-mpicc=any_bogus_name_will_do and see if that helps. J On Wednesday 30 July 2008 08:36, Vrijendra Gokhale wrote: > Hi Folks, > > I get following error on a make: > > --snip-- > mpicc -g -O -fno-omit-frame-pointer -Wall -fpic -shared -m64 \ > -I../include \ > -o libmpiwrap-AMD64_LINUX.so libmpiwrap.c > /usr/bin/ld: /usr/lib64/libmpi.a(laminit.o): relocation R_X86_64_32S against > `lam_mpi_comm_world' can not be used when making a shared object; recompile > with -fPIC > /usr/lib64/libmpi.a: could not read symbols: Bad value > collect2: ld returned 1 exit status > mpicc: No such file or directory > make[2]: *** [libmpiwrap-AMD64_LINUX.so] Error 1 > make[2]: Leaving directory `/root/vrigo/valgrind/valgrind-3.3.1/auxprogs' > make[1]: *** [all-recursive] Error 1 > make[1]: Leaving directory `/root/vrigo/valgrind/valgrind-3.3.1' > make: *** [all] Error 2 > --snip-- > > I have downloaded the valgrind-3-3-1.tar.bz2 > from //www.valgrind.org/downloads/valgrind-3.3.1.tar.bz2, run configure > without any options and did a make (also without any options)? > > Can someone please help? > > My system is a RHEL4 on Intel Xeon. > > --snip-- > [root@thorpc251 valgrind-3.3.1]# cat /etc/redhat-release > Red Hat Enterprise Linux AS release 4 (Nahant Update 3) > [root@thorpc251 valgrind-3.3.1]# cat /proc/cpuinfo > processor : 0 > vendor_id : GenuineIntel > cpu family : 15 > model : 3 > model name : Intel(R) Xeon(TM) CPU 2.80GHz > stepping : 4 > cpu MHz : 2793.085 > cache size : 1024 KB > physical id : 0 > siblings : 2 > --snip-- > > thanks! > > Vrijendra > > > ------------------------------------------------------------------------- > This SF.Net email is sponsored by the Moblin Your Move Developer's challenge > Build the coolest Linux based applications with Moblin SDK & win great prizes > Grand prize is a trip for two to an Open Source event anywhere in the world > http://moblin-contest.org/redirect.php?banner_id=100&url=/ > _______________________________________________ > Valgrind-users mailing list > Val...@li... > https://lists.sourceforge.net/lists/listinfo/valgrind-users > |
|
From: Vrijendra G. <vri...@gm...> - 2008-07-30 09:16:40
|
Julian Seward <jseward <at> acm.org> writes: > > > The build system is getting confused by your MPI implementation. > Try rerunning configure with --with-mpicc=any_bogus_name_will_do > and see if that helps. > > J Thanks for your reply. Unfortunately configure still thinks this is an AMD box :-( output of configure --snip-- [root@thorpc251 valgrind-3.3.1]# ./configure --with- mpicc=any_bogus_name_will_do . . . Primary build target: AMD64_LINUX Secondary build target: X86_LINUX Default supp files: xfree-3.supp xfree-4.supp glibc-2.34567-NPTL- helgrind.supp glibc-2.3.supp --snip-- |
|
From: Tom H. <to...@co...> - 2008-07-30 09:23:03
|
In message <loo...@po...>
Vrijendra Gokhale <vri...@gm...> wrote:
> Julian Seward <jseward <at> acm.org> writes:
>
>> The build system is getting confused by your MPI implementation.
>> Try rerunning configure with --with-mpicc=any_bogus_name_will_do
>> and see if that helps.
>
> Thanks for your reply.
>
> Unfortunately configure still thinks this is an AMD box :-(
No, it thinks it is a machine with the amd64 (aka x86_64) architecture
which I believe it is.
Tom
--
Tom Hughes (to...@co...)
http://www.compton.nu/
|
|
From: Julian S. <js...@ac...> - 2008-07-30 09:32:08
|
On Wednesday 30 July 2008 11:22, Tom Hughes wrote: > In message <loo...@po...> > Vrijendra Gokhale <vri...@gm...> wrote: > > > Julian Seward <jseward <at> acm.org> writes: > > > >> The build system is getting confused by your MPI implementation. > >> Try rerunning configure with --with-mpicc=any_bogus_name_will_do > >> and see if that helps. > > > > Thanks for your reply. > > > > Unfortunately configure still thinks this is an AMD box :-( > > No, it thinks it is a machine with the amd64 (aka x86_64) architecture > which I believe it is. Try adding --enable-only32bit if you want only a 32-bit build. J |
|
From: Vrijendra G. <vri...@gm...> - 2008-07-30 18:26:57
|
Julian Seward <jseward <at> acm.org> writes: > > On Wednesday 30 July 2008 11:22, Tom Hughes wrote: > > In message <loom.20080730T091052-119 <at> post.gmane.org> > > Vrijendra Gokhale <vrijendra <at> gmail.com> wrote: > > > > > Julian Seward <jseward <at> acm.org> writes: > > > > > >> The build system is getting confused by your MPI implementation. > > >> Try rerunning configure with --with-mpicc=any_bogus_name_will_do > > >> and see if that helps. > > > > > > Thanks for your reply. > > > > > > Unfortunately configure still thinks this is an AMD box > > > > No, it thinks it is a machine with the amd64 (aka x86_64) architecture > > which I believe it is. > > Try adding --enable-only32bit if you want only a 32-bit build. > > J Thanks! That worked like a charm. configure, make and make install went flawlessly. I wonder why the 64 bit build did not go through? Regards, Vrijendra |