From: "Nick Warne" <nick@ukfsn.org>
To: linux-kernel@vger.kernel.org
Subject: Re[3]: 2.6.2 Compile Failure - Redhat 7.3 Distro
Date: Sun, 08 Feb 2004 12:13:13 -0000 [thread overview]
Message-ID: <402627D9.21481.19D612E6@localhost> (raw)
In-Reply-To: <1075729900.777.40.camel@bart>
> Hello Robert,
>
> Sighs...I guess I have to look at making new set of RPM packages
> for 7.3 Distros \
> to upgrade the glibc, gcc and few other packages to have it updated
> to be able to \
> compile the kernel.
>
> Thanks.
Saturday, February 7, 2004, 4:31:25 PM, you wrote:
RFM> Elikster wrote:
> > fs/proc/array.c: In function `proc_pid_stat':
> > fs/proc/array.c:398: Unrecognizable insn:
> > (insn/i 721 1009 1003 (parallel[
> > (set (reg:SI 0 eax)
> > (asm_operands ("") ("=a") 0[
> > (reg:DI 1 edx)
> > ]
> > [
> > (asm_input:DI ("A"))
> > ] ("include/linux/times.h") 38))
> > (set (reg:SI 1 edx)
> > (asm_operands ("") ("=d") 1[
> > (reg:DI 1 edx)
> > ]
> > [
> > (asm_input:DI ("A"))
> > ] ("include/linux/times.h") 38))
> > (clobber (reg:QI 19 dirflag))
> > (clobber (reg:QI 18 fpsr))
> > (clobber (reg:QI 17 flags))
> > ] ) -1 (insn_list 715 (nil))
> > (nil))
> > fs/proc/array.c:398: confused by earlier errors, bailing out
> > make[2]: *** [fs/proc/array.o] Error 1
> > make[1]: *** [fs/proc] Error 2
> > make: *** [fs] Error 2
> > root@longmont [/usr/src/linux-2.6.2]#
I was getting all sorts of funny reportedly code errors with RH GCC:
gcc version 2.96 20000731 (Red Hat Linux 7.2 2.96-112.7.1)
It used to build ok, then report an error somewhere.. but never in
the same place/file. Funnily enough, a kernel built with 5 or 6 of
these errors (i.e. just 'make'ing again from where it 'broke' to
carry on the build) is OK.
Well, for me it turned out GCC gets very _flakey_ if CPU (K6 233)
gets too hot...
...I just put on a bigger heatsink, and it fixed it!
The machine had/has never shown any other symptoms of overheating
until/unless I build a kernel.
Nick
prev parent reply other threads:[~2004-02-08 12:13 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-01-29 10:01 Where do the "Machine Check Exceptions" come from? Kai Militzer
2004-02-02 13:51 ` Where do the "Machine Check Exceptions" come from? [update] Kai Militzer
2004-02-08 12:13 ` Nick Warne [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=402627D9.21481.19D612E6@localhost \
--to=nick@ukfsn.org \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.