Opened 7 years ago
Last modified 7 years ago
#55640 assigned defect
ocaml-ctypes: use of undeclared identifier 'uint64'
Reported by: | skymoo (Adam Mercer) | Owned by: | pmetzger (Perry E. Metzger) |
---|---|---|---|
Priority: | Normal | Milestone: | |
Component: | ports | Version: | |
Keywords: | Cc: | hapaguy (Brian Kurt Fujikawa), pmetzger (Perry E. Metzger) | |
Port: | ocaml-ctypes |
Description
Getting the following when trying to build ocaml-ctypes
on Sierra:
:info:build /opt/local/var/macports/build/_opt_local_var_macports_sources_rsync.macports.org_release_tarballs_ports_ocaml_ocaml-ctypes/ocaml-ctypes/work/ocaml-ctypes-0.3.4/src/ctypes/type_info_stubs.c:51:52: error: expected expression :info:build case Uint64_t: b = ctypes_copy_uint64(*(uint64 *)buf); break; :info:build ^ :info:build /opt/local/var/macports/build/_opt_local_var_macports_sources_rsync.macports.org_release_tarballs_ports_ocaml_ocaml-ctypes/ocaml-ctypes/work/ocaml-ctypes-0.3.4/src/ctypes/type_info_stubs.c:51:44: error: use of undeclared identifier 'uint64' :info:build case Uint64_t: b = ctypes_copy_uint64(*(uint64 *)buf); break; :info:build ^ :info:build /opt/local/var/macports/build/_opt_local_var_macports_sources_rsync.macports.org_release_tarballs_ports_ocaml_ocaml-ctypes/ocaml-ctypes/work/ocaml-ctypes-0.3.4/src/ctypes/type_info_stubs.c:92:29: error: expected expression :info:build case Uint64_t: *(uint64 *)buf = Uint64_val(v); break; :info:build ^ :info:build /opt/local/var/macports/build/_opt_local_var_macports_sources_rsync.macports.org_release_tarballs_ports_ocaml_ocaml-ctypes/ocaml-ctypes/work/ocaml-ctypes-0.3.4/src/ctypes/type_info_stubs.c:92:21: error: use of undeclared identifier 'uint64' :info:build case Uint64_t: *(uint64 *)buf = Uint64_val(v); break; :info:build ^ :info:build 4 errors generated.
Full build log is attached.
Attachments (1)
Change History (15)
Changed 7 years ago by skymoo (Adam Mercer)
comment:1 Changed 7 years ago by mf2k (Frank Schima)
comment:2 Changed 7 years ago by mf2k (Frank Schima)
I tried updating to the latest version, but it fails to build because:
ocamlfind: Package `integers' not found
It looks like we need to create a port for ocaml-integers. https://github.com/ocamllabs/ocaml-integers
comment:3 Changed 7 years ago by hapaguy (Brian Kurt Fujikawa)
Cc: | hapaguy added |
---|
comment:4 Changed 7 years ago by hapaguy (Brian Kurt Fujikawa)
Any updates on this issue? Workarounds? Port science/root6 is dependent on ocaml-ctypes, and the undeclared uint64
issue is preventing its installation.
comment:5 Changed 7 years ago by pmetzger (Perry E. Metzger)
We need to fix a bunch of ocaml infrastructure. Given that these problems would be straightforward. I'm adding myself to the ticket for now.
comment:6 Changed 7 years ago by pmetzger (Perry E. Metzger)
Cc: | pmetzger added |
---|
comment:7 Changed 7 years ago by pmetzger (Perry E. Metzger)
Owner: | set to pmetzger |
---|---|
Status: | new → assigned |
comment:8 Changed 7 years ago by pmetzger (Perry E. Metzger)
Note that I'm trying to come up with a comprehensive solution right now. If there's a rush on this, I'd recommend that you help me manually packaging the dependents (which include ocaml-integer and ocaml-topkg) for now.
comment:9 Changed 7 years ago by pmetzger (Perry E. Metzger)
So I'm currently working on getting some changes made to OPAM to make it possible to cleanly track OCaml packages going forward. This may take a little while to finish.
comment:10 Changed 7 years ago by skymoo (Adam Mercer)
Thanks. I know next to nothing about OCaml, I tried packaging the dependencies when this originally came up but didn't get very far.
comment:11 Changed 7 years ago by pmetzger (Perry E. Metzger)
It's a pretty complicated ecosystem and we were without an OCaml package maintainer for a long time. Sorry about the delay. If you can give me a list of OCaml packages you're dependent on I'll try to prioritize them.
comment:12 Changed 7 years ago by skymoo (Adam Mercer)
The priority for me is getting the port mentioned in this ticket, i.e. ocaml-ctypes
, building with a newer Xcode.
comment:13 Changed 7 years ago by pmetzger (Perry E. Metzger)
I'll see what can be done there later this week.
comment:14 Changed 7 years ago by skymoo (Adam Mercer)
No rush, this has been waiting a few months without major issue. I can wait until you have the infrastructure ready.
It looks like our port is way out of date. Latest version is 0.13.1.