Buildroot Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Peter Korsgaard <jacmet@uclibc.org>
To: buildroot@busybox.net
Subject: [Buildroot] Lighttpd and PCRE
Date: Wed, 17 Sep 2008 23:35:58 +0200	[thread overview]
Message-ID: <87ljxqsbep.fsf@macbook.be.48ers.dk> (raw)
In-Reply-To: <48D0CDD3.4070604@netcentral.co.uk> (Nick Peirson's message of "Wed\, 17 Sep 2008 10\:28\:51 +0100")

>>>>> "Nick" == Nick Peirson <nick@netcentral.co.uk> writes:

 Nick> Hi,

 Nick> I'm fairly new to buildroot and cross compiling in general and
 Nick> I've encountered some problems getting PCRE support enabled in
 Nick> lighttpd.

 Nick> Initially PCRE was failing to compile complaining of an unknown
 Nick> option -N, which I tracked down to the the line in the PCRE
 Nick> Makefile:

 Nick> STRIP = true -Not_stripping

Hmm, do you have BR2_STRIP_none set?

 Nick> Commenting this out allow PCRE to compile, however lighttpd
 Nick> failed to compile with an error regarding libc.so.6 conflicting
 Nick> with with libc.so.0. A quick find through my buildroot
 Nick> environment showed no instances of libc.so.6, however it was
 Nick> present on my host system. In an attempt to fix it I changed
 Nick> the line:

Yeah, that's caused by pcre-config returning /usr/lib instead of
$(STAGING_DIR)/usr/lib - I've fixed that now.

With those fixes pcre/lighttpd builds for me (arm9) - Does it still
not work for you?

-- 
Bye, Peter Korsgaard

  parent reply	other threads:[~2008-09-17 21:35 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-09-17  9:28 [Buildroot] Lighttpd and PCRE Nick Peirson
2008-09-17 15:03 ` Nick Peirson
2008-09-17 21:35 ` Peter Korsgaard [this message]
2008-09-18  7:59   ` Nick Peirson
2008-09-18  8:49     ` Nick Peirson
2008-09-18  8:58       ` Peter Korsgaard

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=87ljxqsbep.fsf@macbook.be.48ers.dk \
    --to=jacmet@uclibc.org \
    --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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox