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
Original bug ID: 64 Reporter: administrator Status: closed Resolution: not a bug Priority: normal Severity: minor Category: ~DO NOT USE (was: OCaml general)
Sometimes, but not always, the final linking of an OCAMLMKTOP application fails
with the message that the linker is unable to open the TEMPORARY directory
(Win/NT 4.0 sp 3 LINK.EXE). I have found that there is a residual file named
"ocamlprim0.obj" left in the destination directory, and that by removing this
old file and rerunning the Make, then the linking succeeds. However, if I rerun
the Make without first removing this leftover file, it fails consistently with
the above message. I have not yet found where, in the OCAML sources, this
behavior is induced.
The text was updated successfully, but these errors were encountered:
Couldn't reproduce the problem, but added an explicit "remove" of the .obj file
left behind by VC++. It's cleaner and might fix the problem too. -Xavier,
2000-04-10.
Original bug ID: 64
Reporter: administrator
Status: closed
Resolution: not a bug
Priority: normal
Severity: minor
Category: ~DO NOT USE (was: OCaml general)
Bug description
Full_Name: David McClain
Version: 2.99
OS: Win/NT 4.0 (sp 3)
Submission from: dialup001ip074.tus.azstarnet.com (169.197.12.74)
Sometimes, but not always, the final linking of an OCAMLMKTOP application fails
with the message that the linker is unable to open the TEMPORARY directory
(Win/NT 4.0 sp 3 LINK.EXE). I have found that there is a residual file named
"ocamlprim0.obj" left in the destination directory, and that by removing this
old file and rerunning the Make, then the linking succeeds. However, if I rerun
the Make without first removing this leftover file, it fails consistently with
the above message. I have not yet found where, in the OCAML sources, this
behavior is induced.
The text was updated successfully, but these errors were encountered: