As an ocaml lib, ocaml-sqlite3 should have a .cmxs Reproducible: Always
Created attachment 316995 [details, diff] ocaml-sqlite3.patch
Comment on attachment 316995 [details, diff] ocaml-sqlite3.patch that patch does not change anything on the installed package so is certainly wrong. anyway, imho, installing a new file is something that should be sent upstream first.
Created attachment 317260 [details, diff] ocaml-sqlite3-1.6.1-cmxs.patch
Created attachment 317262 [details, diff] ocaml-sqlite3-1.6.1.ebuild.patch
I'm sorry, I've missed it. I had not tested this patch. These patchs are tested. BTW: I will send an upstream patch. But for the moment can you apply these patchs ?
what does need it ?
What ? What are you talking about ? The patchs or the upstream team ?
the cmxs :=)
You want to know which apps requires the cmxs ? It is used by any applications that is compiled natively with shared lib instead of static one. See: http://alain.frisch.fr/natdynlink.html for more informations. For instance, it's require by www-servers/ocsigen and www-servers/ocsigenserver when launching the server with the sqlite plugin.
so they require anyone wanting sqlite in ocsigen to use a patched version of ocaml-sqlite3 ? that sounds weird to me, could you please check with both upstreams ?
moreover, does your patch respect this (from your link): The new ocamlopt option -dlcode must be used when compiling a unit so that it can be put into a plugin. It can still be linked statically. Currently, -dlcode is only necessary for the Linux AMD64 port, but it is a good idea to always use it. There is theoretically a chance that -dlcode degrades performances, but it has never never been observed in practice. ?
(In reply to comment #11) > moreover, does your patch respect this (from your link): > > The new ocamlopt option -dlcode must be used when compiling a unit so that > it can be put into a plugin. It can still be linked statically. Currently, > -dlcode is only necessary for the Linux AMD64 port, but it is a good idea to > always use it. There is theoretically a chance that -dlcode degrades > performances, but it has never never been observed in practice. > > > ? scratch that, it is the default now (-nodynlink disables it)
(In reply to comment #10) > so they require anyone wanting sqlite in ocsigen to use a patched version of > ocaml-sqlite3 ? that sounds weird to me, could you please check with both > upstreams ? https://bitbucket.org/mmottl/sqlite3-ocaml/issue/1/sqlite3cmxs-is-not-generated
All other distros include the .cmxs. For instance: http://packages.debian.org/sid/i386/libsqlite3-ocaml/filelist You can see: /usr/lib/ocaml/sqlite3/sqlite3.cmxs
because they patched it locally... i dont want to add a new abi without upstream doing it also for exactly this reason: developers then tend to think they can expect it without realizing this has been added by their distribution. we shouldnt mimic debian's bad practices.
(In reply to comment #15) > because they patched it locally... > > i dont want to add a new abi without upstream doing it also for exactly this > reason: developers then tend to think they can expect it without realizing > this has been added by their distribution. we shouldnt mimic debian's bad > practices. Ok, so you deprive the library users from all they can expect. What's the problem ? The developer is aware of it. Why not just apply this patch and send the patch upstream after, like I did ?
fixed by bumping to 2.0.1
