Hello Hugues;
When a tool chain is built, it is unlike other binaries because the tool
chain is built for a specific path. The tool chain that I built must run
from the /skiff/local directory. No other path will work. It was built in
/skiff/local to accommodate Georgia Tech University. If you go to
ftp.handhelds.org/pub/linux/arm/toolchain, then you will find a README file
with some install directions. Next week I plan to upgrade the toolchain with
a path of /usr/local and create a web page on http://handhelds.org with
instructions for building and installation.
I hope this helps. Please let me know how things turn out.
--George
George France, [EMAIL PROTECTED]
Cambridge Research Laboratory, Compaq Computer Corporation
One Cambridgecenter MS: CRL
Cambridge, MA 02142 USA
-----Original Message-----
From: Hugues Belanger [mailto:[EMAIL PROTECTED]]
Sent: Tuesday, June 27, 2000 9:05 PM
To: [EMAIL PROTECTED]
Subject: Help with toolchain
I need a little help getting started with my little project...
I'm planning to port LRP (linux router project) to my LART board and I
can't get even compile a kernel...
I've downloaded Compaq's arm toolchain ... and extracted it to
/data/lart/cross/bin ... (I don't have to instruction on how to set it
up so I'm going with Lart's setup)
I've added that to the path in .bash_profile...
I've download kernel 2.2.16-1 and I could find any arm patch for this
kernel, so I'm assuming it doesn't need any for ARM... Is that a bad
assumption ?
I applied all the LRP patches to the kernel tree...
and complied it for i486 (that worked great)...
I then changed the follwing in the top level Makefile:
ARCH := arm
CROSS_COMPILE = /data/lart/cross/bin/arm-linux-
I get : Makefile:249: *** target file `symlinks' has both : and ::
entries. Stop.
when I type make menuconfig
have you seen this before ?
Thanks
Hugues Belanger
unsubscribe: body of `unsubscribe linux-arm' to [EMAIL PROTECTED]
++ Please use [EMAIL PROTECTED] for ++
++ kernel-related discussions. ++
