Re: Converting a project to libtool

2002-09-18 Thread Tor Lillqvist
Steve M. Robbins writes: > then you can just reverse-engineer > the computation that libtool does. Then choose values for Current, > Revision, and Age that give you the answer you want. Or choose fresh current, revision, age values that won't cause a clash with your current name now or in the

Re: Converting a project to libtool

2002-09-18 Thread Jeff Bailey
On Wed, 18 Sep 2002 19:32:00 -0400, Steve M. Robbins wrote: >> I'm converting a project to libtool, and need to maintain the >> existing SONAME and library names. I can't find a FAQ to see if >> there's a good way to do this. >I think the answer is "no, there's no good way to do this". >This i

Re: Converting a project to libtool

2002-09-18 Thread Steve M. Robbins
On Wed, Sep 18, 2002 at 04:16:24PM -0700, Jeff Bailey wrote: > I'm converting a project to libtool, and need to maintain the existing > SONAME and library names. I can't find a FAQ to see if there's a good > way to do this. I think the answer is "no, there's no good way to do this". This is m

Converting a project to libtool

2002-09-18 Thread Jeff Bailey
I'm converting a project to libtool, and need to maintain the existing SONAME and library names. I can't find a FAQ to see if there's a good way to do this. I essentially need my versuffix=".0.3" - Is there a -override-versuffix=".0.3" option? If not, would you accept a patch for it? I'm imagi

Intel icc and shared libs

2002-09-18 Thread Philip Willoughby
I'm having difficulty persuading libtool (version 1.4.2) to build shared libraries using icc. Is this possible (I'm guessing not with 1.4.2)? Assuming no, is it fixed in a newer version of libtool, or in current CVS, or do I need an extra patch? Please cc me in replies since I'm not on this list

Automake 1.6d available (beta for Automake 1.7)

2002-09-18 Thread Alexandre Duret-Lutz
Here is a snapshot of the current development version of Automake. This should become Automake 1.7 *soon*. How soon will depends on the feedback we get on this beta. Please get it, install it, test it, torture it. Please report any issue by mail to <[EMAIL PROTECTED]>, or (preferred) using the

Re: [Mingw-users] Re: libbfd, libtool & Win32

2002-09-18 Thread Danny Smith
--- David Olofson <[EMAIL PROTECTED]> wrote: > On Wednesday 18 September 2002 12:29, Danny Smith wrote: > [...] > > > > A gotcha with this is that some exported names in dll are aliases, > > > > the prime culprit being stdcall names. > > > > > > Uh oh. Why would that be an issue with ld, if it is

Re: libtool -release 2.1 does not add release to library name

2002-09-18 Thread Guido Draheim
Frank Kemmer wrote: > > Wouldn't it be nice, if libtool had versioned the '.a' files, too, if the > -release option > is given? Or may be another option -staticlib-release? > > This is just a question? Or is there another style of versioning intended > for the > static libs? > we had a talk

Re: libtool -release 2.1 does not add release to library name

2002-09-18 Thread Robert Boehne
Frank, What version of libtool are you using? -- Robert Boehne Software Engineer Ricardo Software Chicago Technical Center TEL: (630)789-0003 x. 238 FAX: (630)789-0127 email: rboehne AT ricardo-us DOT com ___ Libtool mailing list [EMA

Re: [Mingw-users] Re: libbfd, libtool & Win32

2002-09-18 Thread David Olofson
On Wednesday 18 September 2002 12:29, Danny Smith wrote: [...] > > > A gotcha with this is that some exported names in dll are aliases, > > > the prime culprit being stdcall names. > > > > Uh oh. Why would that be an issue with ld, if it isn't with > > impgen.c...? > > It is an issue with impgen.

Re: [Mingw-users] Re: libbfd, libtool & Win32

2002-09-18 Thread Danny Smith
--- David Olofson <[EMAIL PROTECTED]> wrote: > On Wednesday 18 September 2002 11:46, Danny Smith wrote: > > --- David Olofson <[EMAIL PROTECTED]> wrote: > On Tuesday 17 > > > > I'm a bit late catching up with this thread. No one has mentioned the > > code in ld/pe-dll.c, function pe_implied_imp

libtool -release 2.1 does not add release to library name

2002-09-18 Thread Frank Kemmer
The scenarion is as follows: We build a custom library with libtool. We use libtool to build the shared lib and the static lib. For building the library I use the following options: libtool -release 2.1 -version-info 0.0.0 ... The shared library name results in libmyname-2.1.so.0.0.0 which is

Re: [Mingw-users] Re: libbfd, libtool & Win32

2002-09-18 Thread David Olofson
On Wednesday 18 September 2002 11:46, Danny Smith wrote: > --- David Olofson <[EMAIL PROTECTED]> wrote: > On Tuesday 17 > > September 2002 20:33, Guido Draheim wrote: > > [...] > > > > > On another e-mail, you said to have some idea of the `objdump -p` > > > output of an export table. If someone

Re: [Mingw-users] Re: libbfd, libtool & Win32

2002-09-18 Thread Danny Smith
--- David Olofson <[EMAIL PROTECTED]> wrote: > On Tuesday 17 September 2002 20:33, Guido Draheim wrote: > [...] > > On another e-mail, you said to have some idea of the `objdump -p` > > output of an export table. If someone could work that out with a > > portable shell program (sh/sed/etc), then

Re: [Mingw-users] Re: libbfd, libtool & Win32

2002-09-18 Thread David Olofson
On Wednesday 18 September 2002 11:08, David Olofson wrote: [...] > Indeed, it seems that the export section is *not* really a symbol > table, which is why some DLLs can have symbols ('-syms'), while most > DLLs don't. (In fact, I think clean DLLs *shouldn't* have the kind of > symbol table that 'o

Re: [Mingw-users] Re: libbfd, libtool & Win32

2002-09-18 Thread David Olofson
On Tuesday 17 September 2002 20:33, Guido Draheim wrote: [...] > On another e-mail, you said to have some idea of the `objdump -p` > output of an export table. If someone could work that out with a > portable shell program (sh/sed/etc), then we can let that impgen.sh be > created in the $builddir

libtool/MinGW DLLs patch - tidied up section 2

2002-09-18 Thread Max Bowsher
I am tidying and explaining my patch bit by bit. Here is the second chunk. A libtool expert needs to check Hunk 2. See my comments below Once section 1 and 2 have been pronounced OK, they can be commited, as they are just groundwork for the main chunk of the patch, and can stand alone. Max. --