Status of compiling 2.4 with gcc3.1?
How far from wise is it to compile the 2.4.19-prex kernel with gcc3.1? Is there a list of known issues? Only report of trouble I've seen so far is
http://groups.google.com/groups?selm=linux.kernel.5.1.0.14.2.20020515015506.02749780%40pop.cus.cam.ac.uk
and that's just a compile-time fatal error building ntfs.
- Dan
Scribbling feverishly on May 20, Dan Kegel managed to emit:
Quoted 5 lines
How far from wise is it to compile the 2.4.19-prex kernel with gcc3.1? Is there a list of known issues? Only report of trouble I've seen so far is
http://groups.google.com/groups?selm=linux.kernel.5.1.0.14.2.20020515015506.02749780%40pop.cus.cam.ac.uk
and that's just a compile-time fatal error building ntfs.
I'm running 2.4.18 built with GCC 3.1 and having no trouble that I've seen.
Kurt
Signature · 1 line
For large values of one, one equals two, for small values of two.
Quoted 9 lines · Kurt Wall
Scribbling feverishly on May 20, Dan Kegel managed to emit:
Quoted 5 lines
How far from wise is it to compile the 2.4.19-prex kernel with gcc3.1? Is there a list of known issues? Only report of trouble I've seen so far is
http://groups.google.com/groups?selm=linux.kernel.5.1.0.14.2.20020515015506.02749780%40pop.cus.cam.ac.uk
and that's just a compile-time fatal error building ntfs.
Quoted 4 lines
I'm running 2.4.18 built with GCC 3.1 and having no trouble that I've seen.
Kurt
I'm running both 2.4.19-pre8 and 2.5.16, and, though both were compiled with gcc 3.1, I am having no problems.
Although I remember someone saying that gcc 3.1 produced larger binaries, and inefficient code in some places.
Also, gcc 3.1 generates lots of warnings because of things like multi-line string literals, etc.
Signature · 3 lines
-o) J o h n W e b e r /\\ [email protected] _\/v http://www.linuxhq.com/people/weber/