From: Matthias Fuchs <matthias.fuchs@esd-electronics.com>
To: u-boot@lists.denx.de
Subject: [U-Boot-Users] 1.3.3-rc2 - release status
Date: Thu, 1 May 2008 09:46:37 +0200 [thread overview]
Message-ID: <200805010946.37958.matthias.fuchs@esd-electronics.com> (raw)
In-Reply-To: <20080430074920.E358324681@gemini.denx.de>
On Wednesday 30 April 2008 09:49:20 Wolfgang Denk wrote:
> In message <200804300936.47258.matthias.fuchs@esd-electronics.com> you
wrote:
> > I noticed some warnings when compiling recent U-Boot source for some 4xx
> > bo> ards with gcc 4.0.0 or 4.2.2. Perhaps somebody has a clue on how to
> > get rid of t> hese:
>
> That's your host GCC. WHich distro is this?
Yes you are right.
It's Debian Etch.
matthias at debby:~$ gcc -v
Using built-in specs.
Target: i486-linux-gnu
Configured
with: ../src/configure -v --enable-languages=c,c++,fortran,objc,obj-c++,treelang --prefix=/usr --enable-shared --with-system-zlib --libexecdir=/usr/lib --without-included-gettext --enable-threads=posix --enable-nls --program-suffix=-4.1 --enable-__cxa_atexit --enable-clocale=gnu --enable-libstdcxx-debug --enable-mpfr --with-tune=i686 --enable-checking=release
i486-linux-gnu
Thread model: posix
gcc version 4.1.2 20061115 (prerelease) (Debian 4.1.1-21
Matthias
>
> I didn't see such warnigns yet...
>
> > gcc -g -Wall -pedantic -idirafter
> > /data/home/matthias/git/u-boot/u-boot/inc> lude -idirafter
> > /data/home/matthias/git/u-boot/u-boot/include2 -idirafter />
> > data/home/matthias/git/u-boot/u-boot/include -DTEXT_BASE=0xFFFA0000
> > -DUSE> _HOSTCC -O -c -o md5.o md5.c md5.c: In function ???MD5Update???:
> > md5.c:95: warning: implicit declaration of function ???memmove??> ?
> > md5.c:95: warning: incompatible implicit declaration of built-in function
> > > ???memmove??? md5.c:98: warning: incompatible implicit declaration of
> > built-in function > ???memmove??? md5.c:107: warning: incompatible
> > implicit declaration of built-in function > ???memmove??? md5.c:116:
> > warning: incompatible implicit declaration of built-in function >
> > ???memmove???
>
> I smell some header file incompatibitilies - eventually this is a
> distro issue.
>
> Best regards,
>
> Wolfgang Denk
next prev parent reply other threads:[~2008-05-01 7:46 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-04-29 21:49 [U-Boot-Users] 1.3.3-rc2 - release status Wolfgang Denk
2008-04-30 7:36 ` Matthias Fuchs
2008-04-30 7:49 ` Wolfgang Denk
2008-05-01 7:46 ` Matthias Fuchs [this message]
2008-04-30 20:29 ` [U-Boot-Users] [PATCH] env_nand: fix incompatible pointer type on nand_{read, write} Jean-Christophe PLAGNIOL-VILLARD
2008-04-30 20:38 ` [U-Boot-Users] [PATCH] cmd_nand: fix warning: str2long ncompatible pointer type Jean-Christophe PLAGNIOL-VILLARD
2008-04-30 20:59 ` Wolfgang Denk
2008-05-01 0:13 ` [U-Boot-Users] [PATCH 0/1] pxa: fix pcmcia operation on 'i' may be undefined Jean-Christophe PLAGNIOL-VILLARD
2008-05-01 0:13 ` [U-Boot-Users] [PATCH 1/1] pxa: fix previous definition on cpu init Jean-Christophe PLAGNIOL-VILLARD
2008-05-03 18:56 ` Wolfgang Denk
2008-05-03 18:55 ` [U-Boot-Users] [PATCH 0/1] pxa: fix pcmcia operation on 'i' may be undefined Wolfgang Denk
2008-04-30 20:56 ` [U-Boot-Users] [PATCH] env_nand: fix incompatible pointer type on nand_{read, write} 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=200805010946.37958.matthias.fuchs@esd-electronics.com \
--to=matthias.fuchs@esd-electronics.com \
--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