|
From: Matt F. <mat...@gm...> - 2009-02-02 16:02:58
|
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 ...
matt
On Monday 02 February 2009, you wrote:
> What happens if you configure and build in the simplest possible way,
> without the --with-mpicc=/home/mafunk/Packages/mpich2-1.0.8/BUILD/bin/mpicc
> and without CPPFLAGS='-fPIC -noasm' --disable-pie
>
> ?
>
> J
>
> On Monday 02 February 2009, Matt Funk wrote:
> > I guess nobody knows ?
> > I still have no idea what the problem could be ...
> >
> > matt
> >
> > On Tuesday 20 January 2009, Matt Funk wrote:
> > > Hi,
> > >
> > > i am sure i am doing something stupid, but of course i can't figure out
> > > what it is:
> > > - i downloaded valgrid3.4.0 and build it using:
> > > ./configure --prefix=/home/mafunk/Packages/valgrind-3.4.0/BUILD
> > > --with-mpicc=/home/mafunk/Packages/mpich2-1.0.8/BUILD/bin/mpicc
> > > CPPFLAGS='-fPIC -noasm' --disable-pie
> > > (i googled my problem and the -noasm --disable-pie flags were
> > > mentioned, so i tried them but it didn't change anything)
> > >
> > > Anyway, it builds fine, but doing:
> > > /home/mafunk/Packages/valgrind-3.4.0/BUILD/bin/valgrind -v ps
> > > (or my other code)
> > >
> > > gives me:
> > >
> > > ==25081== Memcheck, a memory error detector.
> > > ==25081== Copyright (C) 2002-2008, and GNU GPL'd, by Julian Seward et
> > > al. ==25081== Using LibVEX rev 1878, a library for dynamic binary
> > > translation. ==25081== Copyright (C) 2004-2008, and GNU GPL'd, by
> > > OpenWorks LLP. ==25081== Using valgrind-3.4.0, a dynamic binary
> > > instrumentation framework. ==25081== Copyright (C) 2000-2008, and GNU
> > > GPL'd, by Julian Seward et al. ==25081==
> > > --25081-- Command line
> > > --25081-- ps
> > > --25081-- Startup, with flags:
> > > --25081-- -v
> > > --25081-- Contents of /proc/version:
> > > --25081-- Linux version 2.6.24 (root@bioemag-001) (gcc version 4.1.2
> > > 20061115 (prerelease) (Debian 4.1.1-21)) #7 SMP Wed Feb 6 14:57:55 MST
> > > 2008 --25081-- Arch and hwcaps: AMD64, amd64-sse2
> > > --25081-- Page sizes: currently 4096, max supported 4096
> > > --25081-- Valgrind library
> > > directory: /home/mafunk/Packages/valgrind-3.4.0/BUILD/lib/valgrind
> > > --25081-- Reading syms from /bin/ps (0x400000)
> > > --25081-- object doesn't have a symbol table
> > > --25081-- Reading syms from /lib/ld-2.7.so (0x4000000)
> > > --25081-- Reading debug info from /lib/ld-2.7.so ..
> > > --25081-- .. CRC mismatch (computed 049ac48c wanted e760853c)
> > > --25081-- Reading debug info from /usr/lib/debug/lib/ld-2.7.so ..
> > > --25081-- Reading syms
> > > from
> > > /home/mafunk/Packages/valgrind-3.4.0/BUILD/lib/valgrind/amd64-linux/mem
> > >ch ec k (0x38000000)
> > > --25081-- object doesn't have a dynamic symbol table
> > > --25081-- Reading suppressions
> > > file:
> > > /home/mafunk/Packages/valgrind-3.4.0/BUILD/lib/valgrind/default.supp
> > > --25081-- Reading syms
> > > from
> > > /home/mafunk/Packages/valgrind-3.4.0/BUILD/lib/valgrind/amd64-linux/vgp
> > >re lo ad_core.so (0x4a1d000)
> > > --25081-- Reading syms
> > > from
> > > /home/mafunk/Packages/valgrind-3.4.0/BUILD/lib/valgrind/amd64-linux/vgp
> > >re lo ad_memcheck.so (0x4c1e000)
> > > --25081-- REDIR: 0x4014ec0 (index) redirected to 0x4c22120 (index)
> > > --25081-- REDIR: 0x4015070 (strcmp) redirected to 0x4c22380 (strcmp)
> > > --25081-- REDIR: 0x4015180 (strlen) redirected to 0x4c222b0 (strlen)
> > > --25081-- Reading syms from /lib/libproc-3.2.7.so (0x4033000)
> > > --25081-- object doesn't have a symbol table
> > > --25081-- Reading syms from /lib/libc-2.7.so (0x4e25000)
> > > --25081-- Reading debug info from /lib/libc-2.7.so ..
> > > --25081-- .. CRC mismatch (computed 3d44d45b wanted e52ce9af)
> > > --25081-- Reading debug info from /usr/lib/debug/lib/libc-2.7.so ..
> > > --25081-- REDIR: 0x4ea0460 (rindex) redirected to 0x4c21fd0 (rindex)
> > > --25081-- REDIR: 0x4e9c9e0 (malloc) redirected to 0x4c21260 (malloc)
> > > --25081-- REDIR: 0x4ea0c10 (memchr) redirected to 0x4c22400 (memchr)
> > > --25081-- REDIR: 0x4ea1eb0 (memcpy) redirected to 0x4c23490 (memcpy)
> > > --25081-- REDIR: 0x4e9a9e0 (free) redirected to 0x4c20de0 (free)
> > > --25081-- REDIR: 0x4ea2cf0 (rawmemchr) redirected to 0x4c22600
> > > (rawmemchr) Segmentation fault
> > >
> > >
> > > I build valgrind before on another machine which worked fine.
> > > Any ideas what is going on.
> > >
> > > I am on a debian etch distribution (with backports).
> > >
> > >
> > > thanks
> > > matt
> > >
> > > -----------------------------------------------------------------------
> > >-- -- --- This SF.net email is sponsored by:
> > > SourcForge Community
> > > SourceForge wants to tell your story.
> > > http://p.sf.net/sfu/sf-spreadtheword
> > > _______________________________________________
> > > Valgrind-users mailing list
> > > Val...@li...
> > > https://lists.sourceforge.net/lists/listinfo/valgrind-users
> >
> > -------------------------------------------------------------------------
> >-- --- This SF.net email is sponsored by:
> > SourcForge Community
> > SourceForge wants to tell your story.
> > http://p.sf.net/sfu/sf-spreadtheword
> > _______________________________________________
> > Valgrind-users mailing list
> > Val...@li...
> > https://lists.sourceforge.net/lists/listinfo/valgrind-users
|