|
From: Julian S. <js...@ac...> - 2009-02-02 16:07:44
|
On Monday 02 February 2009, Matt Funk wrote: > When i do a simple: > ./configure --prefix=/home/mafunk/Packages/valgrind-3.4.0/BUILD > it configures. However it fails during the build with: > > mpicc -g -O -fno-omit-frame-pointer -Wall -fpic -shared -m64 \ > -I../include \ > -o libmpiwrap-AMD64_LINUX.so libmpiwrap.c > libmpiwrap.c: In function 'walk_type': > libmpiwrap.c:651: warning: cast from pointer to integer of different size > libmpiwrap.c:652: warning: cast from pointer to integer of different size > libmpiwrap.c:657: warning: cast from pointer to integer of different size > libmpiwrap.c:658: warning: cast from pointer to integer of different size > libmpiwrap.c:663: warning: cast from pointer to integer of different size > libmpiwrap.c:664: warning: cast from pointer to integer of different size > libmpiwrap.c:669: warning: cast from pointer to integer of different size > libmpiwrap.c:670: warning: cast from pointer to integer of different size > libmpiwrap.c:675: warning: cast from pointer to integer of different size > libmpiwrap.c:676: warning: cast from pointer to integer of different size > libmpiwrap.c:681: warning: cast from pointer to integer of different size > libmpiwrap.c:682: warning: cast from pointer to integer of different size > libmpiwrap.c: In function 'maybe_complete': > libmpiwrap.c:1306: warning: format '%p' expects type 'void *', but argument > 5 has type 'MPI_Request' > /usr/bin/ld: /usr/local/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 > /usr/local/lib/libmpich.a: could not read symbols: Bad value > collect2: ld returned 1 exit status > make[2]: *** [libmpiwrap-AMD64_LINUX.so] Error 1 > make[2]: Leaving directory `/home/mafunk/Packages/valgrind-3.4.0/auxprogs' > make[1]: *** [all-recursive] Error 1 > make[1]: Leaving directory `/home/mafunk/Packages/valgrind-3.4.0' > make: *** [all] Error 2 > > So that is why it tried to pass some of those flags ... Yes. Known problem. Configure again with --with-mpicc=/some/path/that/does/not/exist, so that it will not try to use mpicc at all. J |