On Tue, 6 Aug 2019 at 21:38, Jason Wessel
wrote:
>
> Sqlite3 doesn't have a an explicit disable. It has the typical autoconf
> check for a header/library. From configure.ac:
>
>
> AC_CHECK_HEADERS(zlib.h,[
> AC_SEARCH_LIBS(deflate,z,[BUILD_CFLAGS="$BUILD_CFLAGS
> -DSQLITE_HAVE_ZLIB"])
> ])
>
On 8/6/19 2:17 PM, Alexander Kanavin wrote:
On Tue, 6 Aug 2019 at 20:52, Jason Wessel mailto:jason.wes...@windriver.com>> wrote:
Just to follow up to be very specific about how I deleted files, you can
see the identical failure with:
sudo yum install -y zlib-devel
rm -rf tmp
On Tue, 6 Aug 2019 at 20:52, Jason Wessel
wrote:
>
> Just to follow up to be very specific about how I deleted files, you can
> see the identical failure with:
>
> sudo yum install -y zlib-devel
> rm -rf tmp
>
> bitbake -c cleansstate sqlite3-native
>
> bitbake sqlite3-native
>
> sudo yum remove
On 8/6/19 1:36 PM, Jason Wessel wrote:
On 8/6/19 12:55 PM, Alexander Kanavin wrote:
On Tue, 6 Aug 2019 at 19:31, Jason Wessel mailto:jason.wes...@windriver.com>> wrote:
The build of sqlite3-native is not fully deterministic. There is some
corner case as shown with the recent pseudo
On 8/6/19 12:55 PM, Alexander Kanavin wrote:
On Tue, 6 Aug 2019 at 19:31, Jason Wessel mailto:jason.wes...@windriver.com>> wrote:
The build of sqlite3-native is not fully deterministic. There is some
corner case as shown with the recent pseudo commit where the sqlite3
will
On Tue, 6 Aug 2019 at 19:31, Jason Wessel
wrote:
> The build of sqlite3-native is not fully deterministic. There is some
> corner case as shown with the recent pseudo commit where the sqlite3
> will sometimes link against zlib. It is possible that in a build with
> sstate that since the zlib
The build of sqlite3-native is not fully deterministic. There is some
corner case as shown with the recent pseudo commit where the sqlite3
will sometimes link against zlib. It is possible that in a build with
sstate that since the zlib is not listed, that pseudo-native will fail
to build because
