From: "Randy.Dunlap" <rddunlap@osdl.org>
To: walt <walt@nea-fast.com>
Cc: marco.roeland@xs4all.nl, linux-kernel@vger.kernel.org
Subject: Re: 2.6-test11 build error (fs/proc/array.c gcc 2.96 again!)
Date: Fri, 12 Dec 2003 12:03:02 -0800 [thread overview]
Message-ID: <20031212120302.6f58dafe.rddunlap@osdl.org> (raw)
In-Reply-To: <200312121502.58555.walt@nea-fast.com>
On Fri, 12 Dec 2003 15:02:58 -0500 walt <walt@nea-fast.com> wrote:
| On Friday 12 December 2003 01:13 pm, Marco Roeland wrote:
| > On Friday december 12th 2003 walt wrote:
| > > I got the following when trying to compile 2.6.0-test11. Config is
| > > attached.
| > >
| > > [internal compiler error for fs/proc/array.c]
| >
|
| Thanks Marco!
|
| FYI - I removed
| Kernel .config support (IKCONFIG)
| and it compiled fine.
You disabled IKCONFIG --> with or without applying the patch <-- ??
and it compiled fine...
--
~Randy
MOTD: Always include version info.
next prev parent reply other threads:[~2003-12-12 20:11 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-12-12 16:59 2.6-test11 build error walt
2003-12-12 18:13 ` 2.6-test11 build error (fs/proc/array.c gcc 2.96 again!) Marco Roeland
2003-12-12 20:02 ` walt
2003-12-12 20:03 ` Randy.Dunlap [this message]
2003-12-12 20:21 ` walt
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=20031212120302.6f58dafe.rddunlap@osdl.org \
--to=rddunlap@osdl.org \
--cc=linux-kernel@vger.kernel.org \
--cc=marco.roeland@xs4all.nl \
--cc=walt@nea-fast.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