On Thu, 2009-03-12 at 19:54 +0100, Ralf Wildenhues wrote:
> Hello Coleman,
>
> * Coleman Kane wrote on Thu, Mar 12, 2009 at 07:22:31PM CET:
> >
> > Libtool doesn't perform much low-level investigation of the library file
> > types, nor does it rewrite paths to accommodate the 20-million different
Hello Coleman,
* Coleman Kane wrote on Thu, Mar 12, 2009 at 07:22:31PM CET:
>
> Libtool doesn't perform much low-level investigation of the library file
> types, nor does it rewrite paths to accommodate the 20-million different
> ways that vendors install 32/64-bit libraries on the same system.
Hello Ethan,
* Ethan Mallove wrote on Thu, Mar 12, 2009 at 05:25:50PM CET:
> Libtool is trying to link in 64-bit libs on a -m32 compile with the
> Pathscale C++ compiler. E.g.,
>
> /bin/sh ../../../libtool --tag=CXX --mode=link pathCC -O3 -DNDEBUG -Wall
> -m32 -Wundef -Wno-long-long -finli
Something (probably in configure.ac) is picking up your lib64 path and
adding it to your LIBS or LDFLAGS. This is typically done by (broken?)
autoconf m4 macros that get included (such as older sdl.m4 versions) or
from using the wrong PKG_CONFIG_PATH in your environment.
I'd suggest making sure th
Hello,
Libtool is trying to link in 64-bit libs on a -m32 compile with the
Pathscale C++ compiler. E.g.,
/bin/sh ../../../libtool --tag=CXX --mode=link pathCC -O3 -DNDEBUG -Wall
-m32 -Wundef -Wno-long-long -finline-functions -fexceptions -pthread
-export-dynamic -fexceptions -o libmpi_
