From: GeunSik Lim <leemgs1@gmail.com>
To: debian developer <debiandev@gmail.com>
Cc: linux kernel <kernelnewbies@nl.linux.org>,
LKML <linux-kernel@vger.kernel.org>
Subject: Re: Unable to compile 2.6.30-rc7 on RHEL 4 - GCC 3.4.6
Date: Tue, 26 May 2009 16:26:56 +0900 [thread overview]
Message-ID: <49b7c2350905260026h95a229bse4b1f253601a40c8@mail.gmail.com> (raw)
In-Reply-To: <f24d23310905252256h74d609d9l7e23b1cdc0a240c6@mail.gmail.com>
On Tue, May 26, 2009 at 2:56 PM, debian developer <debiandev@gmail.com> wrote:
> On Tue, May 26, 2009 at 3:15 AM, GeunSik Lim <leemgs1@gmail.com> wrote:
>> Hi,
>>
>> If you keep gcc 3.X.X to compile recent kernel source contiunally,
>> You will meet another problems again.
>>
>
> OK, so 3.x.x is officially not supposed to be used for compilation?
It not means that gcc 3.x.x don't support normal compilation of recent
kernel source officially. Below some cases is about gcc 3.x.x.
http://kerneltrap.org/mailarchive/linux-kernel/2008/1/8/547730
https://launchpad.net/ubuntu/hardy/+source/linux/2.6.24-23.48
https://bugzilla.redhat.com/show_bug.cgi?id=488991
>
>
and, I've mistyped a word. I figured out typo thanks to Martin.
X) http://linuxdistrowatch.com
O) http://distrowatch.com/
--
Regards,
GeunSik Lim
--
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/
next prev parent reply other threads:[~2009-05-26 7:27 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-05-25 16:56 debian developer
2009-05-25 21:17 ` Simon König
2009-05-26 16:59 ` Stefan Richter
2009-05-25 21:45 ` GeunSik Lim
2009-05-26 5:56 ` debian developer
2009-05-26 7:26 ` GeunSik Lim [this message]
2009-05-26 7:41 ` Mikael Pettersson
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=49b7c2350905260026h95a229bse4b1f253601a40c8@mail.gmail.com \
--to=leemgs1@gmail.com \
--cc=debiandev@gmail.com \
--cc=kernelnewbies@nl.linux.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
all inboxes | Powered by JetHome®