Actually, I think that mpicc is doing exactly the Right Thing.
If you don't specify -m32, the underlying compiler is going to default
to 64 bit builds (and libraries), so it naturally tries the /usr/lib64
stuff. But when you supply -m32, it knows that you want to do 32 bit
builds and uses
FYI, this worked and OMPI compiled but mpicc tries to use the 64bit
libraries. Doesn't appear that -m32 is being passed in the configure or
whatever down into mpicc. Once I dropped -m32 on my mpicc I was able to
do 32bit compiles using mpicc on a 64bit machine.
Looks like there's definately
Hi Nathan, Jeff,
* Jeff Squyres wrote on Tue, Sep 27, 2005 at 09:39:59PM CEST:
> This looks like it *might* be a libtool problem -- it's picking up the
> /usr/lib64/libstdc++.so when you're compiling in 32 bit mode (and
> therefore barfing).
Yep, I think it is.
> Can you send the libtool com
This looks like it *might* be a libtool problem -- it's picking up the
/usr/lib64/libstdc++.so when you're compiling in 32 bit mode (and
therefore barfing).
Can you send the libtool command that immediately preceded this link
line?
As a workaround, you should be able to --disable-cxx to d
