All of lore.kernel.org
 help / color / mirror / Atom feed
From: Thomas Petazzoni <thomas.petazzoni@bootlin.com>
To: buildroot@busybox.net
Subject: [Buildroot] [git commit] snort: avoid detecting the host pcre
Date: Mon, 2 Apr 2018 09:16:22 +0200	[thread overview]
Message-ID: <20180402071628.5895F838E1@busybox.osuosl.org> (raw)

commit: https://git.buildroot.net/buildroot/commit/?id=f6d28852ab36ddcacfd37368f6b2c07d437cbc6b
branch: https://git.buildroot.net/buildroot/commit/?id=refs/heads/master

The pcre configure script does this:

if test "x$with_libpcre_libraries" != "xno"; then
    LDFLAGS="${LDFLAGS}  -L${with_libpcre_libraries}"
else
    LDFLAGS="${LDFLAGS} `pcre-config --libs`"
fi

So if you don't pass --with-libpcre-libraries, it calls pcre-config as
available in the PATH. So it picks up pcre-config from $(HOST_DIR) or
the system, which return results inappropriate for cross-compilation.

So, let's explicitly pass --with-libpcre-includes and
--with-libpcre-libraries to avoid those issues.

Fixes:

  http://autobuild.buildroot.net/results/3df11c48c8e2f795f478d1ee666dda9de19133d0/

Signed-off-by: Thomas Petazzoni <thomas.petazzoni@bootlin.com>
---
 package/snort/snort.mk | 2 ++
 1 file changed, 2 insertions(+)

diff --git a/package/snort/snort.mk b/package/snort/snort.mk
index 13f16b3b0f..568393468b 100644
--- a/package/snort/snort.mk
+++ b/package/snort/snort.mk
@@ -15,6 +15,8 @@ SNORT_DEPENDENCIES = libpcap libdnet daq pcre
 SNORT_AUTORECONF = YES
 
 SNORT_CONF_OPTS = \
+	--with-libpcre-includes=$(STAGING_DIR)/usr/include \
+	--with-libpcre-libraries=$(STAGING_DIR)/usr/lib \
 	--with-libpcap-includes=$(STAGING_DIR)/usr/include/pcap \
 	--disable-static-daq
 

                 reply	other threads:[~2018-04-02  7:16 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

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=20180402071628.5895F838E1@busybox.osuosl.org \
    --to=thomas.petazzoni@bootlin.com \
    --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.