From: Marco Roeland <marco.roeland@xs4all.nl>
To: yiding_wang@agilent.com
Cc: linux-kernel@vger.kernel.org
Subject: Re: Still have build error on 2.6.2 fc/proc/array.c
Date: Fri, 20 Feb 2004 14:03:06 +0100 [thread overview]
Message-ID: <20040220130306.GA11351@localhost> (raw)
In-Reply-To: <0A78D025ACD7C24F84BD52449D8505A15A80D4@wcosmb01.cos.agilent.com>
On Tuesday February 17th yiding_wang@agilent.com wrote:
> Based on README and requirement of Changes in linux-2.6.2, I have updated needed utilities and other files with the following:
> binnutils 2.14
> e2fsprogs-1.34
> module-init-tools-3.0-pre10
> procps 3.1.15
>
> Everything is installed OK.
>
> Then compiling new 2.6.2 kernel still fails wi the following. What is the upgrade file for this problem?
Your kernel sources and all the mentioned tools are now OK, and probably
were OK already. The only thing that is giving you the error is the
version of the gcc compiler that you use (2.96).
> make[1]: `arch/i386/kernel/asm-offsets.s' is up to date.
> CHK include/linux/compile.h
> CC fs/proc/array.o
> fs/proc/array.c: In function `proc_pid_stat':
> fs/proc/array.c:398: Unrecognizable insn:
> (insn/i 727 1015 1009 (parallel[
> ...
It is the *compiler* (gcc-2.96) that has a bug here. As this version of
gcc has many other bugs developers no longer work around difficulties
this specific version of gcc has.
What you can do is upgrade your gcc package to a later version (3.2.x or
3.3.x or even later from your distribution). As a workaround I've made a
little patch that you can apply to fs/proc/array.c if you still want to
keep using gcc 2.96 for a little while. It's archived here:
http://marc.theaimsgroup.com/?l=linux-kernel&m=107567013416122&w=2
--
Marco Roeland
next prev parent reply other threads:[~2004-02-20 13:05 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-02-17 20:37 Still have build error on 2.6.2 fc/proc/array.c yiding_wang
2004-02-20 13:03 ` Marco Roeland [this message]
-- strict thread matches above, loose matches on Subject: below --
2004-02-20 16:59 yiding_wang
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=20040220130306.GA11351@localhost \
--to=marco.roeland@xs4all.nl \
--cc=linux-kernel@vger.kernel.org \
--cc=yiding_wang@agilent.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