From: Jorik Jonker <linux-mips@boeventronie.net>
To: linux-mips@linux-mips.org
Subject: Re: linux 2.4 and Indy
Date: Fri, 30 Jan 2004 22:01:27 +0100 [thread overview]
Message-ID: <20040130210127.GB19872@ballina> (raw)
In-Reply-To: <20040130204911.GA19872@ballina>
On Fri, Jan 30, 2004 at 09:49:11PM +0100, Jorik Jonker wrote:
> # cvs -z3 -d :pserver:cvs@ftp.linux-mips.org:/home/cvs co \
> -D '5 Dec 2003' \
> -r linux_2_4 linux
>
> I am not extremely confident about my CVS skills, but the fine manual tought
> me this. I even checked out kernels from June 4th 2003, without success. I am
> now trying February 4th 2003.
Without success again.. I am beginning to suspect that I am doing something
completely wrong. I must say I am building using a crosscompiler:
mips-linux-gcc (GCC) 3.2.3 20030221 (Debian prerelease), but.. I successfully
produced a working 2.4.16 and 2.4.17. I am now going to do a native '5
december' build, hoping that will solve the problems.
--
Jorik Jonker
http://boeventronie.net/
next prev parent reply other threads:[~2004-01-30 21:02 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-01-29 10:22 linux 2.4 and Indy Jorik Jonker
2004-01-29 10:40 ` Kumba
2004-01-30 10:59 ` Jorik Jonker
2004-01-30 11:12 ` Dominik 'Rathann' Mierzejewski
2004-01-30 20:49 ` Jorik Jonker
2004-01-30 21:01 ` Jorik Jonker [this message]
2004-01-31 3:04 ` Ralf Baechle
2004-01-31 14:10 ` Jorik Jonker
2004-02-01 4:52 ` R4600 V1.7 errata Ralf Baechle
2004-02-03 11:39 ` Ralf Baechle
2004-02-03 11:42 ` Dominik 'Rathann' Mierzejewski
2004-02-03 11:52 ` Ralf Baechle
2004-02-03 15:43 ` Maciej W. Rozycki
2004-02-03 16:12 ` Ralf Baechle
2004-02-03 16:20 ` Maciej W. Rozycki
2004-02-04 15:48 ` Dominik 'Rathann' Mierzejewski
2004-02-04 15:59 ` Pete Popov
2004-02-04 20:04 ` Ralf Baechle
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=20040130210127.GB19872@ballina \
--to=linux-mips@boeventronie.net \
--cc=linux-mips@linux-mips.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.