Skip to content
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

ocamlbuild non backward compatible change found #6118

Closed
vicuna opened this issue Aug 5, 2013 · 5 comments
Closed

ocamlbuild non backward compatible change found #6118

vicuna opened this issue Aug 5, 2013 · 5 comments
Assignees

Comments

@vicuna
Copy link

vicuna commented Aug 5, 2013

Original bug ID: 6118
Reporter: @bobzhang
Assigned to: @gasche
Status: closed (set by @xavierleroy on 2016-12-07T10:34:49Z)
Resolution: not a bug
Priority: normal
Severity: minor
Version: 4.02.0+dev
Target version: undecided
Category: -for ocamlbuild use https://github.com/ocaml/ocamlbuild/issues
Related to: #5547
Monitored by: @hcarty

Bug description

trunk>ocamlbuild -clean
Failure: ocamlfind not found on path, but -no-ocamlfind not used.

@vicuna
Copy link
Author

vicuna commented Aug 10, 2013

Comment author: @bobzhang

My 2 cents: ocamlfind is not distributed with ocaml, -use-ocamlfind by default nearly breaks all my private repos :-(

@vicuna
Copy link
Author

vicuna commented Aug 21, 2013

Comment author: @damiendoligez

See the discussion in #5547. The bottom line is: almost all OCaml developers have ocamlfind installed, and the ones who don't, should install it. If you really don't want to install it, you'll have to use the -no-ocamlfind option.

@vicuna
Copy link
Author

vicuna commented Sep 19, 2014

Comment author: @gasche

Damien's point is perfectly true, but I would still like to fix the fact that no ocamlfind should be required to clean, only to build stuff.

@vicuna
Copy link
Author

vicuna commented Sep 21, 2014

Comment author: @gasche

I looked at this (accepting "ocamlbuild -use-ocamlfind -clean" in absence of ocamlfind) again. It's not difficult to fix, but it's not trivial to make sure this doesn't introduce regression, so it's not clear it's worth it. Dropping the idea for now.

@vicuna
Copy link
Author

vicuna commented Sep 21, 2014

Comment author: @gasche

This PR doesn't make much sense in the old-and-new world where -no-ocamlfind is the default, and -use-ocamlfind has to be explicitly specified.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

2 participants