Join GitHub today
GitHub is home to over 31 million developers working together to host and review code, manage projects, and build software together.Sign up
Non deleted object files on fatal warnings #7918
Original bug ID: 7918
When compilation of a module failed because of warnings, the generated
Tested on GNU/Linux (Arch) with the two following versions
Steps to reproduce
Run the script checkspuriousobj.sh
Comment author: cfranchini
We're talking about the program which builds gcc, linux, bash, emacs, ocaml, ... I'm sure it's behavior is the correct one.
[striked]I disagree, and I'm sure that a lot of people would agree with me. (Just to be sure: it's not sarcasm, is it?)[/striked]
edit: I was misunderstanding your second statement. It's not how make works.
Comment author: @alainfrisch
Please let's stay focused here on what OCaml should do, not what a good build system should be. make is still used quite a bit (to build OCaml itself for instance) and we should not break existing workflows. Assuming the described behavior is a change in recent versions, I'm in favor of going back to the previous behavior.
If needed, one could add a command-line flag to control the behavior. But:
.cmt/.cmti files should certainly be kept even in case of errors, and they contain all the information (.cmti files "include" the .cmi information as is). Doesn't Merlin use these files?