From: "Kizito Porta Balanyà" <kfeina@gmail.com>
To: cygwin@cygwin.com
Subject: Re: Monit Compilation Errors
Date: Tue, 23 Jan 2018 11:43:00 -0000 [thread overview]
Message-ID: <CAO2ddnYMtH--zeCtMuDVw_WfS+fZ+BCVPOdSi4kV3SEc4KGTdQ@mail.gmail.com> (raw)
In-Reply-To: <p3qq3g$jj7$1@blaine.gmane.org>
2018-01-18 19:47 GMT+01:00 szgyg <szgyg@ludens.elte.hu>:
> On 2018-01-18, BGINFO4X wrote:
> > 2018-01-17 20:12 GMT+01:00 szgyg <xxxxx@xxxxxxxxxxxxxx>:
> ^^^^^^^^^^^^^^^^^^^^
> Please don't quote raw email addresses.
>
> > Finally, fter switching to the 32bits cygwin version (-m32 in cygwin64
> > generated more errors), and modifying Lync.c , monit has been compiled
> > again for this version.
>
> Congrats. (-m32 is not supported on cygwin, don't use it.)
>
>
> > What are the next steps? Try to compile for the 64bits version? Both
> > packages are required or only one? In that case, the 64bits cygwin
> > installer can install the 32 bits monit version?
>
> You can't mix 32 and 64-bit programs. If you want to use it in 64-bit
> cygwin, you should recompile it.
>
> s
>
Which is the best way to compile a program for both platforms (32-64 bits)
to release a cygwin package?
Thanks.
>
>
> --
> 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
>
>
--
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
next prev parent reply other threads:[~2018-01-23 11:43 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-01-15 12:22 Kizito Porta Balanyà
2018-01-15 14:27 ` Ken Brown
2018-01-15 16:33 ` BGINFO4X
2018-01-15 21:07 ` szgyg
2018-01-15 22:19 ` Brian Inglis
2018-01-17 19:15 ` szgyg
2018-01-18 14:48 ` BGINFO4X
2018-01-18 18:49 ` szgyg
2018-01-23 11:43 ` Kizito Porta Balanyà [this message]
2018-01-23 13:17 ` Marco Atzeri
2018-01-23 13:25 ` BGINFO4X
2018-01-23 14:16 ` Marco Atzeri
2018-01-23 18:28 ` Achim Gratz
2018-01-23 18:24 ` Achim Gratz
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=CAO2ddnYMtH--zeCtMuDVw_WfS+fZ+BCVPOdSi4kV3SEc4KGTdQ@mail.gmail.com \
--to=kfeina@gmail.com \
--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).