-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 On Wednesday 30 October 2002 03:55 pm, mark wrote: > On Wednesday 30 October 2002 10:55 am, you is done writ: > > I have attempted to compile rpms for 7.3 using the files in > > compat-gcc rpms > > > > However after using CC=gcc296 CXX=g++296 > > To quote an email I just had from a friend of mine, in response to > problems I > > had trying to compile the 2.4.19 kernel: > >Rob Landley <[EMAIL PROTECTED]> wrote: > > > > Well, there's your problem right there. > > > > Don't use the brain-damaged 2.96. Even Red Hat didn't compile its > > 7.x kernels with gcc 2.96, that's why they ship kgcc. (Hack the > > makefile, tell it to use kgcc as its compiler. Or better yet, rm > > /usr/bin/gcc and ln -s /usr/bin/kgcc /usr/bin/gcc). 2.96 is known to > > miscompile a ton of other stuff, it's just the kernel is the most > > obvious and least forgving.
OH, Please. Not this FUD again. The kernels for the 7.x release compiled without any difficulty using gcc-2.96. While there may have been valid arguments on both sides of the gcc 2.96 debate, none of the ones presented here are among them. As for gcc 2.96 miscompiling things, the main offenders, and the ones who screamed the loudest, were those maintaining broken code. The MPlayer developers were one group who complained loudly. An example of why their code, and not gcc 2.96, was broken is given at the bottom of the link below. See: http://www.redhat.com/advice/speaks_gcc.html - -- - -Michael pgp key: http://www.tuxfan.homeip.net:8080/gpgkey.txt Red Hat Linux 7.{2,3}|8.0 in 8M of RAM: http://www.rule-project.org/ - -- -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.0.7 (GNU/Linux) iD8DBQE9wIhwn/07WoAb/SsRAp7PAKCVgHz7BYgl1l+wCIJdfSEoe2NOhACffQW+ nVSff9XJOUqIXcK6SXEXfVE= =tIu8 -----END PGP SIGNATURE----- -- redhat-list mailing list unsubscribe mailto:redhat-list-request@;redhat.com?subject=unsubscribe https://listman.redhat.com/mailman/listinfo/redhat-list
