From: Keith Owens <kaos@ocs.com.au>
To: linux-kernel@vger.kernel.org
Subject: kbuild 2.5 preventing mixture of compilers
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Date: Thu, 01 Nov 2001 11:43:22 +1100
Message-ID: <26322.1004575402@kao2.melbourne.sgi.com>
Sender: linux-kernel-owner@vger.kernel.org

FYI, kbuild 2.5 will check that all the kernel and modules were
compiled with the same version of gcc, in particular they must all have
the same value of

  $(CC) -v 2>&1 | sed -ne '1s:.*/\([^/]*/[^/]*\)/[^/]\+$:\1:p'

e.g. i386-redhat-linux/2.96

Minor version data such as build date is assumed to be irrelevant.
Anybody who makes significant changes to compiler output without
changing the version number gets what they deserve.

Modules built with a different compiler from the kernel will not load
unless they are forced with insmod -f.

Is this going to cause problems for anybody?  I see no justification
for mixing kernel objects built by different compilers and I know of
problems that have been caused by doing so.

-
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/