On Fri, Mar/13/2009 03:59:04PM, Coleman Kane wrote: > On Fri, 2009-03-13 at 14:44 -0500, Ethan Mallove wrote: > > On Fri, Mar/13/2009 03:24:17PM, Coleman Kane wrote: > > > On Fri, 2009-03-13 at 13:11 -0500, Ethan Mallove wrote: > > > > On Thu, Mar/12/2009 07:49:02PM, Ralf Wildenhues wrote: > > > > > 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., > > > > > > > > > > > > [SNIP] > > > > > > > > > > I wonder: if you do the build with g++, then GNU ld will probably just > > > > > skip over the wrong libstdc++ and keep searching until it finds the 32 > > > > > bit one later in the search path, right? > > > > > > > > > > Can you work around the issue by adding -L/usr/lib32 early in LDFLAGS? > > > > > > > > > > > > > I'll give that a try.
Configuring with LDFLAGS=-L/usr/lib seemed to do the trick (on SuSE 9 and RHEL 4, anyway). Thanks! > > > > > > > > -Ethan > > > > > > > > > > > > > Thanks, > > > > > Ralf > > > > > > It thinks your host system is "x86_64-unknown-linux-gnu". > > > > > > Maybe you need --host=i386-unknown-linux-gnu in your configure args? > > > > I haven't needed to do this with other compilers (e.g., GCC, Intel, > > and Sun Studio). Is it possible the "unknown" would only wreak havoc > > in the case of the Pathscale compilers? > > > > -Ethan > > > > > > The "unknown" part should be irrelevant. My point was that you are > telling the autoconf/automake configure system (and maybe libtool too) > that you want to build an x86_64 project, but then with the -m32 > compiler flag, you tell the compiler that you want to generate i386 > code. > > So I suggest trying to tell configure to build a 32-bit project by > setting host to "i386-unknown-linux-gnu", along with specifying your > -m32 flag to the compiler. See if that helps out at all. Configuring with --host=i386-unknown-linux-gnu, I end up getting: output from link -dump -symbols: link: too many arguments Try `link --help' for more information. configure:35483: error: Could not determine Fortran naming convention. I think the LDFLAGS=-L/usr/lib workaround was all I needed. Thanks, Ethan > > -- > Coleman Kane > _______________________________________________ http://lists.gnu.org/mailman/listinfo/libtool