X-Recipient:	archive-cygwin AT delorie DOT com
X-SWARE-Spam-Status:	No, hits=-2.3 required=5.0 tests=AWL,BAYES_00,SPF_PASS
X-Spam-Check-By:	sourceware.org
Message-ID:	<49C07906.2060504@gmail.com>
Date:	Wed, 18 Mar 2009 04:31:02 +0000
From:	Dave Korn <dave DOT korn DOT cygwin AT googlemail DOT com>
User-Agent:	Thunderbird 2.0.0.17 (Windows/20080914)
MIME-Version:	1.0
To:	cygwin AT cygwin DOT com
Subject:	Re: gcc4: cc
References:	<49C0467A DOT 1080404 AT users DOT sourceforge DOT net>
In-Reply-To:	<49C0467A.1080404@users.sourceforge.net>
Mailing-List:	contact cygwin-help AT cygwin DOT com; run by ezmlm
List-Id:	<cygwin.cygwin.com>
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

Yaakov (Cygwin/X) wrote:

> gcc4 does not provide cc-4, nor does the alternatives script provide cc.
>  It probably goes without saying that this breaks some (obviously
> non-autotoolized) packages that assume cc's presence.

  Ah, thanks for pointing this out.  (The packages are of course broken as far
as portability is concerned, as upstream GCC does not anywhere provide a 'cc'
executable; it's presence in the gcc-3 package is caused by the build script
creating a symlink as a convenience, so it's wrong in general to assume that
there "must be" an executable called 'cc' in the PATH.)  I'll add it back into
the next release.

    cheers,
      DaveK


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