From: David Ford <david@linux.com>
To: unlisted-recipients:; (no To-header on input)@pop.zip.com.au
Cc: Ion Badulescu <ionut@moisil.cs.columbia.edu>,
Hans Reiser <reiser@namesys.com>,
linux-kernel@vger.kernel.org, reiserfs-list@namesys.com,
Jan Kasprzak <kas@informatics.muni.cz>
Subject: Re: [reiserfs-list] ReiserFS Oops (2.4.1, deterministic, symlink related)
Date: Sat, 03 Feb 2001 00:57:45 -0800 [thread overview]
Message-ID: <3A7BC808.E9BF5B44@linux.com> (raw)
In-Reply-To: <E14OoD8-0007GI-00@the-village.bc.nu>
[-- Attachment #1: Type: text/plain, Size: 1374 bytes --]
How about a simple patch to the top level makefile that checks the gcc
version then prints a distinct message ..'this compiler hasn't been approved
for compiling the kernel', sleeping for one second, then continuing on. This
solution doesn't stop compiling and makes a visible indicator without forcing
anything.
Sample attached.
-d
Alan Cox wrote:
> > As it stands, there is no way to determine programatically whether
> > gcc-2.96 is broken or now. The only way to do it is to check the RPM
> > version -- which, needless to say, is a bit difficult to do from the
> > C code about to be compiled. So I can't really blame Hans if he decides
> > to outlaw gcc-2.96[.0] for reiserfs compiles.
>
> Oh I can see why Hans wants to cut down his bug reporting load. I can also
> say from experience it wont work. If you put #error in then everyone will
> mail him and complain it doesnt build, if you put #warning in nobody will
> read it and if you dont put anything in you get the odd bug report anyway.
>
> Basically you can't win and unfortunately a shrink wrap forcing the user
> to read the README file for the kernel violates the GPL ..
>
> Jaded, me ?
>
> Alan
--
There is a natural aristocracy among men. The grounds of this are virtue and talents. Thomas Jefferson
The good thing about standards is that there are so many to choose from. Andrew S. Tanenbaum
[-- Attachment #2: lkml-gccversion.patch --]
[-- Type: text/plain, Size: 961 bytes --]
--- Makefile.orig Sat Feb 3 00:48:26 2001
+++ Makefile Sat Feb 3 00:45:00 2001
@@ -253,11 +253,23 @@
-o vmlinux
$(NM) vmlinux | grep -v '\(compiled\)\|\(\.o$$\)\|\( [aUw] \)\|\(\.\.ng$$\)\|\(LASH[RL]DI\)' | sort > System.map
-symlinks:
+symlinks: gccversioncheck
rm -f include/asm
( cd include ; ln -sf asm-$(ARCH) asm)
@if [ ! -d include/linux/modules ]; then \
mkdir include/linux/modules; \
+ fi
+
+gccversioncheck:
+ @gccversion=`${HOSTCC} --version`;\
+ echo Using gcc version: $$gccversion;\
+ if [ "x$${gccversion}" != "x2.95.2" ]; then \
+ echo "********************************************************************"; \
+ echo "*** This compiler version is not approved for compiling the kernel"; \
+ echo "*** version: " $$HOSTCC $$gccversion ; \
+ echo "*** Please consider this when reporting bugs" ;\
+ echo "********************************************************************"; \
+ sleep 1; \
fi
oldconfig: symlinks
next prev parent reply other threads:[~2001-02-03 8:58 UTC|newest]
Thread overview: 38+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <cs.lists.linux-kernel/E14OjME-0006nU-00@the-village.bc.nu>
2001-02-02 21:22 ` [reiserfs-list] ReiserFS Oops (2.4.1, deterministic, symlink related) Ion Badulescu
2001-02-02 21:57 ` Alan Cox
2001-02-02 22:06 ` Arthur Erhardt
2001-02-02 22:06 ` Hans Reiser
2001-02-02 22:57 ` Ion Badulescu
2001-02-05 2:50 ` Brian Wolfe
2001-02-05 4:08 ` Albert D. Cahalan
2001-02-05 11:58 ` Alan Cox
2001-02-05 11:36 ` Hans Reiser
2001-02-05 12:44 ` [reiserfs-list] ReiserFS Oops (2.4.1, deterministic, symlink Alan Cox
2001-02-05 12:16 ` Hans Reiser
2001-02-05 12:52 ` Alan Cox
2001-02-05 12:33 ` Hans Reiser
2001-02-05 12:57 ` Dr. David Gilbert
2001-02-05 16:57 ` [reiserfs-list] ReiserFS Oops (2.4.1, deterministic, symlink related) James Sutherland
2001-02-12 3:41 ` [reiserfs-list] ReiserFS Oops (2.4.1, deterministic, symlink Albert D. Cahalan
2001-02-12 9:45 ` Hans Reiser
2001-02-05 12:16 ` [reiserfs-list] ReiserFS Oops (2.4.1, deterministic, symlink related) Dr. David Gilbert
2001-02-05 5:21 ` Gregory Maxwell
2001-02-05 12:02 ` Alan Cox
2001-02-05 11:38 ` Hans Reiser
2001-02-05 11:55 ` Alan Cox
2001-02-05 11:35 ` Hans Reiser
2001-02-05 20:19 ` Brian Wolfe
2001-02-02 22:42 ` Ion Badulescu
2001-02-03 3:43 ` Johan Kullstam
2001-02-03 8:57 ` David Ford [this message]
2001-02-03 10:00 ` [reiserfs-list] " J . A . Magallon
2001-02-03 23:26 ` Felix von Leitner
2001-02-04 11:04 ` Alan Cox
2001-02-04 3:24 ` John Alvord
2001-02-02 11:28 Jan Kasprzak
2001-02-02 11:04 ` [reiserfs-list] " Hans Reiser
2001-02-02 12:16 ` Jan Kasprzak
2001-02-02 12:34 ` Alan Cox
2001-02-02 13:09 ` Jan Kasprzak
2001-02-02 16:36 ` Jan Kasprzak
2001-02-02 16:46 ` Alan Cox
2001-02-02 12:15 ` John Morrison
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=3A7BC808.E9BF5B44@linux.com \
--to=david@linux.com \
--cc=ionut@moisil.cs.columbia.edu \
--cc=kas@informatics.muni.cz \
--cc=linux-kernel@vger.kernel.org \
--cc=reiser@namesys.com \
--cc=reiserfs-list@namesys.com \
/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