You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
This is a bug report filed as (I think 1539), and signed off as "working fine
locally". I'll simplify the problem a little bit:
The problem occurs when compiling an interface file (x.ml) into a non-local
location:
ocamlc -c -o /tmp/x.cmi x.mli
The result: x.cmi is located in the local directory, not in /tmp.
The text was updated successfully, but these errors were encountered:
This is a bug report filed as (I think 1539), and signed off as
"working fine locally". I'll simplify the problem a little bit:
The problem occurs when compiling an interface file (x.ml) into a non-local
location:
ocamlc -c -o /tmp/x.cmi x.mli
The result: x.cmi is located in the local directory, not in /tmp.
Oh, I see your point now. In the current implementation, the -o option
is ignored for compilation (ocamlc -c): it determines the name of the
output only for linking (ocamlc, ocamlc -output-obj) and library
construction (ocamlc -a, ocamlc -pack). (See the reference manual.)
So, the behavior you observe is "normal", although it doesn't do what
you want. I'll file your report as a feature wish.
One problem with honoring -o during compilation is what to do if
several source files are given on the command line.
Original bug ID: 1652
Reporter: administrator
Status: closed
Resolution: fixed
Priority: normal
Severity: feature
Category: ~DO NOT USE (was: OCaml general)
Bug description
Full_Name: Ohad Rodeh
Version: 3.06
OS: WinXP/Linux
Submission from: 80.178.100.217.forward.012.net.il (80.178.100.217)
This is a bug report filed as (I think 1539), and signed off as "working fine
locally". I'll simplify the problem a little bit:
The problem occurs when compiling an interface file (x.ml) into a non-local
location:
ocamlc -c -o /tmp/x.cmi x.mli
The result: x.cmi is located in the local directory, not in /tmp.
The text was updated successfully, but these errors were encountered: