public inbox for cygwin-apps@cygwin.com
 help / color / mirror / Atom feed
From: "Yaakov (Cygwin/X)" <yselkowitz@users.sourceforge.net>
To: cygwin-apps@cygwin.com
Subject: Re: [SECURITY] lighttpd
Date: Tue, 27 Mar 2012 11:11:00 -0000	[thread overview]
Message-ID: <4F71A066.9050201@users.sourceforge.net> (raw)
In-Reply-To: <4F719E0F.7030908@lapo.it>

On 2012-03-27 06:01, Lapo Luchini wrote:
> Yaakov (Cygwin/X) wrote:
>> The attached .cygport and patch WFM.  Do these not work for you?
>
> Nope, it's just the same as the 1.4.28 as found on CygPorts repository
> (and trivially-updated to 1.4.30).
>
> Didn't report it yet because I hadn't the time to check it on a
> different box, but here it goes:
>
> % cygport lighttpd-1.4.30-1 prep build
>>>> Preparing lighttpd-1.4.30-1
>>>> Unpacking source lighttpd-1.4.30.tar.xz
> *** Info: applying patch 1.4.28-no-undefined.patch:
> patching file src/Makefile.am
> Hunk #1 succeeded at 89 (offset 1 line).
>>>> Preparing working source directory
> *** Info: applying patch lighttpd-1.4.30-1.cygwin.patch:
> patching file CYGWIN-PATCHES/README
> patching file CYGWIN-PATCHES/setup.hint
>>>> Compiling lighttpd-1.4.30-1
> autoreconf-2.68: Entering directory `.'
> autoreconf-2.68: configure.ac: not using Gettext
> autoreconf-2.68: running: aclocal --force -I m4
> autoreconf-2.68: configure.ac: tracing
> autoreconf-2.68: running: libtoolize --copy --force
> libtoolize: putting auxiliary files in `.'.
> libtoolize: copying file `./ltmain.sh'
> libtoolize: putting macros in AC_CONFIG_MACRO_DIR, `m4'.
> libtoolize: copying file `m4/libtool.m4'
> libtoolize: copying file `m4/ltoptions.m4'
> libtoolize: copying file `m4/ltsugar.m4'
> libtoolize: copying file `m4/ltversion.m4'
> libtoolize: copying file `m4/lt~obsolete.m4'
> autoreconf-2.68: running: /usr/bin/autoconf-2.68 --force
> configure.ac:1: error: possibly undefined macro: dnl
>        If this token and others are legitimate, please use m4_pattern_allow.
>        See the Autoconf documentation.
> 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.


Yaakov

  reply	other threads:[~2012-03-27 11:11 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) [this message]
2012-03-29 14:59               ` Lapo Luchini
2012-03-29 18:39                 ` Yaakov (Cygwin/X)
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=4F71A066.9050201@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).