ocaml-3.11.1 native code compiler fails.

[kiyoshi.coquser@…]

Ocaml 3.11.1 have some issues about native code generation.

So building of some ports (ex. Unison +aqua) fails.

I prepared minimal patches to fix these issues.

They are borrowed from Caml CVS repository:

 http://camlcvs.inria.fr/

Fixing issues:

0004813: incorrect parsing of floating point literals

 http://caml.inria.fr/mantis/view.php?id=4813

0004841: Cannot make callbacks from C code when using the -output-obj option under Mac OS X

 http://caml.inria.fr/mantis/view.php?id=4841

0004867: ocamlopt -shared failed on Mac OS X 10.6 Snow Leopard (x86_64)

 http://caml.inria.fr/mantis/view.php?id=4867

0004877: Definition of uint64 in caml/config.h conflicts. (MacOSX Snow Leopard, X86_64)

 http://caml.inria.fr/mantis/view.php?id=4877

Note: These issues will be fixed in the next release of ocaml.

[kiyoshi.coquser@…]

patch files

[avsm@…]

Cc Me!

[avsm@…]

Cc Me!

[avsm@…]

svn diff of the changes

[avsm@…]

Attached ocaml.diff of the changes which also bumps Revision of the port in the Portfile. Testing it now on x86_32 Snow Leopard

[avsm@…]

no regressions spotted in x86_32, except an unrelated bug involving ld.conf - most of our ports do not update the ld.conf on install, so I changed base ocaml to include the ld.conf directory in its ld.conf. Committed in r58665 .

Kiyoshi, if you could confirm that your problems are fixed on x86_64 SL with this commit, I'd appreciate it.

[kiyoshi.coquser@…]

Replying to avsm@…:

I confirm that unison +aqua port (with 64bit support patches) now be compiled on X86_64 environment.

It also passed my private test cases which I built to clarify the problem.

And, patch for ld.conf is nice.

Thanks a lot avsm.

[stessaris@…]

0004877: Definition of uint64 in caml/config.h conflicts. (MacOSX Snow Leopard, X86_64)  http://caml.inria.fr/mantis/view.php?id=4877 Note: These issues will be fixed in the next release of ocaml.

Version 3.11.2 doesn't fix 0004877 (see  http://caml.inria.fr/mantis/changelog_page.php), so the conflict is still there.

[ryandesign@…]

Neither does 3.12.0 apparently (the upstream bug report is still open)