Re: libtool 1.5 tag woes (static/shared)

2003-11-19 Thread Sander Niemeijer
Bringing the discussion back to the list. Begin forwarded message: Hi Paolo, I think I start to understand it now. When I was writing my e-mail, the libtool mail archive site was also not reachable, but today it was working again, so I have been able to do some catching up. As you already stat

Re: libtool 1.5 tag woes (static/shared)

2003-11-17 Thread Sander Niemeijer
Hi Paulo, It seems this thread starts to go into a direction that might change the recently added functionality of the -static and -shared flags. In a previous posting you opted for reverting the -static/-shared functionality and in the posting quoted below you are opting to make the disable-s

Re: libtool 1.5 tag woes

2003-11-17 Thread Paolo Bonzini
Why make enable_shared and enable_static specific to a tag? Wouldn't it be odd that you create shared libs for "C" programs and static for "C++"? And, the --enable-shared and --enable-static options would have to multiply (--enable-c-shared, --enable-cxx-shared, etc). I'm using tags for something d

Re: libtool 1.5 tag woes

2003-11-14 Thread Bob Friesenhahn
On Fri, 14 Nov 2003, Albert Chin wrote: > On Fri, Nov 14, 2003 at 10:44:52AM +0100, Paolo Bonzini wrote: > > > Does this help? > > > AC_LIBTOOL_TAGS([]) > > > > That's only in CVS (actually, I checked and it is not in 1.5, so it must be > > in CVS). > > I can send you a patch against 1.5 if you wa

Re: libtool 1.5 tag woes

2003-11-14 Thread Albert Chin
On Fri, Nov 14, 2003 at 10:44:52AM +0100, Paolo Bonzini wrote: > > Does this help? > > AC_LIBTOOL_TAGS([]) > > That's only in CVS (actually, I checked and it is not in 1.5, so it must be > in CVS). I can send you a patch against 1.5 if you want. > I don't see it that bad that C is not a proper t

Re: libtool 1.5 tag woes

2003-11-14 Thread Paolo Bonzini
> Does this help? > AC_LIBTOOL_TAGS([]) That's only in CVS (actually, I checked and it is not in 1.5, so it must be in CVS). I don't see it that bad that C is not a proper tag, actually. It would also be good if enable_shared and enable_static became proper tag variables instead of globals. BTW

Re: libtool 1.5 tag woes

2003-11-12 Thread Scott James Remnant
On Wed, 2003-11-12 at 20:49, Albert Chin wrote: > On Wed, Nov 12, 2003 at 06:59:44PM +0100, Paolo Bonzini wrote: > > I have just upgraded to libtool 1.5 (Debian's package which is taken > > out of CVS) and here are my first experiences. > > HEAD or branch-1-5? I think development is happening on

Re: libtool 1.5 tag woes

2003-11-12 Thread Albert Chin
On Wed, Nov 12, 2003 at 06:59:44PM +0100, Paolo Bonzini wrote: > I have just upgraded to libtool 1.5 (Debian's package which is taken > out of CVS) and here are my first experiences. HEAD or branch-1-5? I think development is happening on HEAD towards a 1.6 release. > However, I have had serious

libtool 1.5 tag woes

2003-11-12 Thread Paolo Bonzini
I have just upgraded to libtool 1.5 (Debian's package which is taken out of CVS) and here are my first experiences. I'd like to make a custom tag so that, for a particular libtool library, PIC code is also compiled with -fomit-frame-pointer (I really need the register that is lost by the GOT code)