Subject: Re: [Boost-build] Compiling Boost.MPI and mpich2 under Suse Linux
From: Michael1984 (m.auli_at_[hidden])
Date: 2010-05-28 14:10:19
The reason why bjam used mpich2 and not mpich was because I still had
mpich2/bin in the path (just after mpich). I suspect that bjam just cannot
use mpich to build mpi because there is not mpicxx in mpich/bin....
> Unfortunately, ./bjam link=static gives me the same error:
> /mnt/thor2/michael/tools/mpich2/lib/libmpich.a(attr_get.o): relocation
> R_X86_64_32 against `a local symbol' can not be used when making a shared
> object; recompile with -fPIC
> /mnt/thor2/michael/tools/mpich2/lib/libmpich.a: could not read symbols:
> Bad value
> collect2: ld returned 1 exit status
> So it's still building dynamic libraries - I don't understand.
> Belcourt, Kenneth wrote:
>> On May 28, 2010, at 11:32 AM, Michael1984 wrote:
>>> I googled now for a while but could not figure out how to build boost
>>> as an archive - can you please give me a hint?
>> bjam link=static ...
>> should do it.
>>> The error messages I quoted previously were still with MPICH2 as I
>>> could not get MPICH to work: Building it works all fine but when
>>> to execute bin/mpicc I get the following:
>>> /usr/lib64/gcc/x86_64-suse-linux/4.3/../../../../lib64/crt1.o: In
>>> (.text+0x20): undefined reference to `main'
>>> collect2: ld returned 1 exit status
>> That's weird, did you install your build of MPICH2 into the /bin
>> directory or is there an pre-installed version on your system?
>> -- Noel
>> Unsubscribe & other changes:
-- View this message in context: http://old.nabble.com/Compiling-Boost.MPI-and-mpich2-under-Suse-Linux-tp28696953p28710204.html Sent from the Boost - Build mailing list archive at Nabble.com.
Boost-Build list run by bdawes at acm.org, david.abrahams at rcn.com, gregod at cs.rpi.edu, cpdaniel at pacbell.net, john at johnmaddock.co.uk