Mailing-List: contact cygwin-help@cygwin.com; run by ezmlm List-Subscribe: List-Archive: List-Post: List-Help: , Sender: cygwin-owner@cygwin.com Mail-Followup-To: cygwin@cygwin.com Delivered-To: mailing list cygwin@cygwin.com X-Authentication-Warning: eos.vss.fsi.com: ford owned process doing -bs Date: Thu, 13 Nov 2003 15:38:23 -0600 (CST) From: Brian Ford X-X-Sender: ford@eos To: Patrick Eisenacher cc: cygwin@cygwin.com Subject: Re: cc1plus.exe not included in GCC 3.3.1-3? In-Reply-To: <3FB3F920.7020103@fillmore-labs.com> Message-ID: References: <3FB3F920.7020103@fillmore-labs.com> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII On Thu, 13 Nov 2003, Patrick Eisenacher wrote: > I faced the same problem. Upgrading from the old monolithic gcc to the > new separate front end packaged ones only gave me gcc-c. I had to > separately select gcc-c++. > > I'm not sure whether this can be classified as a setup dependency bug, > since you always face this kind of problem when you split up a > monolithic package into separate smaller ones. Which one(s) do you > classifiy as the default successor(s)? > Logically, I'd say all that were in the previous monolithic package, and none that were not. That's easy. -- 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/