[eside-ghost] Problemas con las headers

[Oscar]

Hola Jon,

Saturday, October 25, 2003, 10:51:42 AM, tu escribiste:

JA> Hola a tod en s. Me he bajado el kernel 2.4.22 
JA> (linux-2.4.22.tar.bz2) y las headers
JA> (kernel-headers-2.4.22-1_2.4.22-3_i386.deb) 
JA> pero al intentar instalar los drivers de NVIDIA me da problemas de
JA> incompatibilidad con las headers. ¿No son las que se corresponden con el
JA> kernel?  Pues ahi queda eso, yo sigo intentándolo que la noche es joven.
JA> Agur

jon e estado mirado el documento de ayuda del installer ese de las
anrices que tare ahora el tema (me parecia ams facil antes) y te pone
lo del error nuestro aquel

Q: Compiling the NVIDIA kernel module gives this error:

        You appear to be compiling the NVIDIA kernel module with
        a compiler different from the one that was used to compile
        the running kernel. This may be perfectly fine, but there
        are cases where this can lead to unexpected behaviour and
        system crashes.

        If you know what you are doing and want to override this
        check, you can do so by setting IGNORE_CC_MISMATCH.

        In any other case, set the CC environment variable to the
        name of the compiler that was used to compile the kernel.

A: You should compile the NVIDIA kernel module with the same compiler
   version that was used to compile your kernel.  Some Linux kernel data
   structures are dependent on the version of gcc used to compile it;
   for example, in include/linux/spinlock.h:

        ...
        * Most gcc versions have a nasty bug with empty initializers.
        */
        #if (__GNUC__ > 2)
          typedef struct { } rwlock_t;
          #define RW_LOCK_UNLOCKED (rwlock_t) { }
        #else
          typedef struct { int gcc_is_buggy; } rwlock_t;
          #define RW_LOCK_UNLOCKED (rwlock_t) { 0 }
        #endif

   If the kernel is compiled with gcc 2.x, but gcc 3.x is used when the
   kernel interface is compiled (or vice versa), the size of rwlock_t
   will vary, and things like ioremap will fail.

   To check what version of gcc was used to compile your kernel, you
   can examine the output of:

        cat /proc/version

   To check what version of gcc is currently in your $PATH, you can
   examine the output of:

        gcc -v

-- 
Agur
 Oscar                            mailto:1osatien en rigel.deusto.es