From: Dawid Toton <d0@wp.pl>
To: caml-list@yquem.inria.fr
Subject: Re: [Caml-list] MingW compiler (!) and Ocaml for Windows
Date: Fri, 31 Aug 2007 21:32:17 +0200 [thread overview]
Message-ID: <46D86CC1.5090801@wp.pl> (raw)
> If on the other side problems with "@responsefile" are only occuring
> in more rare situation -- can anybody tell me how to provoke the
> problem?
I was compiling an application using LablGTK to native code (using
MSYS). AFAIR the linker invocation contained quite long list of
libraries and ocamlopt decided to use responsefile. I got some
incomprehensible error message (and only then discovered that I have to
use Cygwin tools). I have no idea whether the problem with MSYS tools
still persists. When command parameters were short enough they worked
seamlessly.
Dawid Toton
next reply other threads:[~2007-08-31 19:32 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-08-31 19:32 Dawid Toton [this message]
2007-09-01 1:41 ` Markus E L
2007-09-01 5:49 ` kyra
2007-09-01 10:03 ` Adrien
2007-09-01 15:25 ` Markus E L
2007-09-01 15:13 ` Leypold Software-Dienstleistungen
-- strict thread matches above, loose matches on Subject: below --
2007-08-26 14:07 Markus E L
2007-08-26 16:06 ` [Caml-list] " Adrien
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=46D86CC1.5090801@wp.pl \
--to=d0@wp.pl \
--cc=caml-list@yquem.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;
as well as URLs for NNTP newsgroup(s).