Package Details: ocaml-sqlite3 4.1.3-1

Git Clone URL: (read-only)
Package Base: ocaml-sqlite3
Description: SQLite3 bindings for OCaml
Upstream URL:
Licenses: MIT
Submitter: ftrvxmtrx
Maintainer: oriba
Last Packager: oriba
Votes: 44
Popularity: 0.455286
First Submitted: 2010-12-30 01:31
Last Updated: 2017-07-13 01:59

Latest Comments

1 2 3 Next › Last »

david_rysk commented on 2018-07-08 20:36

It looks like a stable jbuilder is available in the main repos.

oriba commented on 2018-01-27 03:01

It looks like the installation-procedure of ocaml-sqlite3 has changed a lot. It looks like jbuilder is needed, which (the AUR-package) by itself is outdated and not even building in the current package). So, updating the ocaml-sqlite3 might need some time. BTW: anyone here who used jbuilder so far and coul give advice on installation?

radek_r commented on 2017-09-30 12:32

Please add achitecture "armv7h" to the PKGBUILD.

xiretza commented on 2017-01-28 12:22

Requires ocamlbuild as makedep.

oriba commented on 2015-12-15 18:02

Next OCaml-release will be in Jan. 2016, and some patches related to this or similar issues will be on board then.
Hopefully this will be fixed then...

layus commented on 2015-12-15 07:21

No idea really :-). I do not know how they did fix it.
As I said on the bugtracker [1], I recompiled ocaml with -fPIC which solved my problem. Maybe the correct solution would be to add -runtime-variant _pic to ocamlopt or ocamlfind (I'm guessing here...) ?
The last comment of the mantis [2] seems to me like the latter option is the right one. Any idea where to add -runtime-variant _pic to this package ?


PS: My system is up to date, and my ocaml version is indeed 4.02.3.

oriba commented on 2015-12-14 22:32

The caml-link says: fixed in 4.02.2+dev / +rc1.
Official ocaml in Arch is: 4.02.3.
Should be fixed there...?!
Do you have the current OCaml installed?

layus commented on 2015-12-14 13:01

This seems related to,
which in turns points to
Both issues are relevant. I will try to bix my build based on this.

oriba commented on 2015-12-14 11:57

I don't have such problems. It compiles without problems here.
Do you have a 32-bit system, or use 32-bit libraries?
"R_X86_64_32" seems to be related to 32/64-bit-issues.

layus commented on 2015-12-14 11:51

Nop, the same problem still occurs.
Any way I can help debugging ?