mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: David Relson <relson@osagesoftware.com>
To: "Corisen" <csyap@starnet.gov.sg>
Cc: <linux-kernel@vger.kernel.org>
Subject: Re: anyone compiled 2.2.17 on RH7 successfully?
Date: Mon, 13 Nov 2000 20:58:05 -0500	[thread overview]
Message-ID: <4.3.2.7.2.20001113205514.00af7d20@mail.osagesoftware.com> (raw)
In-Reply-To: <005a01c04ddc$6dc14360$050010ac@starnet.gov.sg>
In-Reply-To: <200011140118.eAE1IuV17166@moisil.dev.hydraweb.com>

Corisen,

RedHat 7.0's version of gcc, known as gcc 2.96, is incompatible with the 
kernel's code.  Preprocessor changes cause the problem you encountered.  It 
also has some defects in how it optimizes code that would cause the kernel 
to run incorrectly.

The 7.0 distribution includes an older version of gcc, known as kgcc (for 
kernel gcc), that compiles code correctly and can be used for kernel 
compilation.  Install the rpm and go for it!

David

At 08:44 PM 11/13/00, Corisen wrote:
>has anyone running RedHat7(with kernel 2.2.16, gcc 2.96, kgcc 2.91.66)
>complied 2.2.17 kernel successfully?
>
>i've downloaded the source and gunzip/untar to /root/linux-2.2.17
>
>1. make menuconfig (ok)
>2. make dep (ok)
>3. make zImage
>===> lots of warning message
>===> error: checksum.S:231 badly punctuated parameter list in #define
>===> error: checksum.S:237 badly punctuated parameter list in #define
>
>4. make CC=kgcc zImage
>===> snapshot of errors reported:
>In file included from init/main.c:15:
>/usr/i386-glibc21-linux/include/linux/proc_fs.h:283: parse error before
>`mode_t'
>/usr/i386-glibc21-linux/include/linux/proc_fs.h:283: warning: no semicolon
>at end of struct or union
>/usr/i386-glibc21-linux/include/linux/proc_fs.h:284: warning: data
>definition has no type or storage class
>/usr/i386-glibc21-linux/include/linux/proc_fs.h:285: parse error before
>`uid'
>/usr/i386-glibc21-linux/include/linux/proc_fs.h:285: warning: data
>definition has no type or storage class
>/usr/i386-glibc21-linux/include/linux/proc_fs.h:286: parse error before
>`gid'
>/usr/i386-glibc21-linux/include/linux/proc_fs.h:286: warning: data
>definition has no type or storage class
>....many more errors
>....many more errors
>....
>
>5. changed CC= kgcc in Makefile and execute "make zImage"
>===> same error as 3 (strange, seems like the the compilation is still by
>gcc and not kgcc despite the change)
>
>i was able to compile 2.4.0-test10 kernel image with "make CC=kgcc bzImage"
>
>pls kindly advise on the possible solutions.
>
>thanks.
>
>
>
>
>
>-
>To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
>the body of a message to majordomo@vger.kernel.org
>Please read the FAQ at http://www.tux.org/lkml/

--------------------------------------------------------
David Relson                   Osage Software Systems, Inc.
relson@osagesoftware.com       514 W. Keech Ave.
www.osagesoftware.com          Ann Arbor, MI 48103
voice: 734.821.8800            fax: 734.821.8800

-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
Please read the FAQ at http://www.tux.org/lkml/

  parent reply	other threads:[~2000-11-14  2:28 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2000-11-13 20:18 PATCH: Pcmcia/Cardbus/xircom_tulip in 2.4.0-test10 David Hinds
2000-11-14  1:18 ` Ion Badulescu
2000-11-14  1:44   ` anyone compiled 2.2.17 on RH7 successfully? Corisen
2000-11-14  1:58   ` David Relson [this message]
2000-11-14  2:14     ` Corisen
2000-11-14  3:49       ` Michael Rothwell
2000-11-14  3:37         ` Dan Browning
2000-11-14  7:08       ` anyone compiled 2.2.17 on RH7 successfully? [SOLVED] Corisen

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=4.3.2.7.2.20001113205514.00af7d20@mail.osagesoftware.com \
    --to=relson@osagesoftware.com \
    --cc=csyap@starnet.gov.sg \
    --cc=linux-kernel@vger.kernel.org \
    /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

all inboxes | Powered by JetHome®