public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Boris Pisarcik <boris@acheron.sk>
To: linux-kernel@vger.kernel.org
Subject: Re: Compiling problem kernel 2.4.2
Date: Wed, 4 Apr 2001 19:21:04 +0200	[thread overview]
Message-ID: <20010404192104.A6914@Boris> (raw)
In-Reply-To: <5.0.2.1.2.20010326175151.01eef100@pop.wanadoo.nl>
In-Reply-To: <5.0.2.1.2.20010326175151.01eef100@pop.wanadoo.nl>; from tscholte@wanadoo.nl on Mon, Mar 26, 2001 at 06:00:36PM +0200

 
> 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

Hi.

-02 mean -O2 ?

Do you comile over NFS ? Did you try it to local-compile , or compile
on another system version ? It really
may be nfs or some system bug, if you compile on some old system (what kernel
version did you compile on ? They me differ on slack and redhat machines.)

I recently had a bug with gnu assembler, which could safely compile all
files a tried, but not the ones that consisted of any combination 
3 chars name+1 char suffix.
Really interesting bug too.

Bye                                                                   B.


      parent reply	other threads:[~2001-04-04 19:10 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2001-03-26 16:00 Compiling problem kernel 2.4.2 Theodoor Scholte
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 [this message]

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=20010404192104.A6914@Boris \
    --to=boris@acheron.sk \
    --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