Mailing-List: contact cygwin-help AT sourceware DOT cygnus DOT com; run by ezmlm
List-Subscribe: <mailto:cygwin-subscribe AT sources DOT redhat DOT com>
List-Archive: <http://sources.redhat.com/ml/cygwin/>
List-Post: <mailto:cygwin AT sources DOT redhat DOT com>
List-Help: <mailto:cygwin-help AT sources DOT redhat DOT com>, <http://sources.redhat.com/ml/#faqs>
Sender: cygwin-owner AT sources DOT redhat DOT com
Delivered-To: mailing list cygwin AT sources DOT redhat DOT com
Message-Id: <4.3.1.2.20000908100651.01f2d400@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: Fri, 08 Sep 2000 10:13:00 -0400
To: <kris DOT thielemans AT ic DOT ac DOT uk>
From: "Larry Hall (RFK Partners, Inc)" <lhall AT rfk DOT com>
Subject: RE: problem with dynamic_cast
Cc: "Cygwin (E-mail)" <cygwin AT sourceware DOT cygnus DOT com>
In-Reply-To: <003101c0199d$58898020$460a10ac@petnt1.rpms.ac.uk>
References: <4 DOT 3 DOT 1 DOT 2 DOT 20000908095010 DOT 00b4ff18 AT pop DOT ma DOT ultranet DOT com>
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"

At 10:01 AM 9/8/2000, Kris Thielemans wrote:

> > Quite true.  -lm and -lc are not necessary with Cygwin.  The support for
> > them are in the Cygwin DLL/lib which is linked in automatically.  Linking
> > with it twice (or more) guarantees a crash.  The simple answer is, don't
> > us -lm or -lc with Cygwin.
> >
>
>Dear Larry,
>
>I don't think that's a viable solution. One of the important benefits  of
>cygwin is to be able to part programs from Unix to Windows. Now you might
>not be using numeric C++ packages, but lots of other people do. We do not
>want to go and change all Makefiles, do we ?
>
>Also, providing the patch would prevent other people having to waste 4 days
>with tracking the bug. Ok, somebody will have to waste time to install the
>patch of course, but I think in the end it's worth it, especially as I won't
>be the one installing the patch :-).
>
>Kris


Hi Kris,

Right now, there isn't a "patch".  That doesn't mean there won't be.  I'm
simply pointing out a work-around to your current problem in the meantime.
Your original example was so simple that this seemed like a viable one.  
Dealing with it in makefiles that already exist may be more of an issue.
Another option may be to simply create an empty libm.a library in place of the symlink (although I seem to recall some ancient discussion on this topic 
that swayed people away for this option.)  YMMV.

Of course, if you're interested in investigating the issue and providing
an appropriate patch, I'm sure it will be thoughtfully considered!:-)


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


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