Re: per-deplib static/dynamic flags

2006-02-03 Thread Ralf Wildenhues
Hi Peter, * Peter O'Gorman wrote on Thu, Feb 02, 2006 at 03:04:19PM CET: > Ralf Wildenhues wrote: > | > | This is precisely and only because I wasn't sure whether we would find a > | linker which allows to set the preferred more but not force it to. > > The odcctools

Re: libtool-2.0 release [WAS per-deplib static/dynamic flags]

2006-02-02 Thread Bob Friesenhahn
On Thu, 2 Feb 2006, Gary V. Vaughan wrote: According to: http://tkd.kicks-ass.net/GnuLibtoolProject/RoadMap, the three remaining release blockers for 2.0 are: * libtool.m4 macro ordering/requirement audit. pending * LT_WITH_LTDL should build libltdl by default; currently nothing happens

Re: per-deplib static/dynamic flags

2006-02-02 Thread Peter O'Gorman
-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 |>>

libtool-2.0 release [WAS per-deplib static/dynamic flags]

2006-02-02 Thread Gary V. Vaughan
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 t

Re: per-deplib static/dynamic flags

2006-02-02 Thread Bob Friesenhahn
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 the

Re: per-deplib static/dynamic flags

2006-02-02 Thread Ralf Wildenhues
Hi Bob, Albert, * Bob Friesenhahn wrote on Wed, Feb 01, 2006 at 07:47:51AM CET: > On Tue, 31 Jan 2006, Albert Chin wrote: > > >On Mon, Jan 30, 2006 at 10:28:52PM +0100, Ralf Wildenhues wrote: > >>- Should the corresponding libtool flags be named `-Bstatic' resp. > >> `-Bdynamic'? Those were the

Re: per-deplib static/dynamic flags

2006-02-01 Thread Ralf Wildenhues
Hi Bob, * Bob Friesenhahn wrote on Thu, Feb 02, 2006 at 05:39:02AM CET: > On Wed, 1 Feb 2006, Albert Chin wrote: > >> > >>Good. GCC uses -B to mean something else. So -Bstatic is a > >>linker-only option. It is likely useful to use something new which > >>won't be confusing due the different me

Re: per-deplib static/dynamic flags

2006-02-01 Thread Bob Friesenhahn
On Wed, 1 Feb 2006, Albert Chin wrote: Good. GCC uses -B to mean something else. So -Bstatic is a linker-only option. It is likely useful to use something new which won't be confusing due the different meaning between GCC and ld. How about -static-only and -shared-only? Note though that Ra

Re: per-deplib static/dynamic flags

2006-02-01 Thread Albert Chin
On Wed, Feb 01, 2006 at 05:40:51PM -0600, Bob Friesenhahn wrote: > On Wed, 1 Feb 2006, Albert Chin wrote: > > > >Fine. -Bstatic on Linux means "Do not link against shared libraries." > >anyway. > > Good. GCC uses -B to mean something else. So -Bstatic is a > linker-only option. It is likely us

Re: per-deplib static/dynamic flags

2006-02-01 Thread Bob Friesenhahn
On Wed, 1 Feb 2006, Albert Chin wrote: Fine. -Bstatic on Linux means "Do not link against shared libraries." anyway. Good. GCC uses -B to mean something else. So -Bstatic is a linker-only option. It is likely useful to use something new which won't be confusing due the different meaning b

Re: per-deplib static/dynamic flags

2006-02-01 Thread Albert Chin
On Wed, Feb 01, 2006 at 12:47:51AM -0600, Bob Friesenhahn wrote: > On Tue, 31 Jan 2006, Albert Chin wrote: > > >On Mon, Jan 30, 2006 at 10:28:52PM +0100, Ralf Wildenhues wrote: > >>- Should the corresponding libtool flags be named `-Bstatic' resp. > >> `-Bdynamic'? Those were the most common nam

Re: per-deplib static/dynamic flags

2006-01-31 Thread Bob Friesenhahn
On Tue, 31 Jan 2006, Albert Chin wrote: On Mon, Jan 30, 2006 at 10:28:52PM +0100, Ralf Wildenhues wrote: - Should the corresponding libtool flags be named `-Bstatic' resp. `-Bdynamic'? Those were the most common names I could find, but IMHO they are not very self-explanatory for users not

Re: per-deplib static/dynamic flags

2006-01-31 Thread Albert Chin
On Mon, Jan 30, 2006 at 10:28:52PM +0100, Ralf Wildenhues wrote: > - Should the corresponding libtool flags be named `-Bstatic' resp. > `-Bdynamic'? Those were the most common names I could find, but IMHO > they are not very self-explanatory for users not used to them. -prefer-static, -prefer

per-deplib static/dynamic flags

2006-01-30 Thread Ralf Wildenhues
The 1.5.20 regression fix for `-static' for programs has made it clear that per-deplib static/shared flags are desirable for libtool. I will followup to this mail (to libtool-patches only for size, removing all Cc:s) with a patch to implement per-deplib flags for programs (for CVS HEAD) and add co