mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Theodoor Scholte <tscholte@wanadoo.nl>
To: linux-kernel@vger.kernel.org
Subject: Compiling problem kernel 2.4.2
Date: Mon, 26 Mar 2001 18:00:36 +0200	[thread overview]
Message-ID: <5.0.2.1.2.20010326175151.01eef100@pop.wanadoo.nl> (raw)

Hello,

I have a problem with compiling kernel-2.4.2. When I want to make a bzImage 
on a RedHat Linux 5.2 box,
then I get this error-message:

gcc -D__KERNEL__ -I/usr/src/linux/include -Wall -Wstrict-prototypes -02
-fomit-frame-pointer -fno-strict-aliasing -pipe -march=i486  -c -o init/main.o
init/main.c
gcc -D__KERNEL__ -I/usr/src/linux/include -Wall -Wstrict-prototypes -02
fomit-frame-pointer -fno-strict-aliasing -pipe  -march=i486
-DUTS_MACHINE='"i386"' -c -o init/version.o init/version.c
cpp: /usr/src/linux/include/linux/compile.h: Input/output error
init/version.c:20: `UTS_VERSION' undeclared here (not in a function)
init/version.c:20: initializer element for `system_utsname.version' is not
constant
init/version.c:25: parse error before `LINUX_COMPILE_BY'
make: *** [init/version.o] Error 1

I have installed these software revisions:
GNU C  egcs-2.91.66
GNU make  3.78.1
binutils  2.9.5.0.22-6
util-linux  2.10f
modutils  2.4.2
e2fsprogs  1.19

What is the solution for this problem? On a Slackware 7.1-box with the same 
software-revisions I have no problems with compiling kernel 2.4.2.

Thanks in advance,

Theodoor Scholte


             reply	other threads:[~2001-03-26 15:50 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2001-03-26 16:00 Theodoor Scholte [this message]
2001-03-26 16:12 ` Tobias Ringstrom
2001-03-26 16:42 ` Theodoor Scholte
2001-03-26 18:57   ` Theodoor Scholte
2001-03-26 21:23     ` Tobias Ringstrom
2001-03-27 20:01     ` Theodoor Scholte
2001-04-04 17:21 ` Boris Pisarcik

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=5.0.2.1.2.20010326175151.01eef100@pop.wanadoo.nl \
    --to=tscholte@wanadoo.nl \
    --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®