-
Notifications
You must be signed in to change notification settings - Fork 346
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Packaging opam for FreeBSD shows strange error #4894
Comments
Also I'm curious since the full tarball an build process compiles an OCaml compiler, but configure checks for a OCaml compiler as well, if that could be simplified -- and if the shipped OCaml compiler could be used for all OCaml code in the full tarball (to drop the dependency on an external OCaml compiler). |
The requirement on curl/wget should be fixed, yes - I'll have a look at that. When you bootstrap a compiler,
i.e. if you bootstrapped the compiler as part of opam's build, it will completely the presence or not of any preinstalled ocaml compiler. |
I'm not sure I understand what you mean. An experiment I conduct without any
Now, the packaged compiler fro FreeBSD is 4.05.0, if this is installed I get:
Maybe I misunderstand how building opam-full should be done -- should there be a |
I also tried to run
That makes me wonder why findlib/ocamlbuild/topkg are in Makefile.sources as it seems they are not used for compilation? |
After reading some more of configure.ac and the recent development on the master branch, I'd hope that before a 2.2 release is done, this could be solved. A hacky solution would be a custom |
I'm not sure there's anything which needs to be solved, but it does sound as though there is a bug in the full tarball in that it forces requirement of a tool which isn't needed (the curl/wget part)! The README specifies that OCaml is a prerequisite and has a link to further in down it for if you don't to https://github.com/ocaml/opam#compiling-without-ocaml which explains |
Thanks @dra27, indeed I missed the |
The findlib, ocamlbuild, etc. tarballs are there for the |
Indeed, to wrap up:
Sorry for the partial noise, and please enjoy your weekend. Special thanks to @dra27 for pointing me to the documentation. |
In FreeBSD, we now have opam 2.1.2 in the ports with two patches (see https://github.com/freebsd/freebsd-ports/tree/65d44673f0de934bf18081e60ca92742cb404324/devel/ocaml-opam/files)
The sad news is that with opam 2.0.x (where we were able to use OCaml 4.05.0 from ports (also patched https://github.com/freebsd/freebsd-ports/tree/65d44673f0de934bf18081e60ca92742cb404324/lang/ocaml/files), this worked nicely on arm32 bit systems -- now it fails and my attempts to get this working lead nowhere (https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=261180). |
FWIW, it would be greatly appreciated if these packaging issues could be addressed before the next release (even if it is 2.1.3) -- mainly the |
#5223 should fix half of this issue. And if I understand correctly, once 4.14.1 is out and opam bootstraps with it, it should fix the remaining issue. EDIT: Actually it's in 4.14.0 |
Dear all,
I want to update the FreeBSD port of devel/ocaml-opam from 2.0.8 to 2.1.1. I use the full tarball -- i.e. where all dependencies are embedded as tarballs (since the build phase does not have access to the network). While doing that, I noticed that now a full OCaml compiler is bootstrapped. This is done via shell/bootstrap-ocaml.sh, which right at the top has needlessly an
exit 1
if neither "curl" nor "wget" is found. As the full tarball contains all tarballs, this shell script will never execute "curl"/"wget", and the shell script should not exit with 1.For the FreeBSD package, I added a local patch https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=259667 (https://bugs.freebsd.org/bugzilla/attachment.cgi?id=229304&action=diff) -- but it would be nice to fix the bootstrap story of the full tarball before a next release. Since I'm not sure how the bootstrap story is put together, I'm not sure what an appropriate fix is (in FreeBSD, we as well pass
--disable-checks
to configure since otherwise (at least in earlier releases) opam refused to build without curl/wget).Thanks for reading and have a nice weekend,
Hannes
The text was updated successfully, but these errors were encountered: