[OE-core] [PATCH] sqlite3: Always build sqlite3-native with zlib

Alexander Kanavin alex.kanavin at gmail.com
Tue Aug 6 19:17:35 UTC 2019


On Tue, 6 Aug 2019 at 20:52, Jason Wessel <jason.wessel at 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
>
> bitbake -c cleansstate sqlite3-native
>
> bitbake sqlite3-native
>
> sudo yum remove -y zlib-devel
>
> bitbake -c cleansstate pseudo-native
>
> bitbake pseudo-native
>
>
> I seriously doubt this is exactly what is going on on the host builder
> which failed.  More analysis would be needed as I explained earlier to draw
> a final conclusion.  Either way sqlite3-native should be configured to
> build consistently, which would prevent this kind of contamination.
>

This is not quite what I meant. I meant looking at the source code of
sqlite, and finding out how exactly it is looking for zlib, and where
things might go wrong (e.g. host contamination, or other possible causes of
non-determinism). There might be a configure switch to control that
behavior, or something similar that we can use to achieve deterministic
builds.

Alex
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.openembedded.org/pipermail/openembedded-core/attachments/20190806/16fff8fb/attachment.html>


More information about the Openembedded-core mailing list