From: Keith Owens <kaos@ocs.com.au>
To: linux-kernel@vger.kernel.org
Subject: kbuild 2.5 preventing mixture of compilers
Date: Thu, 01 Nov 2001 11:43:22 +1100 [thread overview]
Message-ID: <26322.1004575402@kao2.melbourne.sgi.com> (raw)
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.
next reply other threads:[~2001-11-01 0:43 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-11-01 0:43 Keith Owens [this message]
2001-11-01 8:13 ` kbuild 2.5 preventing mixture of compilers Lee Packham
2001-11-01 8:37 ` arjan
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=26322.1004575402@kao2.melbourne.sgi.com \
--to=kaos@ocs.com.au \
--cc=linux-kernel@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox