I certainly wouldn't mind a branch that bypasses libtool - it could be very
handy any time we run into something like this.
Paul: Thanks for the explanation!!!!!! I'm going to give it a whirl!
BTW - you can do dynamic linking on BG/Q - but it's tough to do and
basically frowned upon - so we're not doing it for MOOSE.
Derek
On Tue, Dec 10, 2013 at 1:03 PM, Kirk, Benjamin (JSC-EG311) <
benjamin.k...@nasa.gov> wrote:
> I'm working up a branch for you that bypasses libtool altogether - might
> need John to help update the moose rule that currently uses our libtool,
> though.
>
> Would that help for the short term?
>
> -Ben
>
>
> On Dec 10, 2013, at 12:34 PM, Paul T. Bauman <ptbau...@gmail.com> wrote:
>
> > On Tue, Dec 10, 2013 at 12:18 PM, Derek Gaston <fried...@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:
> >
> >
> http://www.gnu.org/software/libtool/manual/html_node/Configure-notes.html
> >
> > 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).
> >
> > Best,
> >
> > Paul
> >
> ------------------------------------------------------------------------------
> > Rapidly troubleshoot problems before they affect your business. Most IT
> > organizations don't have a clear picture of how application performance
> > affects their revenue. With AppDynamics, you get 100% visibility into
> your
> > Java,.NET, & PHP application. Start your 15-day FREE TRIAL of
> AppDynamics Pro!
> >
> http://pubads.g.doubleclick.net/gampad/clk?id=84349831&iu=/4140/ostg.clktrk_______________________________________________
> > Libmesh-devel mailing list
> > Libmesh-devel@lists.sourceforge.net
> > https://lists.sourceforge.net/lists/listinfo/libmesh-devel
>
>
------------------------------------------------------------------------------
Rapidly troubleshoot problems before they affect your business. Most IT
organizations don't have a clear picture of how application performance
affects their revenue. With AppDynamics, you get 100% visibility into your
Java,.NET, & PHP application. Start your 15-day FREE TRIAL of AppDynamics Pro!
http://pubads.g.doubleclick.net/gampad/clk?id=84349831&iu=/4140/ostg.clktrk
_______________________________________________
Libmesh-devel mailing list
Libmesh-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/libmesh-devel
