From: Paul Snively <psnively@mac.com>
To: caml-list@inria.fr
Subject: [Caml-list] Oasis Bug?
Date: Mon, 28 Mar 2016 06:39:44 -0700 [thread overview]
Message-ID: <206FE738-9D7C-4739-A82B-643CFF82260B@mac.com> (raw)
[-- Attachment #1: Type: text/plain, Size: 890 bytes --]
Hi everyone,
I recently tried installing some packages in OPAM using the ocaml-4.02.3-musl-static compiler. One of them failed because it includes some C stubs, and the build script, which was generated by Oasis, blithely assumed dynlink support. After a bit of digging, I found this <https://github.com/ocaml/oasis/blob/0.4.5/src/oasis/OASISLibrary.ml#L203> line. This seems to be in error to me. Shouldn’t the line read:
if has_native_dynlink [["dll"^cs.cs_name^"_stubs"^ext_dll]] else []
to account for the possibility that the compiler cannot generate or load dynamic libraries?
In any event, even if I’m wrong about the particulars, it’s clearly true that the ocamlbuild code generated by at least some versions of Oasis does not respect the inability of perfectly valid OCaml environments to support shared libraries, so any advice is welcome.
Best regards,
Paul
[-- Attachment #2: Type: text/html, Size: 1431 bytes --]
reply other threads:[~2016-03-28 13:39 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=206FE738-9D7C-4739-A82B-643CFF82260B@mac.com \
--to=psnively@mac.com \
--cc=caml-list@inria.fr \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox