[Buildroot] Analysis of build failures

Gustavo Zacarias gustavo at zacarias.com.ar
Mon Nov 11 09:30:00 UTC 2013


On 11/11/2013 09:26 AM, Fatih Aşıcı wrote:

> Probably the following change will fix it:
> 
> --- a/src/3rdparty/sqlite/sqlite3.c
> +++ b/src/3rdparty/sqlite/sqlite3.c
> @@ -22938,7 +22938,8 @@ SQLITE_PRIVATE const char *sqlite3OpcodeName(int i){
>  /* Use posix_fallocate() if it is available
>  */
>  #if !defined(HAVE_POSIX_FALLOCATE) \
> -      && (_XOPEN_SOURCE >= 600 || _POSIX_C_SOURCE >= 200112L)
> +      && (_XOPEN_SOURCE >= 600 || _POSIX_C_SOURCE >= 200112L) \
> +      && !defined(__UCLIBC__)
>  # define HAVE_POSIX_FALLOCATE 1
>  #endif
>  
> 
> 
> sqlite3's own build system (which is not available in qt) checks if 
> posix_fallocate() is available. I wonder if there is a special reason for 
> providing an option to use the built-in sqlite.

There was a bug in sqlite 3.7.17 with this, see
http://git.buildroot.net/buildroot/commit/package/sqlite?id=316f991729c423c9a49a955d3747ff31ad7a0068
It's fixed now, but a similar solution might be appropiate.
Newer uClibc versions might have posix_fallocate so excluding uClibc
might not be appropiate in the future.
Regards.



More information about the buildroot mailing list