From: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
To: buildroot@busybox.net
Subject: [Buildroot] simple xtensa build fails
Date: Mon, 2 Jun 2014 23:00:10 +0200 [thread overview]
Message-ID: <20140602230010.591ed0c4@free-electrons.com> (raw)
In-Reply-To: <20140602064030.GB4473@tarshish>
Dear Baruch Siach,
On Mon, 2 Jun 2014 09:40:30 +0300, Baruch Siach wrote:
> Hi Waldemar,
>
> On Mon, Jun 02, 2014 at 08:23:54AM +0200, Waldemar Brodkorb wrote:
> > a simple Xtensa build fails:
> > CC libc/sysdeps/linux/common/posix_fadvise.os
> > libc/sysdeps/linux/common/posix_fadvise.c:26:29: error: unknown type
> > name 'off64_t'
> > libc/sysdeps/linux/common/posix_fadvise.c:26:45: error: unknown type
> > name 'off64_t'
> > libc/sysdeps/linux/common/posix_fadvise.c: In function
> > 'posix_fadvise':
> > libc/sysdeps/linux/common/posix_fadvise.c:32:2: warning: implicit
> > declaration of function 'posix_fadvise64'
> > [-Wimplicit-function-declaration]
> > make[1]: *** [libc/sysdeps/linux/common/posix_fadvise.os] Error 1
> > make[1]: Leaving directory
> > `/home/wbx/br/output/build/uclibc-7bf35c8b7d4a1f97174eb49f47f33946b282114c'
> > make: ***
> > [/home/wbx/br/output/build/uclibc-7bf35c8b7d4a1f97174eb49f47f33946b282114c/.stamp_built]
> > Error 2
>
> Snapshot uClibc build without LFS is currently broken. See
> http://article.gmane.org/gmane.comp.lib.uclibc.general/23714 for a fix.
Should we integrate this patch in our Xtensa and ARC uClibc patch
series?
Thanks,
Thomas
--
Thomas Petazzoni, CTO, Free Electrons
Embedded Linux, Kernel and Android engineering
http://free-electrons.com
next prev parent reply other threads:[~2014-06-02 21:00 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-06-02 6:23 [Buildroot] simple xtensa build fails Waldemar Brodkorb
2014-06-02 6:40 ` Baruch Siach
2014-06-02 21:00 ` Thomas Petazzoni [this message]
2014-06-03 4:16 ` Baruch Siach
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=20140602230010.591ed0c4@free-electrons.com \
--to=thomas.petazzoni@free-electrons.com \
--cc=buildroot@busybox.net \
/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