OK. This has nothing to do with the sources. It may have something to do with the kbuild, how it gets its paths!
I have always had funny stuff building nvidia.ko, both with m-a and with nvidia's .run. It thinks my 2.6.23 was built with gcc-2. I can only get nvidia to build if I symlink to that. The complaint is spurious. M-a will try to build with an override. It was indeed a 96.43.01 that got installed. The fact that I could change the number and run with the new libglx says something about the need for this test. The .01 came off a different /usr/modules subdirectory tree entirely. I have /usr/modules/nvidia-kernel-legacy without the 96xx with builds for 2.6.18. I will get rid of these. In tune with a previous bug I sent in for m-a, the build apparently uses BOTH the SYSSRC and /usr/src/linux. Both MUST point to the same place. Only then, all is well. If there is a bug here, it might be that SYSSRC should override /usr/src/linux entirely. -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
