ok ok, I simplified the explanation a bit, remember it was in brackets at the bottom of a mail describing the solution to the questioner's problem. (I have no idea how technical the questioner is, and he'd have to be pretty technical to understand your explanation ;-) )
I don't know whether it was just cygwin that separated the packages or whether that's how gcc is recommended to be distributed now, but they *are* separate packages now. (in the cygwin world that I'm a part of, and the questioner is a part of) And I'm not saying they are independent of one another, obviously g++ depends on the core gcc package. Regards --------------------------------- Q-Games, Dylan Cuthbert. http://www.q-games.com "Dave Korn" <dk at artimi dot com> wrote in message news:[EMAIL PROTECTED] > > > > -----Original Message----- > > From: cygwin-owner On Behalf Of Dylan Cuthbert > --- explanation snipped --- > > Here endeth the lesson on the internal structure of gcc and compiler > terminology. Hope it was at least mildly interesting. > > > > cheers, > DaveK > -- > Can't think of a witty .sigline today.... > > > [*] Actually, I've oversimplified here, just a little. The compiler > infrastructure calls the frontend to generate a tree; it then converts that > tree to a second internal representation known as RTL; that RTL is then > passed to the backend which generates sequences of assembler instructions > corresponding to it. > > -- 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/
