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

Installation problems on Alpha/Linux #3583

Closed
vicuna opened this issue Aug 23, 2002 · 4 comments
Closed

Installation problems on Alpha/Linux #3583

vicuna opened this issue Aug 23, 2002 · 4 comments
Labels

Comments

@vicuna
Copy link

vicuna commented Aug 23, 2002

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

Bug description

Full_Name: Stefan Kral
Version: 3.05 and 3.06
OS: SuSE Linux 6.4
Submission from: a03.dialin.tuwien.ac.at (192.35.240.13)

The installation process of ocaml-3.05 and ocaml-3.06 fails on my 21164PC-based
Alpha-box running Linux.

'make world' proceeds up to 'ocaml-3.0x/ocamldoc'.

Then, 'sh ./runocamldoc [...]' outputs 1 out of these 2 error messages and
aborts:
w/ocaml-3.05: "Compiler error. Use the ocaml compiler to get more details."
w/ocaml-3.06: "Fatal error. out of memory"

These problems may be related to the (relatively) old versions of binutils and
gcc that I use. However, the compilation of ocaml-3.00 succeeds without any
problems.

Regards,
Stefan

@vicuna
Copy link
Author

vicuna commented Aug 26, 2002

Comment author: administrator

Hello,

The installation process of ocaml-3.05 and ocaml-3.06 fails on my 21164PC-based
Alpha-box running Linux.

'make world' proceeds up to 'ocaml-3.0x/ocamldoc'.

Then, 'sh ./runocamldoc [...]' outputs 1 out of these 2 error messages and
aborts:
w/ocaml-3.05: "Compiler error. Use the ocaml compiler to get more details."
w/ocaml-3.06: "Fatal error. out of memory"

These problems may be related to the (relatively) old versions of binutils and
gcc that I use. However, the compilation of ocaml-3.00 succeeds without any
problems.

Could you run the last command with an additionnal -v option and send the last lines
of the output (this is the verbose mode, to know when it crashes) ? Thanks.
BTW, how much RAM do you have ?

As a temporary workaround, you can do the following, in ocamldoc/Makefile:

  • remove "manpages" from the "all" target
  • in the "install" target, remove the line
    $(CP) stdlib_man/* $(INSTALL_MANODIR)

So ocamldoc will not be launched to create std library man pages, and man pages
wil not be installed, but the rest of the compilation should be ok.

Regards,

--
Maxence Guesdon

@vicuna
Copy link
Author

vicuna commented Aug 26, 2002

Comment author: administrator

I attached the entire session log to this mail.

Thanks. It appears to be the same problem that we encountered on
Itanium/Linux: malloc() can return blocks that are very far apart
(e.g. several terabytes apart), causing an internal bitmap used by the
OCaml GC to explode. Guess it's a phenomenon common to all 64-bit
ports of Linux and not just the Itanium port.

The good news is that the workaround is already in the sources, it
just needs to be activated. Here's how: without re-running "configure",
add the following line to config/s,h:
#define USE_MMAP_INSTEAD_OF_MALLOC

Then do make clean, make world, make opt.

Let me know if it works. In the meantime, I'll fix the configure script.

All the best,

  • Xavier Leroy

@vicuna
Copy link
Author

vicuna commented Aug 26, 2002

Comment author: administrator

On Mon, 26 Aug 2002, Xavier Leroy wrote:

I attached the entire session log to this mail.

Thanks. It appears to be the same problem that we encountered on
Itanium/Linux: [...]

The good news is that the workaround is already in the sources, it
just needs to be activated. [...]
Let me know if it works. [...]
I just tried it and it works fine.

Regards,
Stefan Kral

@vicuna
Copy link
Author

vicuna commented Aug 27, 2002

Comment author: administrator

Fixed 2002-08-27 by XL (use mmap instead of malloc)

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

No branches or pull requests

1 participant