From: Arnout Vandecappelle <arnout@mind.be>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH] package/efl/libevas: remove unsafe paths
Date: Tue, 8 Sep 2015 17:29:21 +0200 [thread overview]
Message-ID: <55EEFED1.7010700@mind.be> (raw)
In-Reply-To: <1441723349-31061-1-git-send-email-Vincent.Riera@imgtec.com>
On 08-09-15 16:42, Vicente Olivert Riera wrote:
> Fixes:
>
> http://autobuild.buildroot.net/results/7f2/7f2baef97c4ff3b9111becc1e0b79780c6e9db6f/
>
> Signed-off-by: Vicente Olivert Riera <Vincent.Riera@imgtec.com>
> ---
> package/efl/libevas/libevas.mk | 7 +++++++
> 1 files changed, 7 insertions(+), 0 deletions(-)
>
> diff --git a/package/efl/libevas/libevas.mk b/package/efl/libevas/libevas.mk
> index 8113162..9ffedce 100644
> --- a/package/efl/libevas/libevas.mk
> +++ b/package/efl/libevas/libevas.mk
> @@ -17,6 +17,13 @@ LIBEVAS_DEPENDENCIES = host-pkgconf zlib libeina freetype
> HOST_LIBEVAS_DEPENDENCIES = \
> host-pkgconf host-zlib host-libeina \
> host-freetype host-libpng host-libjpeg
> +
> +define LIBEVAS_REMOVE_UNSAFE_PATHS
> +$(SED) 's#-I/usr/include##g' $(@D)/configure
We currently have 1 package using #, 2 packages using ^, and 11 packages using
%. So let's stick to %.
> +endef
> +LIBEVAS_POST_PATCH_HOOKS += LIBEVAS_REMOVE_UNSAFE_PATHS
> +HOST_LIBEVAS_POST_PATCH_HOOKS += LIBEVAS_REMOVE_UNSAFE_PATHS
For the host it's not unsafe... Useless, but not unsafe.
Regards,
Arnout
> +
> HOST_LIBEVAS_CONF_OPTS += \
> --enable-image-loader-png \
> --enable-image-loader-jpeg \
>
--
Arnout Vandecappelle arnout at mind be
Senior Embedded Software Architect +32-16-286500
Essensium/Mind http://www.mind.be
G.Geenslaan 9, 3001 Leuven, Belgium BE 872 984 063 RPR Leuven
LinkedIn profile: http://www.linkedin.com/in/arnoutvandecappelle
GPG fingerprint: 7493 020B C7E3 8618 8DEC 222C 82EB F404 F9AC 0DDF
prev parent reply other threads:[~2015-09-08 15:29 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-09-08 14:42 [Buildroot] [PATCH] package/efl/libevas: remove unsafe paths Vicente Olivert Riera
2015-09-08 15:29 ` Arnout Vandecappelle [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=55EEFED1.7010700@mind.be \
--to=arnout@mind.be \
--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