Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id ; Tue, 23 Oct 2001 09:35:05 -0400 Received: (majordomo@vger.kernel.org) by vger.kernel.org id ; Tue, 23 Oct 2001 09:34:56 -0400 Received: from riker.skynet.be ([195.238.3.132]:10641 "EHLO riker.skynet.be") by vger.kernel.org with ESMTP id ; Tue, 23 Oct 2001 09:34:40 -0400 Message-Id: <200110231334.f9NDYq416699@riker.skynet.be> Date: Tue, 23 Oct 2001 15:34:00 +0200 (CEST) From: jarausch@belgacom.net Reply-To: jarausch@belgacom.net Subject: Thanks - Nvidia modules with 2.4.13-pre6 To: rob cc: Josh McKinney , linux-kernel@vger.kernel.org MIME-Version: 1.0 Content-Type: TEXT/plain; charset=us-ascii Sender: linux-kernel-owner@vger.kernel.org X-Mailing-List: linux-kernel@vger.kernel.org On 23 Oct, rob wrote: ... > Have you changed C compiler since your last kernel upgrade ? ... On 22 Oct, Josh McKinney wrote: > I have seen this same problem here before. I am *pretty sure* that > the problem was I was building the kernel with gcc-3.0 and to build > the nvidia modules I was using gcc-2.95.4. You may want to check what > the sim-link in /usr/bin/cc points to. The nvidia kernel modules use > cc, so make sure cc is a symlink to the same compiler that you used to > build your currently running kernel. That's exactly what happend. Under /usr/local/bin/gcc I have gcc-3.0.2 (cvs) and I recently made a symlink /usr/local/bin/cc to it. While I put /usr/bin (where gcc-2.95.3 is installed) first in my path when compiling the kernel, I didn't do so, when (re)making the kernel modules from Nvidia. This worked fine since the only cc was /usr/bin/cc which pointed to /usr/bin/gcc . I have (re)made Nvidia's module with gcc-2.95.3 and it runs fine now with 2.4.13-pre6 . Sorry for the noise. Helmut. - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/