From: Hans Ole Rafaelsen <hans@simula.no>
To: matthieu.dubuget@gmail.com
Cc: caml-list@inria.fr
Subject: Re: [Caml-list] Linking fails for native version of 3.11 under MinGW when using large number of modules
Date: Sun, 24 May 2009 22:15:30 +0200 [thread overview]
Message-ID: <4A19AAE2.1000402@simula.no> (raw)
In-Reply-To: <4A19A6D0.1060809@gmail.com>
Matthieu Dubuget wrote:
> Hans Ole Rafaelsen a écrit :
>
>> Matthieu Dubuget wrote:
>>
>>> Hans Ole Rafaelsen a écrit :
>>>
>>>
>>>> I'm able to include a large number of my own modules (tested
>>>> with long names), so it does not seem to be the length of the command
>>>> line arguments that is causing the problems.
>>>>
>>>>
>
> Oups. Sorry: I did not read your first post carefully before answering...
>
> Salutations
>
> Matt
>
Thanks for the tip anyway. I had forgotten that flexlink is involved and
might be another suspect. Anyway, I upgraded this to version 0.18, but
the problem remains.
--
Hans Ole
prev parent reply other threads:[~2009-05-24 20:15 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-05-24 14:23 Hans Ole Rafaelsen
2009-05-24 18:44 ` [Caml-list] " Matthieu Dubuget
2009-05-24 19:03 ` Hans Ole Rafaelsen
2009-05-24 19:58 ` Matthieu Dubuget
2009-05-24 20:15 ` Hans Ole Rafaelsen [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=4A19AAE2.1000402@simula.no \
--to=hans@simula.no \
--cc=caml-list@inria.fr \
--cc=matthieu.dubuget@gmail.com \
/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