On Aug 7, 2013, at 1:17 PM, "Gaston, Derek R" wrote:
> On Wed, Aug 7, 2013 at 11:45 AM, Kirk, Benjamin (JSC-EG311)
> wrote:
> ./configure LIBTOOL="libtool -all-static"
>
> That won't work - the -all-static _must_ go after the --mode=link option to
> libtool... and is only valid for that mode…
On Wed, Aug 7, 2013 at 11:45 AM, Kirk, Benjamin (JSC-EG311) <
benjamin.k...@nasa.gov> wrote:
> ./configure LIBTOOL="libtool -all-static"
>
That won't work - the -all-static _must_ go after the --mode=link option to
libtool... and is only valid for that mode...
Derek
-
Guessing from here:
https://www.gnu.org/software/automake/manual/html_node/Libtool-Flags.html
http://stackoverflow.com/questions/8135119/how-libtool-custom-script-is-generated-by-configure
I'm thinking maybe if you do
./configure LIBTOOL="libtool -all-static"
make
that *might* do the trick?
-B
On Aug 7, 2013, at 12:34 PM, "Gaston, Derek R" wrote:
> think it would be handy if we had a way to set this at configure time - but
> I don't know what that is…
I'd think we'd approach it the same way we do compiler flags. configure.ac can
append libmesh_LDFLAGS with system-specific stuff (i
I ran ./bootstrap and used the autotools built there.
So - I have a "fix": you have to pass -all-static to libtool... but you
have to do it _after_ the --mode option for libtool. This is tricky to do.
LDFLAGS is in the right spot - but if you set LDFLAGS=-all-static
configure will fail saying th
What version of libtool is getting run? Just the other day I
encountered a situation with a libMesh app where the system default
libtool (version 2.4 IIRC) was utterly failing while the only slightly
newer version in our contrib (2.4.2) did fine.
---
Roy
On Wed, 7 Aug 2013, Gaston, Derek R wrot
Ben et. al.
I'm having some crazy issue with getting libMesh executables to link on a
BlueGene/Q (Mira at Argonne). The issue is that libtool is choosing to try
to link dynamic libraries even though I explicitly set --enable-static
--disable-shared. It's weird because libtool is picking up .
