From: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH] dillo: avoid poisoned paths in configure
Date: Sat, 10 Jan 2015 12:36:13 +0100 [thread overview]
Message-ID: <20150110123613.6fecd66c@free-electrons.com> (raw)
In-Reply-To: <20150109123645.GA23533@vostro>
Dear Alex Suykov,
On Fri, 9 Jan 2015 14:36:45 +0200, Alex Suykov wrote:
> diff --git a/package/dillo/0002-usr-local-include.patch b/package/dillo/0002-usr-local-include.patch
> new file mode 100644
> index 0000000..eb27742
> --- /dev/null
> +++ b/package/dillo/0002-usr-local-include.patch
> @@ -0,0 +1,41 @@
> +Do not add (possibly poisoned) /usr/local/include and /usr/local/lib
> +to gcc and ld search paths in configure.
> +
> +With BR2_COMPILER_PARANOID_UNSAFE_PATH enabled, poisoned paths result
> +in hard errors, failing affected configure tests.
> +
> +Signed-off-by: Alex Suykov <alex.suykov@gmail.com>
Thanks. But can you make a patch that only changes configure.ac, and
not configure? This package is already autoreconf'ed. Also, please
adjust the comment above DILLO_AUTORECONF = YES in the .mk file to
mention that we also autoreconf for this new patch?
And additionally, please submit this patch to the upstream Dillo
developers!
Thanks,
Thomas
--
Thomas Petazzoni, CTO, Free Electrons
Embedded Linux, Kernel and Android engineering
http://free-electrons.com
next prev parent reply other threads:[~2015-01-10 11:36 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-01-09 12:36 [Buildroot] [PATCH] dillo: avoid poisoned paths in configure Alex Suykov
2015-01-10 11:36 ` Thomas Petazzoni [this message]
2015-01-10 13:33 ` Alex Suykov
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=20150110123613.6fecd66c@free-electrons.com \
--to=thomas.petazzoni@free-electrons.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox