[U-Boot-Users] Compile mpc8260 in u-boot

[U-Boot-Users] Compile mpc8260 in u-boot

[xyyiezi]

Dear sir:        I'll compile the u-boot and I will configure it to mpc8260ads.But I use the command "$make distclean",then I put in "$make MPC8260ADS_config".It displayed "No rule to make target "MPC8260ADS_config".stop" after I had entered.The u-boot I used is the version u-boot 1.1.4,and the GNU compiling tools was DELK4.0.The GNU path is localhome/sm8260/eldk,and the path to u-boot is localhome/sm8260/SVT/sm8260/SWDV/u-boot.I had compile it uder eldk.     I had modefied the makefile before I compiled it.First,I modefied it to "cross_compile=ppc_6xx" in red hat linux.I compiled it and I failed.It diaplay "No rule to make target "MPC8260ADS_config".stop".Secondly,I modefied it to "powerpc-linux-mpc8260",and the same thing was happend.     I don't kown what the matter is.And I hope to earn your help.     Thank you very much!                                                       Yours xyyiezi   
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.denx.de/pipermail/u-boot/attachments/20070719/157844ee/attachment.htm 

[U-Boot-Users] Compile mpc8260 in u-boot

[Jerry Van Baren]

xyyiezi wrote:
> Dear sir:
>  
>        I'll compile the u-boot and I will configure it to mpc8260ads.But 
> I use the command "$make distclean",then I put in "$make 
> MPC8260ADS_config".It displayed "No rule to make target 
> "MPC8260ADS_config".stop" after I had entered.The u-boot I used is the 
> version u-boot 1.1.4,and the GNU compiling tools was DELK4.0.The GNU 
> path is localhome/sm8260/eldk,and the path to u-boot is 
> localhome/sm8260/SVT/sm8260/SWDV/u-boot.I had compile it uder eldk.
>      I had modefied the makefile before I compiled it.First,I modefied 
> it to "cross_compile=ppc_6xx" in red hat linux.I compiled it and I 
> failed.It diaplay "No rule to make target 
> "MPC8260ADS_config".stop".Secondly,I modefied it to 
> "powerpc-linux-mpc8260",and the same thing was happend.
>      I don't kown what the matter is.And I hope to earn your help.
>      Thank you very much!
>  
>                                                       Yours xyyiezi

Dear xyyiezi,

Off topic:
----------
* Please send in plain text, not HTML.
* My company has blackballed 163.com due to malicious content on that 
site so I cannot reply to you directly.  You might consider using a 
different email service (gmail, for instance).

On topic:
---------
I'm guessing you don't have your PATH set up correctly.  You should 
export a symbol for your cross compiler location and prefix rather than 
modifying the makefile.  The following is what I use:

export PATH=$PATH:/opt/eldk/usr/bin/
export CROSS_COMPILE=powerpc-linux-
export ARCH=ppc

After doing this, make will invoke the proper cross compiler.  Obviously,
1) Your configuration may be different
2) If you put the above in a script file, you must use the bash command 
"source" to run it in your current shell.  If you type the script file 
at the command line, it will run in a spawned shell and the exported 
symbols will be gone when the spawned shell exists (not what you want!).

Best regards,
gvb

[U-Boot-Users] Compile mpc8260 in u-boot

[Wolfgang Denk]

Dear Jerry,

in message <469F6B47.5060400@smiths-aerospace.com> you wrote:
> 
> I'm guessing you don't have your PATH set up correctly.  You should 
> export a symbol for your cross compiler location and prefix rather than 
> modifying the makefile.  The following is what I use:
> 
> export PATH=$PATH:/opt/eldk/usr/bin/
> export CROSS_COMPILE=powerpc-linux-
> export ARCH=ppc

I would like to point out that this NOT a legal way to run the ELDK.
For allowed settings of the CROSS_COMPILE variable please see
the table at http://www.denx.de/wiki/view/DULG/ELDKUsage

Other settings are NOT allowed and lead to undefined behaviour.

For example, your mode of usage does not work at all even for trivial
user space applications:

-> cat h.c
#include <stdio.h>
int main (int argc, char *argv[])
{
        printf ("hello world\n");
        return (0);
}
-> export CROSS_COMPILE=powerpc-linux-
-> powerpc-linux-gcc -c h.c
h.c:1:19: error: stdio.h: No such file or directory
h.c: In function 'main':
h.c:4: warning: incompatible implicit declaration of built-in function 'printf'


Please do NOT use the ELDK as above. It does NOT work as intended. If
it worked for you so far than you were just extremely lucky.

Please point people to the official documentation instead.

Best regards,

Wolfgang Denk

-- 
DENX Software Engineering GmbH,     MD: Wolfgang Denk & Detlev Zundel
HRB 165235 Munich, Office: Kirchenstr.5, D-82194 Groebenzell, Germany
Phone: (+49)-8142-66989-10 Fax: (+49)-8142-66989-80 Email: wd at denx.de
Everyting looks interesting until you do it. Then you find it's  just
another job.                     - Terry Pratchett, _Moving Pictures_

[U-Boot-Users] Compile mpc8260 in u-boot

[Jerry Van Baren]

Wolfgang Denk wrote:
> Dear Jerry,
> 
> in message <469F6B47.5060400@smiths-aerospace.com> you wrote:
>> I'm guessing you don't have your PATH set up correctly.  You should 
>> export a symbol for your cross compiler location and prefix rather than 
>> modifying the makefile.  The following is what I use:
>>
>> export PATH=$PATH:/opt/eldk/usr/bin/
>> export CROSS_COMPILE=powerpc-linux-
>> export ARCH=ppc
> 
> I would like to point out that this NOT a legal way to run the ELDK.
> For allowed settings of the CROSS_COMPILE variable please see
> the table at http://www.denx.de/wiki/view/DULG/ELDKUsage
> 
> Other settings are NOT allowed and lead to undefined behaviour.

[snip]

> Please do NOT use the ELDK as above. It does NOT work as intended. If
> it worked for you so far than you were just extremely lucky.
> 
> Please point people to the official documentation instead.
> 
> Best regards,
> Wolfgang Denk

Yup, that cluestick is vaguely familiar, I'm pretty sure you hit me with 
it before.

Sorry about that...
gvb