Mailing-List: contact cygwin-developers-help AT sourceware DOT cygnus DOT com; run by ezmlm
List-Unsubscribe: <mailto:cygwin-developers-unsubscribe-archive-cygwin-developers=delorie DOT com AT sourceware DOT cygnus DOT com>
List-Archive: <http://sourceware.cygnus.com/ml/cygwin-developers/>
List-Post: <mailto:cygwin-developers AT sourceware DOT cygnus DOT com>
List-Help: <mailto:cygwin-developers-help AT sourceware DOT cygnus DOT com>,
	<http://sourceware.cygnus.com/ml/#faqs>
Sender: cygwin-developers-owner AT sourceware DOT cygnus DOT com
Delivered-To: mailing list cygwin-developers AT sourceware DOT cygnus DOT com
Message-Id: <199908231434.JAA17769@mercury.xraylith.wisc.edu>
To: Chris Faylor <cgf AT cygnus DOT com>
cc: cygwin developers <cygwin-developers AT sourceware DOT cygnus DOT com>
Subject: Re: libcygwin.a as a symbolic link to lib{c,m}.a -- need insight 
In-Reply-To: Your message of "Mon, 23 Aug 1999 10:22:23 EDT."
             <19990823102223 DOT C13563 AT cygnus DOT com> 
Date: Mon, 23 Aug 1999 09:34:06 -0500
From: Mumit Khan <khan AT xraylith DOT wisc DOT EDU>

Chris Faylor <cgf AT cygnus DOT com> writes:
> 
> I've never heard of a problem where linking libcygwin.a (or any library file)
> multiple times caused problems.  If this did cause problems I'd think that Mu
> mit
> would have raised this issue.
> 

I don't any reference to the problem in my mailbox or in the cygwin 
archive, but just to be on the safe side, I want to build a variety of 
applications to see if there's going to be a problem. If something
like Octave works, then chances are the rest will too.

One good test of course is to rebuild Cygwin dev tree twice (installing
each time so that the 2nd time everything is built with the new libs).

Regards,
Mumit