From: Raj <obelix123@toughguy.net>
To: Raj <obelix123@toughguy.net>
Cc: Jeff Chua <jeffchua@silk.corp.fedex.com>,
Linux Kernel <linux-kernel@vger.kernel.org>
Subject: Re: Gcc problems on linux-2.6.3
Date: Fri, 20 Feb 2004 17:31:33 +0530 [thread overview]
Message-ID: <4035F71D.7080306@toughguy.net> (raw)
In-Reply-To: <Pine.LNX.4.56.0402201440490.1554@localhost.localdomain>
Gcc is working fine on 2.6.3
My mistake. I totally screwed up the kernels in /boot. I booted a wrong
one and was expecting
things to work fine :-(( .
Sorry for the time wasted.
/Raj
Raj wrote:
>
>
>>What does "df /tmp" shows?
>>
>>
>>
>>
>
>/dev/hda3 18141816 6219444 11000808 37% /
>
>/Raj
>
>
>
>>Thanks,
>>Jeff
>>[ jchua@fedex.com ]
>>
>>On Fri, 20 Feb 2004, Raj wrote:
>>
>>
>>
>>>Included the subject line now. i apologise.
>>>
>>>/Raj
>>>
>>>Life is the art of drawing sufficient conclusions from insufficient
>>>premises.
>>>
>>>
>>>On Fri, 20 Feb 2004, Raj wrote:
>>>
>>>
>>>
>>>>Hi,
>>>>
>>>>I am facing a weird problem with gcc 3.2.2 on RedHat 9.0 machine running
>>>>vanilla 2.6.3.Glibc 2.3.2.
>>>>
>>>>gcc fails to compile c programs. More specifically it fails during the
>>>>assembler phase. I boot back 2.6.2 and things work fine. Below are the
>>>>error messages.
>>>>
>>>>----start-----
>>>>/tmp/ccfRiElp.o: File truncated
>>>>/tmp/ccNO4FCk.s: Assembler messages:
>>>>/tmp/ccNO4FCk.s:23: FATAL: Can't write /tmp/ccfRiElp.o: File truncated
>>>>---end------
>>>>The source is a simple program which just has a printf.
>>>>
>>>>I am attaching the strace output when ran on 2.6.3. If you need
>>>>strace output of 2.6.2. pls let me know.
>>>>
>>>>/Raj
>>>>
>>>>Life is the art of drawing sufficient conclusions from insufficient
>>>>premises.
>>>>
>>>>
>>>>
>>>-
>>>To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
>>>the body of a message to majordomo@vger.kernel.org
>>>More majordomo info at http://vger.kernel.org/majordomo-info.html
>>>Please read the FAQ at http://www.tux.org/lkml/
>>>
>>>
>>>
>-
>To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
>the body of a message to majordomo@vger.kernel.org
>More majordomo info at http://vger.kernel.org/majordomo-info.html
>Please read the FAQ at http://www.tux.org/lkml/
>
>
>
prev parent reply other threads:[~2004-02-20 11:59 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-02-20 8:42 Raj
2004-02-20 8:59 ` Gcc problems on linux-2.6.3 Raj
2004-02-20 9:06 ` Jeff Chua
2004-02-20 9:11 ` Raj
2004-02-20 12:01 ` Raj [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=4035F71D.7080306@toughguy.net \
--to=obelix123@toughguy.net \
--cc=jeffchua@silk.corp.fedex.com \
--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