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

Jump to bottom

Incorrect cleanup after building custom runtime #3041

Closed
vicuna opened this issue Nov 18, 2001 · 2 comments
Closed

Incorrect cleanup after building custom runtime #3041

vicuna opened this issue Nov 18, 2001 · 2 comments
Labels
bug

Comments

@vicuna
Copy link

vicuna commented Nov 18, 2001

Original bug ID: 640
Reporter: administrator
Status: closed
Resolution: fixed
Priority: normal
Severity: minor
Category: ~DO NOT USE (was: OCaml general)

Bug description

Full_Name: Dmitry Bely
Version: 3.03 alpha, MSVC build
OS: Windows 2000
Submission from: stormoff.access.telecore.net.ru (213.135.65.93)

ocamlc does not correctly remove temporary camlprim?.obj after building custom
runtime:

bytecomp/bytelink.ml, line 444
(* C compiler doesn't clean up after itself *)
remove_file (Filename.chop_suffix prim_name ".c" ^ ".obj");

It does not work, because C compiler creates prim_name^".obj" in current
directory, while prim_name^".c" resides in temporary one.
@vicuna
Copy link
Author

vicuna commented Nov 26, 2001

Comment author: administrator

ocamlc does not correctly remove temporary camlprim?.obj after
building custom runtime:

bytecomp/bytelink.ml, line 444
(* C compiler doesn't clean up after itself *)
remove_file (Filename.chop_suffix prim_name ".c" ^ ".obj");

It does not work, because C compiler creates prim_name^".obj" in current
directory, while prim_name^".c" resides in temporary one.

Well spotted! I fixed this in the working sources.

Thanks,

  • Xavier Leroy

@vicuna
Copy link
Author

vicuna commented Nov 26, 2001

Comment author: administrator

Fixed 2001-11-26 by XL

@vicuna vicuna closed this as completed Nov 26, 2001
@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
Assignees
No one assigned
Labels
bug
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
1 participant
@vicuna