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/
