From: Romain Naour <romain.naour@openwide.fr>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH] package/pcre: install headers in legacy location
Date: Sun, 14 Dec 2014 14:32:35 +0100 [thread overview]
Message-ID: <548D9173.3070905@openwide.fr> (raw)
In-Reply-To: <1418490513-10957-1-git-send-email-yann.morin.1998@free.fr>
Hi Yann, all,
Le 13/12/2014 18:08, Yann E. MORIN a ?crit :
> nmap is looking for pcre headers in pcre/pcre.h which our current
> version of pcre does not populates.
>
> So, just create those as symlinks to the actual headers.
>
> Signed-off-by: "Yann E. MORIN" <yann.morin.1998@free.fr>
> Cc: Romain Naour <romain.naour@openwide.fr>
>
> ---
> Note: this is not fixing anything for now, because the error in nmap is
> hidden by another error. But this is relaticvely easy to fix, so here we
> go... ;-)
> ---
Confirmed by the nmap's configure output before this patch...
checking pcre/pcre.h usability... no
checking pcre/pcre.h presence... no
checking for pcre/pcre.h... no
... and after this patch:
checking pcre/pcre.h usability... yes
checking pcre/pcre.h presence... yes
checking for pcre/pcre.h... yes
But it seems that the bundled nmap's libpcre is not build even with this patch.
In nmap's Makefile, "pcre_build" is not part of "all" target.
But for consistency with --with-libpcre="$(STAGING_DIR)/usr", let's the pcre
checking works...
(Maybe some other packages are looking for pcre in /usr/include/pcre/ directory).
So;
Acked-by: Romain Naour <romain.naour@openwide.fr>
Best regards,
--
Romain Naour
OPEN WIDE Ing?nierie - Paris
23/25, rue Daviel| 75013 PARIS
http://ingenierie.openwide.fr
Le blog des technologies libres et embarqu?es :
http://www.linuxembedded.fr
next prev parent reply other threads:[~2014-12-14 13:32 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-12-13 17:08 [Buildroot] [PATCH] package/pcre: install headers in legacy location Yann E. MORIN
2014-12-14 13:32 ` Romain Naour [this message]
2014-12-21 22:19 ` Thomas Petazzoni
2014-12-23 11:21 ` Yann E. MORIN
2014-12-23 11:39 ` Thomas Petazzoni
2014-12-23 12:54 ` Yann E. MORIN
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=548D9173.3070905@openwide.fr \
--to=romain.naour@openwide.fr \
--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.