From: Simon Glass <sjg@chromium.org>
To: u-boot@lists.denx.de
Subject: [U-Boot] [PATCH] fs: cbfs: Fix build of fs/cbfs/cbfs.c when building u-boot sandbox on x86 32-bit
Date: Fri, 17 Jun 2016 17:00:08 -0600 [thread overview]
Message-ID: <CAPnjgZ0N2yEVqnJg=RHd8ad-4it=d43sv+kXTvPNCDZ4PqDEOQ@mail.gmail.com> (raw)
In-Reply-To: <1466156737-6491-1-git-send-email-guillaume.gardet@free.fr>
On 17 June 2016 at 03:45, Guillaume GARDET <guillaume.gardet@free.fr> wrote:
> Fix the following build errors when building sandbox on x86 32-bit:
>
> In file included from fs/cbfs/cbfs.c:8:0:
> include/malloc.h:364:7: error: conflicting types for 'memset'
> void* memset(void*, int, size_t);
> ^
> In file included from include/compiler.h:123:0,
> from include/cbfs.h:10,
> from fs/cbfs/cbfs.c:7:
> include/linux/string.h:78:15: note: previous declaration of 'memset' was here
> extern void * memset(void *,int,__kernel_size_t);
> ^
> In file included from fs/cbfs/cbfs.c:8:0:
> include/malloc.h:365:7: error: conflicting types for 'memcpy'
> void* memcpy(void*, const void*, size_t);
> ^
> In file included from include/compiler.h:123:0,
> from include/cbfs.h:10,
> from fs/cbfs/cbfs.c:7:
> include/linux/string.h:81:15: note: previous declaration of 'memcpy' was here
> extern void * memcpy(void *,const void *,__kernel_size_t);
> ^
> scripts/Makefile.build:280: recipe for target 'fs/cbfs/cbfs.o' failed
>
>
> Signed-off-by: Guillaume GARDET <guillaume.gardet@free.fr>
> Cc: Tom Rini <trini@konsulko.com>
> Cc: Simon Glass <sjg@chromium.org>
>
> ---
> fs/cbfs/cbfs.c | 1 +
> 1 file changed, 1 insertion(+)
Reviewed-by: Simon Glass <sjg@chromium.org>
next prev parent reply other threads:[~2016-06-17 23:00 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-06-17 9:45 [U-Boot] [PATCH] fs: cbfs: Fix build of fs/cbfs/cbfs.c when building u-boot sandbox on x86 32-bit Guillaume GARDET
2016-06-17 23:00 ` Simon Glass [this message]
2016-06-19 14:12 ` Tom Rini
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='CAPnjgZ0N2yEVqnJg=RHd8ad-4it=d43sv+kXTvPNCDZ4PqDEOQ@mail.gmail.com' \
--to=sjg@chromium.org \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.