From: Eric Blake <eblake@redhat.com>
To: cygwin@cygwin.com
Cc: kfeina@gmail.com
Subject: Re: vsnprintf error compiling
Date: Tue, 25 Aug 2015 12:31:00 -0000 [thread overview]
Message-ID: <55DC602C.20901@redhat.com> (raw)
In-Reply-To: <CAO2ddnZ-kj0ZukKopMaTzt8kHzLQWqMRLCTi7d8_z2+6tiq2vw@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 1011 bytes --]
On 08/25/2015 05:29 AM, Kizito Porta Balanyà wrote:
> Hello,
>
> I'm trying to build the new version of monit (5.14) in cygwin, but I
> get the following error executing configure:
>
> autoreconf -i -f && automake -acf && ./configure
>
> checking vsnprintf is c99 conformant... configure: error: in
> `/tmp/monit-5.14/libmonit':
> configure: error: vsnprintf does not conform to c99
Show the relevant portion of config.log, that shows the program that
monit attempted to compile, and the compiler error. Most likely it is a
bug in monit's configure.ac, and not in cygwin.
>
> Is cygwin GCC c99 conformant? I'm totally lost, perhaps what I say has
> no sense.
Yes, cygwin's compilation of vsnprintf is supposed to be c99 compliant.
But without seeing why monit claims it is not, I can't state
definitively if that is the case, or if monit has turned up an actual bug.
--
Eric Blake eblake redhat com +1-919-301-3266
Libvirt virtualization library http://libvirt.org
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 604 bytes --]
next prev parent reply other threads:[~2015-08-25 12:31 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-08-25 11:29 Kizito Porta Balanyà
2015-08-25 12:31 ` Eric Blake [this message]
2015-08-25 15:41 ` Kizito Porta Balanyà
2015-08-25 16:00 ` Marco Atzeri
2015-08-25 16:25 ` cyg Simple
2015-08-25 16:56 ` BGINFO4X
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=55DC602C.20901@redhat.com \
--to=eblake@redhat.com \
--cc=cygwin@cygwin.com \
--cc=kfeina@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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).