From: Joshua Kwan <joshk@ludicrus.ath.cx>
To: rodrigobaroni@yahoo.com.br
Cc: linux-kernel@vger.kernel.org
Subject: Re: kernel compile error
Date: Wed, 8 Jan 2003 18:48:14 -0800 [thread overview]
Message-ID: <20030108184814.72ee41eb.joshk@ludicrus.ath.cx> (raw)
In-Reply-To: <20030109021540.80049.qmail@web11105.mail.yahoo.com>
[-- Attachment #1: Type: text/plain, Size: 1094 bytes --]
Have you considered grabbing an official 2.4.18 source tree from
kernel.org and see if that works?
BTW, 2.4.20 is current, if you're going to get something might as well
get that...
Regards
Josh
Rabid cheeseburgers forced"Rodrigo F. Baroni"
<rodrigobaroni@yahoo.com.br> to write this on Wed, 8 Jan 2003
23:15:40-0300 (ART):
> Hello all,
>
>
> There is a good time that I have trying to compile
> a kernel in a pc 233 mhz (motherboard lmr 591 -
> chipset sis, all-on-board), and so the follow error
> below happen.
>
>
> Does anybody knows what is going on please ?!
> (it's a 2.4.18 kernel in a debian 3)
>
>
>
>
> Rodrigo F Baroni
> Computer Science Grad Student
>
> _____________________________________________________________________
> __ Busca Yahoo!
> O melhor lugar para encontrar tudo o que você procura na Internet
> http://br.busca.yahoo.com/
--
Joshua Kwan
joshk@mspencer.net
pgp public key at http://joshk.mspencer.net/pubkey_gpg.asc
It's hard to keep your shirt on when you're getting something off your
chest.
[-- Attachment #2: Type: application/pgp-signature, Size: 189 bytes --]
next prev parent reply other threads:[~2003-01-09 2:44 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-01-09 2:15 Rodrigo F. Baroni
2003-01-09 2:48 ` Joshua Kwan [this message]
2003-01-09 15:26 ` [SOLVED] " Rodrigo F. Baroni
-- strict thread matches above, loose matches on Subject: below --
2006-05-19 7:45 Kernel compile Error Penshoppe Estrada
2006-05-19 9:15 ` Adrian Bunk
2001-10-13 16:34 Kernel compile error Tobias Hahn
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=20030108184814.72ee41eb.joshk@ludicrus.ath.cx \
--to=joshk@ludicrus.ath.cx \
--cc=linux-kernel@vger.kernel.org \
--cc=rodrigobaroni@yahoo.com.br \
/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®