From: Earnie Boyd <earnie@users.sourceforge.net>
To: cygwin@cygwin.com
Subject: Re: Compilation issue after upgrading cygwin from 1.7.9 to 1.7.16
Date: Tue, 04 Sep 2012 16:06:00 -0000 [thread overview]
Message-ID: <CA+sc5mney3bbe7a5DrTDeUbT4jDn6V7ORsRDv9ViKd_JvFNgDg@mail.gmail.com> (raw)
In-Reply-To: <50461DD6.3030109@gmail.com>
On Tue, Sep 4, 2012 at 11:27 AM, marco atzeri wrote:
> On 9/4/2012 4:42 PM, Caporossi Jérôme wrote:
>>
>> Hi,
>>
>> I've got a compilation issue after upgrading Cygwin.
>> I am working with Metaware IDE, calling a dedicated compiler/linker called
>> mcc.
>>
>> All the makefiles are generated by Metaware and the compilation is
>> launched through gmake.
>
>
> Should you ask Synopsis ? mcc is not discussed here.
Even so, using it within the Cygwin environment.
>
>
>>
>> In the makefile, mcc arguments is quite long (the mcc line is up to 10036
>> characters).
>> Then when launching the compilation, the following error is raised:
>>
>> (C:\ARC\MetaWare\arc\bin\mcc:) No files specified.
>>
>> It is like if the mcc cmd was too long and is truncated before the source
>> file to be specified.
This may be a Windows limitation and depends on how the processes are executed.
--
Earnie
-- https://sites.google.com/site/earnieboyd
--
Problem reports: http://cygwin.com/problems.html
FAQ: http://cygwin.com/faq/
Documentation: http://cygwin.com/docs.html
Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple
prev parent reply other threads:[~2012-09-04 16:06 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-09-04 14:43 Caporossi Jérôme
2012-09-04 15:27 ` marco atzeri
2012-09-04 16:06 ` Earnie Boyd [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=CA+sc5mney3bbe7a5DrTDeUbT4jDn6V7ORsRDv9ViKd_JvFNgDg@mail.gmail.com \
--to=earnie@users.sourceforge.net \
--cc=cygwin@cygwin.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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).