Sqlite building failure using rtems-source-builder

Joel Sherrill joel at rtems.org
Tue Mar 26 22:06:32 UTC 2019

I think the problem is in this command.

../source-builder/sb-set-builder --log=log_sqlite.txt
--with-tools=/opt/rtems5.0-arm-19q1 --target=realview_pbx_a9_qemu
--host=arm-rtems5.0 databases/sqlite


../source-builder/sb-set-builder --log=log_sis_net_snmp \
    --prefix=$HOME/development/rtems/bsps/4.11 \
    --with-tools=$HOME/development/rtems/4.11 \
    --host=sparc-rtems4.11 --with-rtems-bsp=erc32 4.11/net-mgmt/net-snmp

By specifying host and target, it looks like you are doing a Canadian

Hopefully Chris can pop up and verify the command. Offhand, I am not sure
if the command in the documentation is correct.


On Tue, Mar 26, 2019 at 9:25 AM Jonathan Brandmeyer <
jbrandmeyer at planetiq.com> wrote:

> My team hasn't gotten to the stage of actually using SQLite in the
> RTEMS environment yet, but it builds just fine.  We don't use
> rtems-source-builder to do it.  We are just using the latest stable
> amalgamation release, supplied by sqlite.org.  We build it with the
> same options that the configure script normally uses to build a .so on
> Linux, except that we also specify -DSQLITE_OMIT_LOAD_EXTENSION.  I've
> seen some documentation to the effect that rtems actually does support
> dlopen/dlsym, but we haven't tried it and we don't need it for our
> mission.
> If I understand correctly, the only conflicts with RTEMS should be
> SQLIte's dependency on mmap.  RTEMS does not provide virtual memory at
> all, so mmap and kin are only stub functions that return an error.
> The SQLite3 documentation does describe how to configure the
> write-ahead log (WAL) in such a way that it should not rely on mmap at
> runtime, though.
> Hope that helps,
> --
> Jonathan Brandmeyer
> _______________________________________________
> users mailing list
> users at rtems.org
> http://lists.rtems.org/mailman/listinfo/users
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.rtems.org/pipermail/users/attachments/20190326/ea6252c4/attachment-0002.html>

More information about the users mailing list