[lkml]   [2001]   [Feb]   [2]   [last100]   RSS Feed
Views: [wrap][no wrap]   [headers]  [forward] 
Messages in this thread
SubjectRe: [reiserfs-list] ReiserFS Oops (2.4.1, deterministic, symlink related)
On Fri, Feb 02, 2001 at 09:57:39PM +0000, 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 ..

Alan, as a user (one of those few that actually read documentation), I
think it is a good idea to stop people from hurting their data by using
the wrong compiler and assuming everything is ok until shit happens.

As you explained, one either gets the bug reports or the complaints
that $SOURCE doesn't compile. The work for the developers might be
about the same size, the impact on the users' side is less
destructive, though.


arthur dot erhardt at pit dot physik dot uni dash tuebingen dot de
*pgp key available* dg7sea

A physicist is an atom's way of knowing about atoms.
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to
Please read the FAQ at

 \ /
  Last update: 2005-03-22 13:28    [W:0.348 / U:0.360 seconds]
©2003-2020 Jasper Spaans|hosted at Digital Ocean and TransIP|Read the blog|Advertise on this site