Buildroot Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Max Filippov <jcmvbkbc@gmail.com>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH] php: fix wrong -L and -I paths added by iconv tests
Date: Sat, 12 Apr 2014 14:37:02 +0400	[thread overview]
Message-ID: <1397299022-31655-1-git-send-email-jcmvbkbc@gmail.com> (raw)

The commit f2a2c4cce "php: fix iconv related build failure" have removed
logic that used to detect the correct PHP_ICONV_PREFIX with an
assumption that "ICONV_DIR is fine". Currently the ICONV_DIR is only
fine when BR2_PACKAGE_LIBICONV is set to 'y', otherwise php is
configured with plain --with-iconv. This results in empty
PHP_ICONV_PREFIX and -L/lib and -I/include added to CFLAGS and LDFLAGS
respectively, which leads to build failures when e.g. /lib contains
files with the same names as the toolchain sysroot needed for linking.

Fix that by always specifying --with-iconv=$(STAGING_DIR)/usr when iconv
is configured for PHP.

Fixes: http://autobuild.buildroot.net/results/959/959b77fa2c1f13b1958b234803437e09734e882e/

Cc: Gustavo Zacarias <gustavo@zacarias.com.ar>
Cc: Peter Korsgaard <peter@korsgaard.com>
Signed-off-by: Max Filippov <jcmvbkbc@gmail.com>
---
 package/php/php.mk |    4 +---
 1 files changed, 1 insertions(+), 3 deletions(-)

diff --git a/package/php/php.mk b/package/php/php.mk
index ba1200b..bb86829 100644
--- a/package/php/php.mk
+++ b/package/php/php.mk
@@ -108,11 +108,9 @@ ifeq ($(BR2_PACKAGE_PHP_EXT_GETTEXT),y)
 endif
 
 ifeq ($(BR2_PACKAGE_PHP_EXT_ICONV),y)
-ifeq ($(BR2_PACKAGE_LIBICONV),y)
 	PHP_CONF_OPT += --with-iconv=$(STAGING_DIR)/usr
+ifeq ($(BR2_PACKAGE_LIBICONV),y)
 	PHP_DEPENDENCIES += libiconv
-else
-	PHP_CONF_OPT += --with-iconv
 endif
 endif
 
-- 
1.7.7.6

             reply	other threads:[~2014-04-12 10:37 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-04-12 10:37 Max Filippov [this message]
2014-04-12 11:14 ` [Buildroot] [PATCH] php: fix wrong -L and -I paths added by iconv tests Thomas Petazzoni
2014-04-12 11:38   ` Gustavo Zacarias
2014-04-20 17:05 ` Thomas Petazzoni

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=1397299022-31655-1-git-send-email-jcmvbkbc@gmail.com \
    --to=jcmvbkbc@gmail.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