mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: "Corisen" <csyap@starnet.gov.sg>
To: "David Relson" <relson@osagesoftware.com>
Cc: <linux-kernel@vger.kernel.org>
Subject: Re: anyone compiled 2.2.17 on RH7 successfully?
Date: Tue, 14 Nov 2000 10:14:19 +0800	[thread overview]
Message-ID: <008801c04de0$9c08a840$050010ac@starnet.gov.sg> (raw)
In-Reply-To: <200011140118.eAE1IuV17166@moisil.dev.hydraweb.com> <4.3.2.7.2.20001113205514.00af7d20@mail.osagesoftware.com>

thanks for the info. i've kgcc installed during RH7 installation. i've
checked the version to be 2.91.66. i've used the following 2 methods with
kgcc but it won't even allow me to compile:
1. make CC=kgcc zImage
2. change the CC=gcc to CC=kgcc in Makefile

the "make CC=kgcc zImage" process reports the following error messages:

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
/usr/i386-glibc21-linux/include/linux/proc_fs.h:289: parse error before
`off_t'
/usr/i386-glibc21-linux/include/linux/proc_fs.h:290: warning: `struct inode'
declared inside parameter list
/usr/i386-glibc21-linux/include/linux/proc_fs.h:290: warning: its scope is
only this definition or declaration,
/usr/i386-glibc21-linux/include/linux/proc_fs.h:290: warning: which is
probably not what you want.
/usr/i386-glibc21-linux/include/linux/proc_fs.h:293: parse error before
`off_t'
/usr/i386-glibc21-linux/include/linux/proc_fs.h:296: warning: `struct file'
declared inside parameter list
/usr/i386-glibc21-linux/include/linux/proc_fs.h:300: parse error before `}'
/usr/i386-glibc21-linux/include/linux/proc_fs.h:302: parse error before
`off_t'
/usr/i386-glibc21-linux/include/linux/proc_fs.h:305: warning: `struct file'
declared inside parameter list
/usr/i386-glibc21-linux/include/linux/proc_fs.h:308: parse error before
`off_t'
/usr/i386-glibc21-linux/include/linux/proc_fs.h: In function
`proc_scsi_register':
/usr/i386-glibc21-linux/include/linux/proc_fs.h:344: dereferencing pointer
to incomplete type
/usr/i386-glibc21-linux/include/linux/proc_fs.h:345: dereferencing pointer
to incomplete type
/usr/i386-glibc21-linux/include/linux/proc_fs.h: In function
`proc_scsi_unregister':
/usr/i386-glibc21-linux/include/linux/proc_fs.h:359: dereferencing pointer
to incomplete type
/usr/i386-glibc21-linux/include/linux/proc_fs.h:362: `NULL' undeclared
(first use in this function)
/usr/i386-glibc21-linux/include/linux/proc_fs.h:362: (Each undeclared
identifier is reported only once
/usr/i386-glibc21-linux/include/linux/proc_fs.h:362: for each function it
appears in.)
/usr/i386-glibc21-linux/include/linux/proc_fs.h:363: dereferencing pointer
to incomplete type
/usr/i386-glibc21-linux/include/linux/proc_fs.h:365: dereferencing pointer
to incomplete type
/usr/i386-glibc21-linux/include/linux/proc_fs.h:368: sizeof applied to an
incomplete type
.....many more lines
.....many more lines


----- Original Message -----
From: David Relson <relson@osagesoftware.com>
To: Corisen <csyap@starnet.gov.sg>
Cc: <linux-kernel@vger.kernel.org>
Sent: Tuesday, November 14, 2000 9:58 AM
Subject: Re: anyone compiled 2.2.17 on RH7 successfully?


> 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/

-
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/

  reply	other threads:[~2000-11-14  2:44 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
2000-11-14  2:14     ` Corisen [this message]
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='008801c04de0$9c08a840$050010ac@starnet.gov.sg' \
    --to=csyap@starnet.gov.sg \
    --cc=linux-kernel@vger.kernel.org \
    --cc=relson@osagesoftware.com \
    /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®