Mailing-List: contact cygwin-help AT cygwin DOT com; run by ezmlm
List-Subscribe: <mailto:cygwin-subscribe AT cygwin DOT com>
List-Archive: <http://sources.redhat.com/ml/cygwin/>
List-Post: <mailto:cygwin AT cygwin DOT com>
List-Help: <mailto:cygwin-help AT cygwin DOT com>, <http://sources.redhat.com/ml/#faqs>
Sender: cygwin-owner AT cygwin DOT com
Delivered-To: mailing list cygwin AT cygwin DOT com
Date: Tue, 1 Jan 2002 11:59:21 -0500
From: Christopher Faylor <cgf AT redhat DOT com>
To: cygwin AT cygwin DOT com
Subject: Re: duplicate regexec/regcomp functions detected
Message-ID: <20020101165921.GA6767@redhat.com>
Reply-To: cygwin AT cygwin DOT com
Mail-Followup-To: cygwin AT cygwin DOT com
References: <01df01c19259$1cbb8300$0200a8c0 AT lifelesswks> <001101c192d0$11e99c60$865c07d5 AT BRAMSCHE>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <001101c192d0$11e99c60$865c07d5@BRAMSCHE>
User-Agent: Mutt/1.3.23.1i

On Tue, Jan 01, 2002 at 03:24:49PM +0100, Ralf Habacker wrote:
>After thinking about this problem a while I had an idea how to solve
>such problems instead of using simple links from libcygwin.a to
>libpthread.a and other.  The idea was to use the cygwin1.dll as used
>currently, but to build only several import libs (!) for special libs
>like libpthread and may me libm and libc.

Yes.  I had misgivings about this idea when you first mentioned it but
on reflection, I really think that this is a very good idea and, so,
have implemented it.  The change is in CVS, as I've mentioned.  As I
mentioned, I used roughly your technique to accomplish this goal.

>The task for doing so (for libpthread) is to look which functions of
>the pthread library are exported (decribed in pthread.h and relating
>headers, but I think it is only the one).  This is done by scanning
>pthread.o with nm for every exported symbol.  (The consequence for this
>is, that only this symbols are has to be exported)
>
>Then search cygdll.a after those symbols and extract only the relevant
>d000xxx.o from cygdll.a to a newly created import library named
>libpthread.a or other revelant name.

And, here is where I don't understand your confusion.  You don't need to
search cygdll.a.  You already have a text file available to you which
contains all of the exports from the cygwin DLL -- cygwin.def.

I was suggesting that you could use this.

I guess if this still isn't clear we'll just have to move on since it's
already implemented.

cgf

--
Unsubscribe info:      http://cygwin.com/ml/#unsubscribe-simple
Bug reporting:         http://cygwin.com/bugs.html
Documentation:         http://cygwin.com/docs.html
FAQ:                   http://cygwin.com/faq/