From: Matthieu Dubuget <matthieu.dubuget@gmail.com>
To: caml-list@inria.fr
Subject: Re: [Caml-list] Re: Strange compilation problem (flexlink trying to deal with windows and cygwin shell limitations)
Date: Wed, 11 Feb 2009 16:15:19 +0100 [thread overview]
Message-ID: <4992EB87.1000901@gmail.com> (raw)
In-Reply-To: <BB046CA812535C45BD0029AA9D04BA7905ECDCD6@KL-SRV57.lmsintl.com>
Christoph Bauer a écrit :
> I added -L$(cygpath -m /usr/lib/w32api) somewhere in the command lin while linking.
> Does this help? (Maybe as -cclib -L$(cygpath -m /usr/lib/w32api))
>
> Regards,
>
> Christoph Bauer
>
No :-/
But I think I understood the problem. flexlink tries a lot of paths.
And if the file is not found, a cygpath conversion is tried before
a second search.
This cygpath conversion is done through a file redirection.
> let get_output cmd =
> let fn = Filename.temp_file "flexdll" "" in
> if (Sys.command (cmd ^ " > " ^ fn) < 0)
> then failwith ("Cannot run " ^ cmd);
> let r = read_file fn in
> Sys.remove fn;
> r
In my case fn is void, and cmd is… long.
String.length cmd gives 8406 ie > 8k
I'm pretty sure that I could have my app. compiled
by using a site-lib directory near the root of the filesystem.
Salutations
Matt
next prev parent reply other threads:[~2009-02-11 15:15 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-02-11 9:28 Strange compilation problem Matthieu Dubuget
2009-02-11 12:05 ` Matthieu Dubuget
2009-02-11 14:30 ` Matthieu Dubuget
[not found] ` <BB046CA812535C45BD0029AA9D04BA7905ECDCCB@KL-SRV57.lmsintl.com>
2009-02-11 14:51 ` [Caml-list] " Matthieu Dubuget
[not found] ` <BB046CA812535C45BD0029AA9D04BA7905ECDCD6@KL-SRV57.lmsintl.com>
2009-02-11 15:15 ` Matthieu Dubuget [this message]
2009-02-11 16:30 ` [Caml-list] Re: Strange compilation problem -> solved Matthieu Dubuget
2009-02-11 17:19 ` Alain Frisch
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=4992EB87.1000901@gmail.com \
--to=matthieu.dubuget@gmail.com \
--cc=caml-list@inria.fr \
/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