<html>
<head>
<meta http-equiv="Content-Type" content="text/html; charset=Windows-1252">
<meta name="Generator" content="Microsoft Exchange Server">
<!-- converted from text --><style><!-- .EmailQuote { margin-left: 1pt; padding-left: 4pt; border-left: #800000 2px solid; } --></style>
</head>
<body>
<div>
<div>Cygwin executables support @response files when invoked by a native process (it's not relevant when they're invoked by q Cygwin process, as the limit doesn't exist).</div>
<div><br>
</div>
<div>I thought flexlink could already do this, but it's not a major patch to flexlink if it can't.</div>
<div><br>
</div>
<div><br>
</div>
<div>David<br>
<br>
<div class="x_acompli_signature"></div>
<br>
</div>
<br>
<br>
<br>
<div class="x_gmail_quote">On Thu, Jul 7, 2016 at 8:18 AM +0100, "Andre Maroneze"
<span dir="ltr"><<a href="mailto:Andre.OLIVEIRAMARONEZE@cea.fr" target="_blank">Andre.OLIVEIRAMARONEZE@cea.fr</a>></span> wrote:<br>
<br>
</div>
</div>
<font size="2"><span style="font-size:10pt;">
<div class="PlainText">Thanks, using those flags it shows useful information:<br>
<br>
- A call to i686-w64-mingw32-as, with a short command line, that succeeds;<br>
- A call to flexlink, also with a short command line, using a response <br>
file (@C:\cygwin32\tmp\camlresp0050ba);<br>
- And then several lines:<br>
<br>
** Use cygpath: true<br>
** Search path: .... (lots of directories, one per line)<br>
** Default libraries: ... (some -l<lib> followed by corresponding lines <br>
"** open: .../lib/<lib>.a")<br>
+ i686-w64-mingw32-gcc -mconsole -shared -Wl,-e_FlexDLLiniter@12 ... <br>
(lots of -I and -L, plus some extra flags, and this line is slightly <br>
larger than 8k characters)<br>
La ligne de commande est trop longue.<br>
** Fatal error: Error during linking<br>
<br>
So it's that call to i686-w64-mingw32-gcc that fails. Is there a way to <br>
use a response file for that command as well?<br>
<br>
<br>
Regards,<br>
<br>
<br>
On 07/06/2016 10:00 PM, Andreas Hauptmann wrote:<br>
> Hi,<br>
><br>
> On Wed, 6 Jul 2016 20:45:41 +0200<br>
> Andre Maroneze wrote:<br>
>> Has someone else also encountered this problem when compiling on<br>
>> Windows with a MinGW-based OCaml?<br>
> It's probably not your own command, that is too long, but a command<br>
> that is internally created by flexlink (or ocamlopt)<br>
> (See for example: <a href="https://github.com/alainfrisch/flexdll/issues/7">https://github.com/alainfrisch/flexdll/issues/7</a> )<br>
><br>
> Compile it with:<br>
><br>
> export FLEXLINKFLAGS='-v -v -v'<br>
> export OCAMLPARAM='_,verbose=1'<br>
> ocamlfind ocamlopt ...<br>
><br>
> then ocamlopt/ocamlc should print, which external commands they call to<br>
> stderr. And flexlink will also print some debug output.<br>
> With this information we can hopefully locate the point at which the<br>
> wrong command is generated.<br>
><br>
><br>
> _______________________________________________<br>
> wg-windows mailing list<br>
> wg-windows@lists.ocaml.org<br>
> <a href="http://lists.ocaml.org/listinfo/wg-windows">http://lists.ocaml.org/listinfo/wg-windows</a><br>
<br>
-- <br>
André Maroneze<br>
Ingénieur-chercheur CEA/LIST<br>
Laboratoire Sûreté et Sécurité des Logiciels<br>
<br>
_______________________________________________<br>
wg-windows mailing list<br>
wg-windows@lists.ocaml.org<br>
<a href="http://lists.ocaml.org/listinfo/wg-windows">http://lists.ocaml.org/listinfo/wg-windows</a><br>
</div>
</span></font>
</body>
</html>