You're kidding, right? If you do exactly what you said, the Nvidia script will try to bail out since the default version of gcc in Lenny (now 4.3.1) doesn't match the version of gcc that built Lenny's default kernel (4.2.4, I think). I'm hoping that the kernel actually released with Lenny (2.6.26 is the target, I think) will fix this problem, but so far as I know it hasn't been fixed yet. The script won't run cleanly on an untweaked Lenny system.AdrianTM wrote:That's pretty much it.
So, at the start, you would need to install gcc-4.2 and run "export CC=/usr/bin/gcc-4.2" or ignore the warning in the Nvidia script. Even if you did one of those things, the module build won't work on many systems because of various problems with the kernel. In last few months, it seems to me that questions and problems about this issue have tripled here. Some of those people may have made mistakes, but I doubt all of them did.
Right now Lenny users have to pick from three bad options:
(1) Use the nv or vesa driver. This is fine for 2D on some systems. On other systems, it leaves video unworkable, even for 2D. (On my desktop, for example, only vesa works at all, and it draws the screen too far to the left. The main part of a default Gnome menu (top panel, far left) and the "Show Desktop" icon (bottom panel, far left) were invisible the first time I installed both Ubuntu and (later) Debian. An interesting challenge for a newbie.)
(2) Mix Sid and Lenny in your sources and try the Debian way. If you don't have a legacy card this seems to work pretty well as far as I can tell, but many people don't want to mix in unstable.
(3) Use a "pure" Lenny system and use the Nvidia binary script. A lot of us don't like this on ideological grounds. Some people won't do it no matter what, some of us only with reluctance. Either way, as I said above, it only begins to solve your problem since there are a number of "gotchas" involved in using their script.