Mailing-List:	contact cygwin-help AT cygwin DOT com; run by ezmlm
List-Subscribe:	<mailto:cygwin-subscribe AT cygwin DOT com>
List-Archive:	<http://sourceware.org/ml/cygwin/>
List-Post:	<mailto:cygwin AT cygwin DOT com>
List-Help:	<mailto:cygwin-help AT cygwin DOT com>, <http://sourceware.org/ml/#faqs>
Sender:	cygwin-owner AT cygwin DOT com
Mail-Followup-To:	cygwin AT cygwin DOT com
Delivered-To:	mailing list cygwin AT cygwin DOT com
From:	"Dave Korn" <dave DOT korn AT artimi DOT com>
To:	<cygwin AT cygwin DOT com>
Subject:	RE: setup: how to handle circular dependencies?
Date:	Fri, 16 Sep 2005 14:22:46 +0100
MIME-Version:	1.0
In-Reply-To:	<432AC517.7030606@familiehaase.de>
Message-ID:	<SERRANOaPeda2UexM500000003b@SERRANO.CAM.ARTIMI.COM>

----Original Message----
>From: Gerrit P. Haase
>Sent: 16 September 2005 14:14

> Hi Setup maintainers,
> 
> I need some circular dependencies, i.e. gcc-core requires gcc-core-mingw
> because -mno-cygwin will not work without the mingw version of the gcc
> runtime.  However, the gcc-core-mingw package only includes the runtime
> which needs gcc-core to be useful.

> Maybe I should include the mingw gcc runtimes in the main gcc packages?


  I can't see the use in having them separate if gcc-core-mingw is really no
use whatsoever on its own.  Perhaps someone else can think of a reason?


    cheers,
      DaveK
-- 
Can't think of a witty .sigline today....


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

- Raw text -