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/