Bug 154274 - Can't build auxprogs/libmpiwrap under AMD64_LINUX
Summary: Can't build auxprogs/libmpiwrap under AMD64_LINUX
Status: RESOLVED DUPLICATE of bug 154240
Alias: None
Product: valgrind
Classification: Developer tools
Component: general (show other bugs)
Version: 3.3.0
Platform: Compiled Sources Linux
: NOR normal
Target Milestone: ---
Assignee: Julian Seward
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2007-12-18 15:58 UTC by Christophe Lyon
Modified: 2009-06-29 09:03 UTC (History)
1 user (show)

See Also:
Latest Commit:
Version Fixed In:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Christophe Lyon 2007-12-18 15:58:21 UTC
When building the whole valgrind-3.3.0 from sources under x86_64 linux (Red Hat
RHEL-3), I get a failure when creating libmpiwrap-AMD64_LINUX.so:

ld:
/usr/lib/gcc-lib/x86_64-redhat-linux/3.2.3/../../../../lib64/libmpi.a(laminit.o):
relocation R_X86_64_32 against `a local symbol' can not be used when making a
shared object; recompile with -fPIC
/usr/lib/gcc-lib/x86_64-redhat-linux/3.2.3/../../../../lib64/libmpi.a: could not
read symbols: Bad value

Even though I compile with:
mpicc -g -O -fno-omit-frame-pointer -Wall -fPIC -shared -m64 \
		-I../include \
		-o libmpiwrap-AMD64_LINUX.so libmpiwrap.c

Maybe I could just disable building in auxprogs?

In addition, note that I compile the rest of valgrind with a hand-installed
GCC-4.2.2 (ie more recent than the machine's default - 3.3.3), could this cause
further problems?
Comment 1 Nicholas Nethercote 2009-06-29 09:01:47 UTC
The build system has been improved quite a bit recently, including how the MPI libs are built.  Christophe, I will assume that these changes have fixed the problem.  If not, please reopen this bug.  Thanks.
Comment 2 Nicholas Nethercote 2009-06-29 09:03:38 UTC
Actually, I now see this is a dup of bug 154240.

*** This bug has been marked as a duplicate of bug 154240 ***