From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 13040 invoked by alias); 1 Jan 2002 17:26:32 -0000 Mailing-List: contact cygwin-help@cygwin.com; run by ezmlm Precedence: bulk List-Subscribe: List-Archive: List-Post: List-Help: , Sender: cygwin-owner@cygwin.com Received: (qmail 13010 invoked from network); 1 Jan 2002 17:26:31 -0000 Received: from unknown (HELO lacrosse.corp.redhat.com) (12.107.208.154) by sources.redhat.com with SMTP; 1 Jan 2002 17:26:31 -0000 Received: from mail.redhat.com (dhcpd244.meridian.redhat.com [172.16.47.244]) by lacrosse.corp.redhat.com (8.11.6/8.9.3) with ESMTP id g01GxOa19052 for ; Tue, 1 Jan 2002 11:59:24 -0500 Received: (from cgf@localhost) by mail.redhat.com (8.11.6/8.8.7) id g01GxLL06893 for cygwin@cygwin.com; Tue, 1 Jan 2002 11:59:21 -0500 Date: Tue, 01 Jan 2002 09:26:00 -0000 From: Christopher Faylor To: cygwin@cygwin.com Subject: Re: duplicate regexec/regcomp functions detected Message-ID: <20020101165921.GA6767@redhat.com> Reply-To: cygwin@cygwin.com Mail-Followup-To: cygwin@cygwin.com References: <01df01c19259$1cbb8300$0200a8c0@lifelesswks> <001101c192d0$11e99c60$865c07d5@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 X-SW-Source: 2002-01/txt/msg00009.txt.bz2 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/