From: Elikster <elik@webspires.com>
To: Robert F Merrill <griever@t2n.org>
Cc: linux-kernel@vger.kernel.org
Subject: Re[2]: 2.6.2 Compile Failure - Redhat 7.3 Distro
Date: Sat, 7 Feb 2004 20:31:30 -0700 [thread overview]
Message-ID: <1458441483.20040207203130@webspires.com> (raw)
In-Reply-To: <4025754D.5050709@t2n.org>
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]#
>>
>>
>>
RFM> ICE ICE baby!
RFM> Common Redhat GCC bug.
RFM> If gcc -v reports a big number starting with 2.96 (NOT .95),
RFM> it's probably broken.
--
Best regards,
Elikster mailto:elik@webspires.com
prev parent reply other threads:[~2004-02-08 3:30 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-02-07 22:21 [PATCH] 2.6.2 Documentation fix (Documentation/kbuild/modules.txt) Ryan Boder
2004-02-07 23:00 ` 2.6.2 Compile Failure - Redhat 7.3 Distro Elikster
2004-02-07 23:31 ` Robert F Merrill
2004-02-08 3:31 ` Elikster [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=1458441483.20040207203130@webspires.com \
--to=elik@webspires.com \
--cc=griever@t2n.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox