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

"make install" should install interface files for toploop-manipulation modules #8255

vicuna opened this issue Aug 28, 2003 · 1 comment


Copy link

@vicuna vicuna commented Aug 28, 2003

Original bug ID: 1804
Reporter: administrator
Assigned to: @xavierleroy
Status: closed (set by @xavierleroy on 2015-12-11T18:04:40Z)
Resolution: fixed
Priority: normal
Severity: feature
Fixed in version: 4.00.0+dev
Category: ~DO NOT USE (was: OCaml general)
Has duplicate: #8343
Monitored by: nogin

Bug description

Full_Name: Aleksey Nogin
Version: 3.06, 3.07beta2
OS: Red Hat Linux
Submission from: (

In order to create a custom Ocaml toploop and to be able to manipulate it
successfuly, one needs access to a bunch of interface files that are not
normally copied into LIBDIR by ocaml's "make install". For example, to be able
to compile code that uses Toplevel.execute_phrase, one needs access to

Currently (see
for the code of the file that manipulates the toploop) we end up having to
manually copy the files:

parsing/location.cmi parsing/location.mli parsing/longident.cmi
parsing/longident.mli parsing/parsetree.cmi parsing/parsetree.mli
typing/typecore.cmi typing/typecore.mli

to LIBDIR. Would you please consider modifying the "install" target in the
Makefile to copy these files (and may be other interface files needed to take
full advantage of Toploop module - such as env.{mli,cmi}, for example) somewhere
under LIBDIR?

Thanks a lot!

Copy link

@vicuna vicuna commented May 24, 2012

Comment author: @xavierleroy

Upcoming release 4.00 installs a big chunk of compiler internal files in ocamlc -where /compiler-libs. You should find everything you need there.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
None yet
Linked pull requests

Successfully merging a pull request may close this issue.

None yet
2 participants