> ../boot/ocamlrun ../ocamlc -I ../boot -linkall -I ../otherlibs/unix -o
> ocamldebug.exe <object files>
>
> with precisely the same error message:
>
> gcc: FilesObjective: No such file or directory
> gcc: Camllib: No such file or directory
> gcc: FilesObjective: No such file or directory
> gcc: Camllib: No such file or directory
> Error while building custom runtime system
One possibility is that you have the OCAMLLIB or CAMLLIB environment
variable set to something like \Program Files\Objective Caml\lib,
e.g. because of a previous installation of the "pure Win32" version of
OCaml. Try to do
unset OCAMLLIB
unset CAMLLIB
in the Bash shell before proceeding with the compilation.
If it still doesn't work, try sticking a "-verbose" option in the
offending command line:
> ../boot/ocamlrun ../ocamlc -verbose -I ../boot -linkall \
> -I ../otherlibs/unix -o ocamldebug.exe <object files>
This causes ocamlc to print the exact invocation of gcc -- very useful
to track down problems like this.
The current release of OCaml definitely mis-handles spaces in
the path to the standard library directory, and also fails to ignore
completely previous installations of OCaml while compiling itself.
Damien Doligez has fixed the latter problem recently, and we promise
to do something about the former before the next release.
Keep us (caml@inria.fr) informed.
- Xavier Leroy
-------------------
To unsubscribe, mail caml-list-request@inria.fr Archives: http://caml.inria.fr
Bug reports: http://caml.inria.fr/bin/caml-bugs FAQ: http://caml.inria.fr/FAQ/
Beginner's list: http://groups.yahoo.com/group/ocaml_beginners