Greg Lopp on Thu, 24 May 2001 23:42:00 -0400 |
On Thu, May 24, 2001 at 10:49:38PM -0400, Michael Leone wrote: > On 24 May 2001 22:41:45 -0400, MaD dUCK wrote: > > also sprach Michael Leone (on Thu, 24 May 2001 10:35:14PM -0400): > > > Just never re-compile a kernel with "gcc"; always use "kgcc". > > > > huh? maybe i am just inherently stupid, but the standard Makefile for > > the linux kernel uses gcc... moreover, my (debian) systems do not have > > any kgcc on them. what's up? > > We're not talking about Debian; we're talking about RH7. > > On RH7, "kgcc" is supposed to call out gcc 2.95.3 (the stable version, > which is suitable for kernel compiling); "gcc" calls out gcc 2.96 (i.e., > the unstable, "never-compile-a-kernel-with-this-version" compiler). Unstable? The folks at redhat seem to think that gcc 2.96 is more standards compliant than the kernel code. http://bugzilla.redhat.com/bugzilla/show_bug.cgi?id=20593 suggests that all this fuss is over some syntax "errors". What is all this "binary incompatible" stuff coming from? To restate an earlier question : can anyone point me to a decent _technical_ explanation of this problem? Is kgcc just for the syntax errors? What is binary incompatible with what? How is it binary incompatible? ______________________________________________________________________ Philadelphia Linux Users Group - http://www.phillylinux.org Announcements-http://lists.phillylinux.org/mail/listinfo/plug-announce General Discussion - http://lists.phillylinux.org/mail/listinfo/plug
|
|