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

camlp4lib.cma embeds dynlink modules #4568

Closed
vicuna opened this issue Jun 22, 2008 · 2 comments
Closed

camlp4lib.cma embeds dynlink modules #4568

vicuna opened this issue Jun 22, 2008 · 2 comments

Comments

@vicuna
Copy link

vicuna commented Jun 22, 2008

Original bug ID: 4568
Reporter: @glondu
Assigned to: ertai
Status: closed (set by @xavierleroy on 2010-04-29T12:31:16Z)
Resolution: fixed
Priority: normal
Severity: tweak
Version: 3.10.2
Fixed in version: 3.11+dev
Category: -for Camlp4 use https://github.com/ocaml/camlp4/issues

Bug description

Hello,

The archive camlp4lib.cma seems embed dynlink modules:

$ ocamlobjinfo /usr/lib/ocaml/3.10.2/camlp4/camlp4lib.cma|grep Unit
Unit name: Dynlinkaux
Unit name: Dynlink
Unit name: Camlp4_import
Unit name: Camlp4_config
Unit name: Camlp4
$ ocamlobjinfo /usr/lib/ocaml/3.10.2/dynlink.cma|grep Unit
Unit name: Dynlinkaux
Unit name: Dynlink

This results in duplication of these modules in projects which use independently dynlink.cma and camlp4lib.cma.

Is there a good reason for this choice?

@vicuna
Copy link
Author

vicuna commented Oct 23, 2008

Comment author: @glondu

Meanwhile, I've seen situations where linking the same module twice may result in trouble (namely, uncatchable exceptions). This problem still exists in OCaml 3.11.0+beta1. Is it planned to fix it?

@vicuna
Copy link
Author

vicuna commented Oct 23, 2008

Comment author: ertai

Thanks for the report this is now fixed in the CVS (head and release311).

Notice that some program will require an explicit linking with the dynlink library.

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

No branches or pull requests

1 participant