Mailing-List: contact cygwin-help AT cygwin DOT com; run by ezmlm 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 X-Authentication-Warning: eos.vss.fsi.com: ford owned process doing -bs Date: Wed, 28 Jan 2004 14:21:43 -0600 (CST) From: Brian Ford X-X-Sender: ford AT eos To: cygwin AT cygwin DOT com Subject: Re: G++ for CygWin In-Reply-To: <1821032508929.20040128141439@familiehaase.de> Message-ID: References: <1821032508929 DOT 20040128141439 AT familiehaase DOT de> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII X-IsSubscribed: yes Reply-To: cygwin AT cygwin DOT com I read these two threads out of order. Sorry for the previous rant in "Re: Lost g++ after update". On Wed, 28 Jan 2004, Gerrit P. Haase wrote: > E.g.: > If you want to install g++ you'll need the package `gcc-g++`, this pulls > automatically the backend package which is currently named `gcc' (may be > changed to `gcc-core') and the according MinGW packages. Similar with > `gcc-java' and the others. > I strongly vote *for* the name change if you can figure out how to do it without messing too much up. > Eventually I will add the installation of `gcc-g++' as an requirement to > the basic GCC installation since in previous releases it was one larger > package which includes gcj, g++, g77 and gcc and the actual compilers > and headers and the users are still used to get g++ automatically with > this one huge package. Since I included also the frontends for Ada, > ObjC and Pascal, the package would be really large and we already had > lots of complaints about the size of the old gcc package (mainly since > java was included), so it was separated. > Yeah! I'm glad you are still considering a fix. -- Brian Ford Senior Realtime Software Engineer VITAL - Visual Simulation Systems FlightSafety International Phone: 314-551-8460 Fax: 314-551-8444 -- 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/