From: "Yaakov (Cygwin/X)" <yselkowitz@users.sourceforge.net>
To: cygwin-apps@cygwin.com
Subject: Re: [SECURITY] lighttpd
Date: Thu, 29 Mar 2012 18:39:00 -0000 [thread overview]
Message-ID: <4F74AC5B.5020207@users.sourceforge.net> (raw)
In-Reply-To: <4F7478A4.7010303@lapo.it>
On 2012-03-29 09:58, Lapo Luchini wrote:
> Yaakov (Cygwin/X) wrote:
>> BLODA?
>
> Not that I know of:
>
> WindowsDefender is deactivated (and I checked the service is not
> running), and only other stuff in the BLODA is "nVidia, some version"
> but I can't really do much to avoid that. I wonder.
So do I, because:
>>> configure.ac:57: error: possibly undefined macro: AC_CHECK_HEADERS
>>> configure.ac:71: error: possibly undefined macro: AC_DEFINE
>>> configure.ac:108: error: possibly undefined macro: AC_CHECK_LIB
>>> configure.ac:112: error: possibly undefined macro: AC_MSG_ERROR
>>> autoreconf-2.68: /usr/bin/autoconf-2.68 failed with exit status: 1
>>> *** ERROR: autoreconf failed
>>
>> Then something is wrong with your installation or environment. I'll
>> need your `cygcheck -srv' output.
>
> Same goes for a fresh install on real hardware (Win7 box in my office).
Nothing obvious in the cygcheck. But as these macros are part of
autoconf itself, if autoconf can't find them, it means that aclocal
silently failed. In any case, this is an issue with your system
(probably BLODA or rebase), not with cygport.
Yaakov
next prev parent reply other threads:[~2012-03-29 18:39 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-12-19 0:13 Yaakov (Cygwin/X)
2012-01-27 10:21 ` Yaakov (Cygwin/X)
2012-01-31 14:26 ` Corinna Vinschen
2012-02-03 15:41 ` Lapo Luchini
2012-02-27 21:33 ` Lapo Luchini
2012-02-28 2:01 ` Yaakov (Cygwin/X)
2012-03-27 11:02 ` Lapo Luchini
2012-03-27 11:11 ` Yaakov (Cygwin/X)
2012-03-29 14:59 ` Lapo Luchini
2012-03-29 18:39 ` Yaakov (Cygwin/X) [this message]
2012-08-15 1:53 ` Yaakov (Cygwin/X)
2012-10-09 10:56 ` Corinna Vinschen
2013-02-01 6:26 ` Yaakov
2013-02-04 10:01 ` Corinna Vinschen
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=4F74AC5B.5020207@users.sourceforge.net \
--to=yselkowitz@users.sourceforge.net \
--cc=cygwin-apps@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).