From: Dan Kegel <dank@kegel.com>
To: Jacky Lam <jackylam@astri.org>
Cc: linuxppc-embedded@lists.linuxppc.org
Subject: Re: Queston about Walnut
Date: Fri, 03 Oct 2003 09:10:26 -0700 [thread overview]
Message-ID: <3F7D9F72.9020700@kegel.com> (raw)
In-Reply-To: <00df01c38992$6d179b40$2803050a@JackyLam>
Jacky Lam wrote:
> Does anyone still working on Walnut platform and successfully boot up
> 2.4 kernel on that? If no, could someone remember what is the last known
> working toolchain and kernel on Walnut?
We used 2.4.17 from linuxppc_2_4_devel.
> I use toolchain gcc 3.2.3, glibc 2.2.5 because I have some trouble to
> compile to newest one (it requests my host gcc >=3.1). Is this related? If
> yes, I would tried to reinstall my RedHat to newer version, but it would be
> painful.....
Why painful? It's as easy as this:
----------
wget ftp://ftp.gnu.org/gnu/gcc/gcc-3.3.1.tar.gz
tar -xzvf gcc-3.3.1.tar.gz
mkdir build-gcc
cd build-gcc
../gcc-3.3.1/configure --prefix=/usr/local/gcc-3.3.1 --enable-languages=c,c++
make
sudo make install
----------
Then put /usr/local/gcc-3.3.1/bin in your PATH before anything else, and you're done.
BTW here's the (awful) script I used to grab the kernel. (It reveals my
total lack of knowledge of bitkeeper; I think 'bk export' is preferred
to my clumsy removal of CVS directories.)
#!/bin/sh
if [ -z $1 ]; then
echo "Usage: `basename $0` TAG"
echo "Example: `basename $0` v2.4.18"
echo "Purpose: fetch a kernel source tarball from the linuxppc_2_4_devel tree"
exit 1
fi
set -x -e
rm -rf linux linuxppc_2_4_devel-$1 || /bin/true
# Download bk from http://www.bitkeeper.com
bk clone -r$1 bk://ppc.bkserver.net/linuxppc_2_4_devel linuxppc_2_4_devel-$1
cd linuxppc_2_4_devel-$1
find . -type d -exec bk get {} \;
# Hey! nonxargs version fails with 'find: no such file foo/SCCS' after deleting foo/SCCS!
# Bug in gnu find 4.1.7? Or in kernel 2.4.18? Who knows...
#find . -name SCCS -exec rm {} \;
find . -name SCCS -print | xargs rm -rf
rm -rf RESYNC/
rm -rf PENDING/
rm -rf BitKeeper/
rm -f ChangeSet
cd ..
mv linuxppc_2_4_devel-$1 linux
--
Dan Kegel
http://www.kegel.com
http://counter.li.org/cgi-bin/runscript/display-person.cgi?user=78045
** Sent via the linuxppc-embedded mail list. See http://lists.linuxppc.org/
next prev parent reply other threads:[~2003-10-03 16:10 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <000e01c388dc$eb525510$0202a8c0@homevl9biy3v7e>
2003-10-02 12:17 ` Queston about Walnut Wolfgang Denk
2003-10-03 1:18 ` Jacky Lam
[not found] ` <3F7D3238.2090400@bluewin.ch>
2003-10-03 9:40 ` Jacky Lam
2003-10-03 15:07 ` Matt Porter
2003-10-03 16:34 ` Jacky Lam
2003-10-04 16:07 ` Matt Porter
2003-10-03 16:10 ` Dan Kegel [this message]
2003-10-03 16:45 ` Jacky Lam
2003-10-03 17:31 ` Dan Kegel
[not found] ` <20031003151729.GC21468@ip68-0-152-218.tc.ph.cox.net>
2003-10-03 23:36 ` Kernel versions Gary Thomas
2003-10-07 13:37 ` Tom Rini
2003-10-03 4:11 ` Queston about Walnut Jacky Lam
2003-10-03 7:44 ` Jacky Lam
2003-10-03 13:51 ARIBAUD Albert
-- strict thread matches above, loose matches on Subject: below --
2003-10-03 7:57 ARIBAUD Albert
2003-10-03 8:26 ` Jacky Lam
2003-10-02 9:17 Jacky Lam
2003-10-02 10:13 ` Wolfgang Denk
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=3F7D9F72.9020700@kegel.com \
--to=dank@kegel.com \
--cc=jackylam@astri.org \
--cc=linuxppc-embedded@lists.linuxppc.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.