From: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
To: buildroot@busybox.net
Subject: [Buildroot] Analysis of build failures, december 26th
Date: Fri, 27 Dec 2013 14:33:26 +0100 [thread overview]
Message-ID: <20131227143326.0811a6af@skate> (raw)
In-Reply-To: <201312271531.46191.fatih.asici@gmail.com>
Dear Fatih A??c?,
On Fri, 27 Dec 2013 15:31:46 +0200, Fatih A??c? wrote:
> On Friday 27 December 2013 11:35:11 Thomas Petazzoni wrote:
> > > sh4 | qt5base-5.2.0 | NOK |
> > >http://autobuild.buildroot.net/results/a249b0cd5b20a2c3eee34b585cd58d4a03
> > >a9338e/
> >
> > ../../../3rdparty/sqlite/sqlite3.c:23535:42: error: 'posix_fallocate'
> > undeclared here (not in a function)
> >
> > I think we had this problem in the past. Note that the SH4 toolchain is
> > older than other toolchain (generated with Buildroot 2013.05, while
> > other toolchains are generated with Buildroot 2013.11-rc2).
> >
> > Fatih, any idea?
>
> posix_fallocate patch was removed while bumping to 5.2.0. Sent a patch to get
> it back.
Thanks. Is there a chance to get this patch upstream somehow?
Thanks!
Thomas
--
Thomas Petazzoni, CTO, Free Electrons
Embedded Linux, Kernel and Android engineering
http://free-electrons.com
next prev parent reply other threads:[~2013-12-27 13:33 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-12-27 7:30 [Buildroot] [autobuild.buildroot.net] Build results for 2013-12-26 Thomas Petazzoni
2013-12-27 9:35 ` [Buildroot] Analysis of build failures, december 26th Thomas Petazzoni
2013-12-27 10:01 ` Baruch Siach
2013-12-27 13:31 ` Fatih Aşıcı
2013-12-27 13:33 ` Thomas Petazzoni [this message]
2013-12-27 13:57 ` Fatih Aşıcı
2013-12-27 13:59 ` Thomas Petazzoni
2013-12-27 14:22 ` Fatih Aşıcı
2013-12-27 14:24 ` Thomas Petazzoni
2013-12-29 12:26 ` Baruch Siach
2013-12-29 12:58 ` Mischa Jonker
2013-12-29 17:06 ` Thomas Petazzoni
2013-12-30 8:12 ` Fatih Aşıcı
2013-12-30 9:40 ` Fatih Aşıcı
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=20131227143326.0811a6af@skate \
--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 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.