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 -log doesn't consistently (and cleanly) report inexistent directories #4313

Closed
vicuna opened this issue Jun 12, 2007 · 1 comment
Labels

Comments

@vicuna
Copy link

vicuna commented Jun 12, 2007

Original bug ID: 4313
Reporter: @dbuenzli
Assigned to: ertai
Status: closed (set by @xavierleroy on 2010-04-29T12:26:11Z)
Resolution: fixed
Priority: normal
Severity: minor
Version: 3.10.0
Fixed in version: 3.10+dev
Category: ~DO NOT USE (was: OCaml general)

Bug description

Go into a directory where there is no b and _build directory.

cd /tmp
rm -rf _build b
ocamlbuild -log b/_log
Fatal error: exception Sys_error("/private/tmp/b/_log: No such file or directory")
Raised at file "stdlib/lazy.ml", line 70, characters 51-52
Called from file "ocamlbuild/shell.ml", line 46, characters 15-88
Re-raised at file "stdlib/lazy.ml", line 71, characters 12-13
Called from file "ocamlbuild/log.ml", line 36, characters 55-73
Called from file "ocamlbuild/log.ml", line 38, characters 28-72
Called from file "ocamlbuild/log.ml", line 39, characters 18-34
Called from file "ocamlbuild/ocamlbuild.ml", line 15, characters 0-28

Now if I do the same a second time nothing is reported :

ocamlbuild -log b/_log

Another thing is that the _log seems to be created �before the _build hence if I try to use ocamlbuild with -log _build/_log after an ocamlbuild -clean, the first error is triggered.

And please (feature) make the _log in _build by default, it's a one line change and makes it easier for other tools (and humans) to ignore build artefacts (with respect to that I would also make the -no-links the default since the feature is anyway limited).

Best,

Daniel

@vicuna
Copy link
Author

vicuna commented Nov 22, 2007

Comment author: ertai

Thanks for the report. This is now fixed in the CVS (both in trunk and release310 branch).

@vicuna vicuna closed this as completed Apr 29, 2010
@vicuna vicuna added the bug label Mar 19, 2019
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

No branches or pull requests

1 participant