Mailing-List: contact cygwin-help AT sourceware DOT cygnus DOT com; run by ezmlm
List-Subscribe: <mailto:cygwin-subscribe AT sourceware DOT cygnus DOT com>
List-Archive: <http://sourceware.cygnus.com/ml/cygwin/>
List-Post: <mailto:cygwin AT sourceware DOT cygnus DOT com>
List-Help: <mailto:cygwin-help AT sourceware DOT cygnus DOT com>, <http://sourceware.cygnus.com/ml/#faqs>
Sender: cygwin-owner AT sourceware DOT cygnus DOT com
Delivered-To: mailing list cygwin AT sourceware DOT cygnus DOT com
Message-Id: <4.3.1.2.20000531185749.03b507f0@pop.ma.ultranet.com>
X-Sender: lhall AT pop DOT ma DOT ultranet DOT com
X-Mailer: QUALCOMM Windows Eudora Version 4.3.1
Date: Wed, 31 May 2000 19:08:41 -0500
To: "Ross Smith" <ross DOT s AT ihug DOT co DOT nz>, "Parker, Ron" <rdparker AT butlermfg DOT com>,
        "cygwin AT sourceware DOT cygnus DOT com" <cygwin AT hotpop DOT com>
From: "Larry Hall (RFK Partners, Inc)" <lhall AT rfk DOT com>
Subject: Re: Major bug -- Exception handling broken
In-Reply-To: <008501bfcb53$27bac960$a8a11dcb@ihug.co.nz>
References: <E12xGdc-0002uy-00 AT mx1 DOT ihug DOT co DOT nz>
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"



At 05:54 PM 5/31/00, Ross Smith wrote:
>From: "Parker, Ron" <rdparker AT butlermfg DOT com>
> > 
> > My hunch about the specs file was wrong.  There are no entries related to
> > g++.  However I did track this down to a problem with g++ using libm.a.
> > 
> > [snip]
> > 
> > gcc -v foo.cpp -o foo -lstd++ (OKAY)
> > gcc -v foo.cpp -o foo -lstd++ -lm(BAD)
> > gcc -v foo.cpp -o foo -lm (BAD)
> > 
> > So the problem seems to be with libm.a.  
>
>Cygwin's libm.a is a symlink to libcygwin.a. I'll try replacing it
>with a dummy stub library ... <tries it> ... nope, that made ld crash.



Hm.  All this rings a bell with me.  Something very old and very
foggy....  Seems to me I recall that multiple references to libraries in 
the link stream always caused Cygwin to crash.  I believe the context of 
this the last time the issue came up was with Windows libraries but perhaps 
the issue is more generic.  Also, I recall discussions which stated that
there isn't really a libm.a for Cygwin.  Its all in Cygwin.  That would 
imply that libcygwin.a == libm.a, a notion that the symlink tends to support.
Given all this, its my impression that libm.a isn't needed, at least in the
default case.  Obviously, eliminating libm.a as a default library to link
against is not the complete solution since some packages are going to link
against it explicitly in their makefile and therefore still see problem 
(unless the makefile is edited!;-))  Probably we'll need to wait for Mumit to
clarify this whole situation but eliminating the -lm seems a good work-around 
for now!;-)



Larry Hall                              lhall AT rfk DOT com
RFK Partners, Inc.                      http://www.rfk.com
118 Washington Street                   (508) 893-9779 - RFK Office
Holliston, MA 01746                     (508) 893-9889 - FAX
                                        (508) 560-1285 - cell phone



--
Want to unsubscribe from this list?
Send a message to cygwin-unsubscribe AT sourceware DOT cygnus DOT com