Mailing-List: contact cygwin-help AT cygwin DOT com; run by ezmlm List-Subscribe: List-Archive: List-Post: List-Help: , Sender: cygwin-owner AT cygwin DOT com Mail-Followup-To: cygwin AT cygwin DOT com Delivered-To: mailing list cygwin AT cygwin DOT com Message-ID: <430603EA.3164298D@dessent.net> Date: Fri, 19 Aug 2005 09:08:10 -0700 From: Brian Dessent MIME-Version: 1.0 To: cygwin AT cygwin DOT com Subject: Re: Trying to build crm114 (20050721) under CygWin 1.5.18-1 References: <4305F226 DOT CD82A7FD AT dessent DOT net> <4305F8FD DOT 3080104 AT familiehaase DOT de> <4305FF5B DOT 2421ED2A AT dessent DOT net> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit X-IsSubscribed: yes Reply-To: cygwin AT cygwin DOT com Brian Dessent wrote: > As far as I know this is only done for link efficiency, as > these sub-libs are never distributed and probably don't work as > standalone libraries. ... Apparently I don't know that much since I just checked and they are distributed. But all the imports in libm should be in libcygwin too: $ nm /usr/lib/libcygwin.a |grep fabs 00000000 T __fabs 00000000 I __imp___fabs 00000000 T __fabsf 00000000 I __imp___fabsf 00000000 I __imp__fabs 00000000 T _fabs 00000000 I __imp__fabsf 00000000 T _fabsf $ nm /usr/lib/libm.a |grep fabs 00000000 I __imp__fabs 00000000 T _fabs 00000000 I __imp__fabsf 00000000 T _fabsf So the libm, libpthread, etc are probably just there to satisfy link command lines that specify them, but all the functionality is in libcygwin.a / cygwin1.dll anyway. Brian -- Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple Problem reports: http://cygwin.com/problems.html Documentation: http://cygwin.com/docs.html FAQ: http://cygwin.com/faq/