X-Recipient: archive-cygwin AT delorie DOT com X-SWARE-Spam-Status: No, hits=-2.4 required=5.0 tests=AWL,BAYES_00,SPF_PASS X-Spam-Check-By: sourceware.org Message-ID: <49C07E09.5070909@users.sourceforge.net> Date: Tue, 17 Mar 2009 23:52:25 -0500 From: "Yaakov (Cygwin/X)" User-Agent: Thunderbird 2.0.0.19 (Windows/20081209) MIME-Version: 1.0 To: cygwin AT cygwin DOT com Subject: Re: gcc4: cc References: <49C0467A DOT 1080404 AT users DOT sourceforge DOT net> <49C07906 DOT 2060504 AT gmail DOT com> In-Reply-To: <49C07906.2060504@gmail.com> Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Mailing-List: contact cygwin-help AT cygwin DOT com; run by ezmlm List-Id: List-Subscribe: List-Archive: List-Post: List-Help: , Sender: cygwin-owner AT cygwin DOT com Mail-Followup-To: cygwin AT cygwin DOT com Delivered-To: mailing list cygwin AT cygwin DOT com -----BEGIN PGP SIGNED MESSAGE----- Hash: SHA256 Dave Korn wrote: > 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. Actually, SUSv2 requires a cc and c89; SUSv3 mentions only a c99. Yaakov -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.9 (Cygwin) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org iEYEAREIAAYFAknAfgkACgkQpiWmPGlmQSO12wCg9/imuhKp04k+1sQnwFmphH5P tVwAoJyvYKElmJbOQeNzkCzKmpkZ1CQG =Opy3 -----END PGP SIGNATURE----- -- 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/