Hi Wolfgang,
What is the specific bug you intend to fix here? Using ppc_8xx-size in case CROSS_COMPILE is not set is not worse than using the native "size" command, it seems. Actually, given the fact that the majority supported of boards are PowerPC, it is right in most cases.
So why do you think it should be changed?
I think size utility do the same function as ppc_8xx-size. I tried 4 cross tools and the result is the same. (Logs are below) And in man page you can find: "size can automatically recognize many formats" in --target option.
From my point of view is size utility better than error message.
And I think that many developers use different cross tools than ppc_8xx-.
Best regards, Michal Simek
microblaze@monstr u-boot-microblaze]$ ./MAKEALL xupv2p Configuring for xupv2p board... ./MAKEALL: line 351: ppc_8xx-size: command not found
[microblaze@monstr u-boot-microblaze]$ ./MAKEALL xupv2p Configuring for xupv2p board... text data bss dec hex filename 89326 21479 214916 325721 4f859 ./u-boot
[microblaze@monstr u-boot-microblaze]$ size u-boot text data bss dec hex filename 89326 21479 214916 325721 4f859 u-boot
[microblaze@monstr u-boot-microblaze]$ microblaze-uclinux-size u-boot text data bss dec hex filename 89326 21479 214916 325721 4f859 u-boot
[microblaze@monstr u-boot-microblaze]$ powerpc-405-linux-gnu-size u-boot text data bss dec hex filename 89326 21479 214916 325721 4f859 u-boot [microblaze@monstr u-boot-microblaze]$
[microblaze@monstr bin]$ powerpc-linux-uclibc-size u-boot text data bss dec hex filename 89326 21479 214916 325721 4f859 u-boot [microblaze@monstr bin]$