From: Xavier Leroy <xavier.leroy@inria.fr>
To: Friedman Roy <roy@cs.technion.ac.il>
Cc: caml-list@inria.fr
Subject: Re: [Caml-list] Problem building -custom on Windows 2000
Date: Thu, 18 Jul 2002 11:52:05 +0200 [thread overview]
Message-ID: <20020718115205.A6341@pauillac.inria.fr> (raw)
In-Reply-To: <Pine.GSO.4.33_heb2.09.0207180936440.25388-100000@csa.cs.technion.ac.il>; from roy@cs.technion.ac.il on Thu, Jul 18, 2002 at 09:45:06AM +0300
> Has anyone encountered the following problem:
> My development environment is Windows 2000, Ocaml 3.04, and Dev Studio
> .NET (for the necessary C compiler, linker, etc)
> I am trying to build an ocaml application with the -custom switch.
> The problem is that if OCAMLLIB is defined as "C:\program files\..."
> the link stage fails claiming that it cannot find the relevant Ocaml
> files.
This problem is known as "the killer space in file names" :-)
OCaml 3.04 calls the C linker without quoting properly the file arguments,
including the OCaml standard library directory. You can view the
resulting mess by running ocamlc -verbose -custom ... for the linking
phase.
This bug should be fixed for good in 3.05. In the meantime, using the
DOS name for OCAMLLIB, as suggested on this list, should do the job.
- 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
prev parent reply other threads:[~2002-07-18 9:52 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-03-25 17:03 [Caml-list] New Ensemble release, 1.35 Ohad Rodeh
2002-07-18 6:45 ` [Caml-list] Problem building -custom on Windows 2000 Friedman Roy
2002-07-18 7:41 ` Jacques Garrigue
2002-07-18 9:26 ` Nicolas Cannasse
2002-07-18 11:12 ` Friedman Roy
2002-07-24 12:13 ` [Caml-list] Has anyone implemented compression in pure OCaml Friedman Roy
2002-07-18 9:52 ` Xavier Leroy [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20020718115205.A6341@pauillac.inria.fr \
--to=xavier.leroy@inria.fr \
--cc=caml-list@inria.fr \
--cc=roy@cs.technion.ac.il \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).