Installing a compiler by default

[Alexander Jacob Tsykin]

On Saturday 10 June 2006 02:53, Alan McKinnon wrote:
> > > You do have to resolve dependencies manually of course, but these
> > > are much rarer than you might think, usually some underlying lib.
> > > Rinse, repeat.
> >
> > It's always been pretty frequent for me,andunless you know what to
> > look for, you can spend a lot of time hunting for dependencies and
> > still never find them.
>
> gcc and binutils are the worst for that. Heck, make that the entire
> toolchain. Fortunately only LFS, Gentoo and FreeBSD users need worry
> about that, it's not applicable here.
>
> Again, a good README is invaluable here
>
not always available. And even if it is, so the person installs libstdc++ 
according to the README, he would never know to install the -dev package. 
Ultimately, compiling is really only for people who know what they are doing, 
otherwise, they should not be trying because all it takes is one bad kernel 
module which they don't know how to unload and they've compiled according to 
a bad distribution agnostic guide, and bang, the system is gone, and only 
somebody who knows what they are doing can fix it, which our theoretical user 
is not. A practical example is the Nvidia drivers, they have stuffed up for 
me in the past (not from nvidia-glx, and admittedly, not in Ubuntu, it was in 
Gentoo) and had I not known what I was doing, I would never have been able to 
get X back.

Sasha