From: Wolfgang Denk <wd@denx.de>
To: u-boot@lists.denx.de
Subject: [U-Boot-Users] Those hello_world compilation problems
Date: Sat, 16 Oct 2004 10:42:36 +0200 [thread overview]
Message-ID: <20041016084241.F34CCC1430@atlas.denx.de> (raw)
In-Reply-To: Your message of "Thu, 14 Oct 2004 15:29:05 CDT." <1097785745.14656.73.camel@cashmere.sps.mot.com>
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 at denx.de
A committee is a group that keeps the minutes and loses hours.
-- Milton Berle
next prev parent reply other threads:[~2004-10-16 8:42 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-10-14 20:29 [U-Boot-Users] Those hello_world compilation problems Jon Loeliger
2004-10-16 8:42 ` Wolfgang Denk [this message]
2004-10-17 15:41 ` Kumar Gala
2004-10-17 16:52 ` Wolfgang Denk
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20041016084241.F34CCC1430@atlas.denx.de \
--to=wd@denx.de \
--cc=u-boot@lists.denx.de \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox