
My experience with ELDK (either due to my 82xx target or my ignorance) is that the prefix is ppc-linux- rather than ppc-8xx. You can override this by creating and exporting the symbol CROSS_COMPILE. E.g., in bash run: $ export CROSS_COMPILE=ppc-linux- You can also edit the top level Makefile in u-boot to change the definion of CROSS_COMPILE to your favorite prefix to effect the same thing.
You will also need the tools (ppc-linux-gcc & co.) in your $PATH if it isn't already, most easily done in your .bashrc file. export PATH=$PATH:<ppc_tools_path>
gvb
-----Original Message----- From: u-boot-users-admin@lists.sourceforge.net [mailto:u-boot-users-admin@lists.sourceforge.net]On Behalf Of T Michael Turney Sent: Thursday, September 09, 2004 11:04 PM To: Wang, Chao (Charles); u-boot-users@lists.sourceforge.net Subject: RE: [U-Boot-Users] Where is the ppc-8xx-gcc
You need a cross-development toolchain. For the PPC, why not try ELDK 3.0? http://www.denx.de Cheers, T.mike
-----Original Message----- From: u-boot-users-admin@lists.sourceforge.net [mailto:u-boot-users-admin@lists.sourceforge.net]On Behalf
Of Wang, Chao
(Charles) Sent: Thursday, September 09, 2004 7:00 PM To: u-boot-users@lists.sourceforge.net Subject: [U-Boot-Users] Where is the ppc-8xx-gcc
When I tried to build the boot code, it came out that no
ppc-8xx-gcc was
found. Where can I get ppc-8xx-gcc?
****************************************** The following messages are brought to you by the Lawyers' League of IdioSpeak:
****************************************** The information contained in, or attached to, this e-mail, may contain confidential information and is intended solely for the use of the individual or entity to whom they are addressed and may be subject to legal privilege. If you have received this e-mail in error you should notify the sender immediately by reply e-mail, delete the message from your system and notify your system manager. Please do not copy it for any purpose, or disclose its contents to any other person. The views or opinions presented in this e-mail are solely those of the author and do not necessarily represent those of the company. The recipient should check this e-mail and any attachments for the presence of viruses. The company accepts no liability for any damage caused, directly or indirectly, by any virus transmitted in this email. ******************************************