Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id ; Mon, 17 Jun 2002 20:24:53 -0400 Received: (majordomo@vger.kernel.org) by vger.kernel.org id ; Mon, 17 Jun 2002 20:24:52 -0400 Received: from mailout11.sul.t-online.com ([194.25.134.85]:29416 "EHLO mailout11.sul.t-online.com") by vger.kernel.org with ESMTP id ; Mon, 17 Jun 2002 20:24:51 -0400 To: Emmanuel Michon Cc: linux-kernel@vger.kernel.org Subject: Re: binary compatibity (mixing different gcc versions) in modules References: <7w3cvmdquu.fsf@avalon.france.sdesigns.com> From: Andi Kleen Date: 18 Jun 2002 02:24:27 +0200 In-Reply-To: Emmanuel Michon's message of "Mon, 17 Jun 2002 14:40:07 +0200" Message-ID: User-Agent: Gnus/5.070095 (Pterodactyl Gnus v0.95) Emacs/20.7 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 Content-Length: 980 Lines: 23 Emmanuel Michon writes: > Hi, > > looking at nvidia proprietary driver, the makefile warns > the user against insmod'ing a module compiled with a gcc > version different from the one that was used to compile > the kernel. > > This sounds strange to me, since I never encountered this > problem. Some earlier obsolete gcc versions had problems with empty types. This lead to an #if based on the compiler version that added a dummy field to spinlocks even for UP kernels. This made structure offsets of structures with spinlocks change based on gcc version. Should be long gone with recent compilers. Still there are enough other variables to structure offsets depending on the configuration. -Andi - 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/