Mailing-List:	contact cygwin-help AT cygwin DOT com; run by ezmlm
List-Subscribe:	<mailto:cygwin-subscribe AT cygwin DOT com>
List-Archive:	<http://sources.redhat.com/ml/cygwin/>
List-Post:	<mailto:cygwin AT cygwin DOT com>
List-Help:	<mailto:cygwin-help AT cygwin DOT com>, <http://sources.redhat.com/ml/#faqs>
Sender:	cygwin-owner AT cygwin DOT com
Delivered-To:	mailing list cygwin AT cygwin DOT com
Message-ID:	<04b501c18f48$3e2da2c0$0200a8c0@lifelesswks>
From:	"Robert Collins" <robert DOT collins AT itdomain DOT com DOT au>
To:	"Jon Leichter" <jon AT symas DOT com>
Cc:	<cygwin AT cygwin DOT com>
References:	<DLEBJKNCNLJEDKMKICHGAENJCAAA DOT jon AT symas DOT com>
Subject:	Re: Potential problems with Cygwin GCC and -mno-cygwin switch
Date:	Fri, 28 Dec 2001 13:34:57 +1100
MIME-Version:	1.0
X-Priority:	3
X-MSMail-Priority:	Normal
X-Mailer:	Microsoft Outlook Express 6.00.2600.0000
X-MimeOLE:	Produced By Microsoft MimeOLE V6.00.2600.0000
X-OriginalArrivalTime:	28 Dec 2001 02:34:48.0137 (UTC) FILETIME=[37E6BB90:01C18F48]

----- Original Message -----
From: "Jon Leichter" <jon AT symas DOT com>
> I was not talking about pre-packaged Cygwin binaries. And I still
claim that
> even after you install Cygwin packages, they will operate if you
relocate
> the libraries in /usr/lib. This is because the Cygwin binaries depend
on
> DLLs accessible via the PATH, which are NOT relocated from /usr/bin.

However , once gcc's specs are changedm linking with the libraries they
provide will fail - which is what I was talking about. (Until every
package gets repackaged, at a significant time cost to the package
maintainers).

And as this would be (at best) an interim fix until gcc is corrected, I
for one do not support implementing this - the time cost would get gcc
fixed many times over.

Rob


--
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/

- Raw text -