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

ocamlc failing when linking very large object codes #8459

Closed
vicuna opened this issue Jan 26, 2004 · 3 comments
Closed

ocamlc failing when linking very large object codes #8459

vicuna opened this issue Jan 26, 2004 · 3 comments

Comments

@vicuna
Copy link

vicuna commented Jan 26, 2004

Original bug ID: 2060
Reporter: administrator
Status: closed (set by @xavierleroy on 2015-12-11T18:24:00Z)
Resolution: fixed
Priority: normal
Severity: feature
Category: ~DO NOT USE (was: OCaml general)

Bug description

Full_Name: David Monniaux
Version: 3.07+2
OS: Linux
Submission from: basilic.ens.fr (129.199.99.48)

On one of our projects, ocamlc fails to link the object files if some very large
.cmo files (generated with -g) are linked in (the one that causes the problem is
36 Mb long).

The problem does not occur with ocamlopt or ocamlc without -g.

The very large file is generated from an automatically generated 1900 line
source code making numerous functor instanciations.

@vicuna
Copy link
Author

vicuna commented Apr 15, 2004

Comment author: administrator

Is this limit easy to raise? DD 2004-04-15

@vicuna
Copy link
Author

vicuna commented Jan 27, 2012

Comment author: @damiendoligez

It's a pity that we don't know what the error message was. From reading bytelink.ml, this looks related to the size limit on strings, and that limit practically doesn't exist on 64-bit machines.

@vicuna
Copy link
Author

vicuna commented Aug 30, 2013

Comment author: @damiendoligez

This is most likely a remake of #1615, #5920, and #5957, which were fixed by rev 13547. See #5957 for details.

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