All of lore.kernel.org
 help / color / mirror / Atom feed
From: Hamish Moffatt <hamish@cloud.net.au>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH] Update lighttpd package
Date: Wed, 2 Apr 2008 11:22:58 +1100	[thread overview]
Message-ID: <20080402002258.GD4616@cloud.net.au> (raw)
In-Reply-To: <DA636050-A5F5-4DA6-9D61-8B2C1FD153FE@valka.is>

On Tue, Apr 01, 2008 at 11:58:27PM +0000, Arnar Mar Sig wrote:
> This patch bumps lighttpd up to version 1.4.19 and adds the option to  
> compile with pcre support to enable mod_rewrite. Tested on AVR32

Your patch is badly damaged by word-wrap. Can you resend?

> +--- lighttpd-1.4.19-org/configure	2008-03-10 21:46:12.000000000 +0000
> ++++ lighttpd-1.4.19/configure	2008-03-31 06:58:41.000000000 +0000
> +@@ -23971,7 +23971,7 @@
> + { echo "$as_me:$LINENO: result: $WITH_PCRE" >&5
> + echo "${ECHO_T}$WITH_PCRE" >&6; }
> +
> +-if test "x$cross_compiling" = xno -a "$WITH_PCRE" != "no"; then
> ++if test "$WITH_PCRE" != "no"; then
> +   # Extract the first word of "pcre-config", so it can be a program  
> name with args.
> + set dummy pcre-config; ac_word=$2
> + { echo "$as_me:$LINENO: checking for $ac_word" >&5

Patching configure scripts directly is a bit of a hack. Can you edit
configure.in/.ac and run $(AUTORECONF) instead?


Hamish
-- 
Hamish Moffatt VK3SB <hamish@debian.org> <hamish@cloud.net.au>

      reply	other threads:[~2008-04-02  0:22 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-04-01 23:58 [Buildroot] [PATCH] Update lighttpd package Arnar Mar Sig
2008-04-02  0:22 ` Hamish Moffatt [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=20080402002258.GD4616@cloud.net.au \
    --to=hamish@cloud.net.au \
    --cc=buildroot@busybox.net \
    /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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.