On Thu, 2 Feb 2006, Ralf Wildenhues wrote:
I would love to be able to supply LDFLAGS options to configure and
have them work appropriately within the configure script, and then
work similarly for libtool.
Note that `-Wl,-Bstatic' will *not* be useful in LDFLAGS, but LIBS at
best, because of
Hallo Ralf,
Ralf Wildenhues wrote:
This fixes the failure uncovered by the new tests posted previously.
OK to apply?
Looks good to me! Please go right ahead :-)
* libltdl/config/ltmain.m4sh (func_mode_link): Fix logic for
adding run paths to also add paths for installed
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Ralf Wildenhues wrote:
|
| Hmm. If we were to invent new flags, I currently like
| -force-static, -prefer-shared
| best.
|
|
|Note though that Ralf has -Bstatic defined as:
|If @var{output-file} is a program, prefer linking statically
|
Hallo Ralf, Bob, Peter, Eric,
Is this patch really necessary for 2.0? I think that introducing so
much code churn in to libtool at this stage is going to bring yet more
release delays. Surely the feature is useful and desireable, but I
really *really* want to avoid more delays for 2.0.
Now is
Hi Bob,
* Bob Friesenhahn wrote on Thu, Feb 02, 2006 at 07:38:13PM CET:
On Thu, 2 Feb 2006, Bob Friesenhahn wrote:
I have also noticed some disturbing leakage of default compiler (GCC)
path information into the build which causes -m64 to not work properly (at
least under Solaris, but
Hi Gary,
Gary V. Vaughan writes:
Is this patch really necessary for 2.0?
No.
I think that introducing so
much code churn in to libtool at this stage is going to bring yet more
release delays. Surely the feature is useful and desireable, but I
really *really* want to avoid more delays for
