From: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH 1/1] package/php: Add -lpthread to detect unixodbc for static build
Date: Sun, 31 May 2015 10:33:06 +0200 [thread overview]
Message-ID: <20150531103306.499b604f@free-electrons.com> (raw)
In-Reply-To: <1433019093-16740-1-git-send-email-bernd.kuhls@t-online.de>
Dear Bernd Kuhls,
On Sat, 30 May 2015 22:51:33 +0200, Bernd Kuhls wrote:
> Fixes
> http://autobuild.buildroot.net/results/157/157749f8b44bc02fbed0232a2b33137aba495134/
> http://autobuild.buildroot.net/results/df4/df4e2ea098b0126867455af1891837c6d7d99a92/
>
> Signed-off-by: Bernd Kuhls <bernd.kuhls@t-online.de>
> ---
> package/php/php.mk | 3 +++
> 1 file changed, 3 insertions(+)
>
> diff --git a/package/php/php.mk b/package/php/php.mk
> index 9be07d5..8e79c49 100644
> --- a/package/php/php.mk
> +++ b/package/php/php.mk
> @@ -225,6 +225,9 @@ endif
> ifeq ($(BR2_PACKAGE_PHP_EXT_PDO_UNIXODBC),y)
> PHP_CONF_OPTS += --with-pdo-odbc=unixODBC,$(STAGING_DIR)/usr
> PHP_DEPENDENCIES += unixodbc
> +ifeq ($(BR2_STATIC_LIBS),y)
> +PHP_CONF_ENV += LIBS='-lpthread'
What happens if you have multiple of such occurrences? You will pass
LIBS='-lfoo' LIBS='-lbar', etc.
Shouldn't we instead do:
PHP_LIBS += -lpthread
and then later, a single PHP_CONF_ENV += LIBS=$(PHP_LIBS)
Also, it's a shame unixodbc doesn't use pkg-config. It installs its own
odbc-config, but I guess it's compiled for the target, and most likely
returns results that are inappropriate for cross compilation.
Thomas
--
Thomas Petazzoni, CTO, Free Electrons
Embedded Linux, Kernel and Android engineering
http://free-electrons.com
prev parent reply other threads:[~2015-05-31 8:33 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-05-30 20:51 [Buildroot] [PATCH 1/1] package/php: Add -lpthread to detect unixodbc for static build Bernd Kuhls
2015-05-31 8:33 ` Thomas Petazzoni [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=20150531103306.499b604f@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 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.