[U-Boot-Users] Those hello_world compilation problems
Folks,
I did some digging on our toolchain here on our new Yellowdog 4.0 installed machines. They have a 3.3.2 compiler on them by default, apparently.
As someone else discerned, that cause an issue with the dummy() function being static in the stubs.o file for the examples directory.
I've found that all appears to be better if the test in the example/stubs.c file is changed from:
#if GCC_VERSION < 3004 to #if GCC_VERSION < 3003
(BTW, the GCC_VERSION symbol, google revealed, comes from ansidecl.h. Oh yeah.)
I'm not sure of the generality of this fix, so I am reluctant to submit a direct patch for it. Perhaps someone more familiar with the details of either the YDL 4.0 or GCC 3.3 vs 3.4 releases can speak authoritatively on this issue.
HTH, jdl
In message 1097785745.14656.73.camel@cashmere.sps.mot.com you wrote:
I did some digging on our toolchain here on our new Yellowdog 4.0 installed machines. They have a 3.3.2 compiler on them by default, apparently.
As someone else discerned, that cause an issue with the dummy() function being static in the stubs.o file for the examples directory.
I've found that all appears to be better if the test in the example/stubs.c file is changed from:
#if GCC_VERSION < 3004to #if GCC_VERSION < 3003
(BTW, the GCC_VERSION symbol, google revealed, comes from ansidecl.h. Oh yeah.)
For which architecture is this?
ELDK 3.1 uses GCC-3.3.3, and I didn't see such problems yet.
I'm not sure of the generality of this fix, so I am reluctant to submit a direct patch for it. Perhaps someone more familiar with the details of either the YDL 4.0 or GCC 3.3 vs 3.4 releases can speak authoritatively on this issue.
At the moment I don't see the need to change anything for GCC-3.3.x.
Best regards,
Wolfgang Denk
Wolfgang,
Do you mind posting what the output off 'gcc -v' is with the gcc-3.3.3 in ELDK 3.1.
The YDL4 compiler is actually gcc-3.3.3 but compiled to handle both PPC64 & PPC32.
thanks
- kumar
On Oct 16, 2004, at 3:42 AM, Wolfgang Denk wrote:
In message 1097785745.14656.73.camel@cashmere.sps.mot.com you wrote:
I did some digging on our toolchain here on our new Yellowdog 4.0 installed machines. They have a 3.3.2 compiler on them by default, apparently.
As someone else discerned, that cause an issue with the dummy() function being static in the stubs.o file for the examples directory.
I've found that all appears to be better if the test in the example/stubs.c file is changed from:
#if GCC_VERSION < 3004 to #if GCC_VERSION < 3003
(BTW, the GCC_VERSION symbol, google revealed, comes from ansidecl.h. Oh yeah.)
For which architecture is this?
ELDK 3.1 uses GCC-3.3.3, and I didn't see such problems yet.
I'm not sure of the generality of this fix, so I am reluctant to submit a direct patch for it. Perhaps someone more familiar with the details of either the YDL 4.0 or GCC 3.3 vs 3.4 releases can speak authoritatively on this issue.
At the moment I don't see the need to change anything for GCC-3.3.x.
Best regards,
Wolfgang Denk
-- Software Engineering: Embedded and Realtime Systems, Embedded Linux Phone: (+49)-8142-66989-10 Fax: (+49)-8142-66989-80 Email: wd@denx.de A committee is a group that keeps the minutes and loses hours. -- Milton Berle
This SF.net email is sponsored by: IT Product Guide on ITManagersJournal Use IT products in your business? Tell us what you think of them. Give us Your Opinions, Get Free ThinkGeek Gift Certificates! Click to find out more http://productguide.itmanagersjournal.com/guidepromo.tmpl _______________________________________________ U-Boot-Users mailing list U-Boot-Users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/u-boot-users
Dear Kumar,
in message 0CBEE6E4-2053-11D9-8306-000393DBC2E8@freescale.com you wrote:
Do you mind posting what the output off 'gcc -v' is with the gcc-3.3.3 in ELDK 3.1.
-> ppc_8xx-gcc -v Reading specs from /opt/eldk-3.1/usr/bin/../lib/gcc-lib/ppc-linux/3.3.3/specs Configured with: ../configure --prefix=/usr --mandir=/usr/share/man --infodir=/usr/share/info --enable-shared --enable-threads=posix --disable-checking --with-system-zlib --enable-__cxa_atexit --with-newlib --enable-languages=c,c++ --disable-libgcj --host=i386-redhat-linux --target=ppc-linux Thread model: posix gcc version 3.3.3 (DENX ELDK 3.1 3.3.3-7)
The YDL4 compiler is actually gcc-3.3.3 but compiled to handle both PPC64 & PPC32.
This alone probably should not have such an effect?
Best regards,
Wolfgang Denk
participants (3)
-
Jon Loeliger -
Kumar Gala -
Wolfgang Denk