On Tue, Dec 10, 2013 at 12:18 PM, Derek Gaston <friedmud@gmail.com> wrote:
Well - it's BG/Q... so ultimately it is using some weird compiler - but I'm using a GCC "wrapper" for them so that it looks like GCC on the outside.  It's all very tough to explain...

Fair enough.

BUT - the admins of the machine pointed me to the following:

And in the last bullet there it says that you can set some autoconf variables at configure time to restrict the paths libtool searches in.

OK, cool, thanks for the link.
BUT - I really don't understand.  Does this mean when configuring libMesh - or when configuring the build of libtool - does anyone know how or when I would set these variables?

 When configuring libMesh (search the configure script in libMesh for this variable and you should see it). So, when configuring libMesh, do 

configure lt_cv_sys_lib_search_path_spec="/bgsys/drivers/toolchain/V1R2M0-efix23/gnu-linux/powerpc64-bgq-linux/lib" <plus your other configure options>

There's no dynamic linking on BG/Q (right?), so I don't think you'll need to set the dlsearch one. Sorry I can't test this directly, but I don't have access to  a BG/Q system.

(FWIW, I think what's happening is that libtool (usually, correctly) guesses these things based on the compiler paths and so forth, but sounds like the wonky compiler setup is too much for libtool ATM).