Mailing-List: contact cygwin-help@sourceware.cygnus.com; run by ezmlm
Sender: cygwin-owner@sources.redhat.com
Message-ID: <01d501c0190e$fc28e930$f7c723cb@lifelesswks>
From: "Robert Collins" <robert.collins@itdomain.com.au>
To: "Gary V. Vaughan" <gvv@techie.com>, "Earnie Boyd" <earnie_boyd@yahoo.com>
Cc: <cygwin@sources.redhat.com>
References: <20000907133430.25505.qmail@web119.yahoomail.com> <20000907185550.O7695@demon.co.uk>
Subject: Re: libtool
Date: Fri, 8 Sep 2000 08:02:46 +1100
MIME-Version: 1.0
Content-Type: text/plain;
	charset="iso-8859-1"
Content-Transfer-Encoding: 7bit

I played around last night... pity I don't know dlls that well :-]

1) the ltdll.c header seems unneeded with current gcc
gcc -shared -g -O2 -Wall,--enable-auto-image-base,--out-imp-lib=.libs/libnam
e.dll.a -o .libs/libname.dll -export-dynamic a.lo b.lo c.lo

built a dll quite happily from standard sources except there were no
exports...
I presume that's what the sed and DLLTOOL scripts in the current libtool are
all about? generating a .def file to explicitly list the exports?

2) the .def files format was broken
-> I haven't looked at this yet

3) the .def file had many un-related symbols pulled via dlltool and sed.
(i.e. printf as an export from glib...)
I'm kicking around using NM and searching for T entries in the .lo files
rather than libtool --export-all

comments anyone?

Rob


----- Original Message -----
From: "Gary V. Vaughan" <gvv@techie.com>
To: "Earnie Boyd" <earnie_boyd@yahoo.com>
Cc: "Robert Collins" <robert.collins@itdomain.com.au>;
<cygwin@sources.redhat.com>
Sent: Friday, September 08, 2000 4:55 AM
Subject: Re: libtool


> On Thu, Sep 07, 2000 at 06:34:30AM -0700, Earnie Boyd wrote:
> > --- "Gary V. Vaughan" <gvv@techie.com> wrote:
> > >
> > > What has changed in the build procedure for cygwin dlls between b20.1
> > > (where I had tested all the changes I made to libtool for dll
> > > generation) and cygwin-1.1.2 (where it no longer works) =(O|
> > >
> >
> > One of the things that changed that might affect this is the handling of
paths
> > with a \ in the string.  So, that \usr is not the same as /usr.  Could
this be
> > the problem?  I don't know I have tried libtool recently.
>
> I don't think so.  Internally, libtool always uses '/' delimitters.
> It *should* propogate '\' correctly on cygwin if such a path is passed
> in by automake or somesuch -- however, if not, it has always been
> broken, and isn't a new problem.
>
> I'll upgrade to cygwin 1.1.4 and post some traces later tonight in the
> hope that someone can make more sense of them than I can.
>
> Cheers,
> Gary.
> --
>   ___              _   ___   __              _         mailto:
gvv@techie.com
>  / __|__ _ _ ___ _| | / / | / /_ _ _  _ __ _| |_  __ _ ___
gary@gnu.org
> | (_ / _` | '_|// / |/ /| |/ / _` | || / _` | ' \/ _` | _ \
>  \___\__,_|_|\_, /|___(_)___/\__,_|\_,_\__, |_||_\__,_|//_/
> home page:  /___/                      /___/                  gpg public
key:
> http://www.oranda.demon.co.uk
http://www.oranda.demon.co.uk/key.asc
>


--
Want to unsubscribe from this list?
Send a message to cygwin-unsubscribe@sourceware.cygnus.com