On Thu, 4 Nov 1999, John Aldrich wrote:
> On Thu, 04 Nov 1999, you wrote:
> >
> > half me half you :)
> >
> > with pgcc /usr/bin/gcc will link to pgcc (colorgcc throws this out of whack a lil)
> >
> > Basicly what i was trying to say was the g in gcc or g++, is for gnu
> > "compliance" (for lack of a better word). It doesn't matter if you've
> > installed gcc, pgcc, or egcs, /usr/bin/gcc will be there and point and
> > something.
> >
> > libstdc++-devel is the most commonly overlooked devel package, but the
> > config.log will always point directly to the problem as ./configure semi
> > hides the errors so it looks pretty (not that there is anything wrong with
> > a .log file)
> >
> Ahh...Ok. I think I understand now... (sorta <G> As I said, I'm no
> programmer! <G>) My thinking was that the source code might be
> looking for a SPECIFIC version of g++, and seeing as to how Mandrake
> ships with pgcc(++) the source code calling for a SPECIFIC g++
> compiler might throw things out of whack...or is that virtually
> impossible??? ;-)
> John
Nope not impossible, there are all kinds of things that can happen
different depending on the compiler.
--
MandrakeSoft http://www.mandrakesoft.com/
--Axalon
