From: akuster808 <akuster808@gmail.com>
To: openembedded-devel@lists.openembedded.org
Cc: Otavio Salvador <otavio@ossystems.com.br>
Subject: Re: [meta-oe][PATCH] php: Fix native build due mistakenly linking against host's iconv
Date: Wed, 27 Aug 2014 19:37:59 -0700 [thread overview]
Message-ID: <53FE9607.3000203@gmail.com> (raw)
In-Reply-To: <1408909187-29642-1-git-send-email-otavio@ossystems.com.br>
Acked-by: Armin Kuster <akuster808@gmail.com>
On 08/24/2014 12:39 PM, Otavio Salvador wrote:
> The configure script has mistakenly choose to enable iconv support,
> due host to provide it, adding '/usr/lib' to the linking flags and
> failing as:
>
> ,----[ Linking error while testing 'fork' support ]
> | conftest.c:268: warning: conflicting types for built-in function 'fork'
> | .../build/tmp/sysroots/x86_64-linux/usr/lib/libxml2.so:
> | undefined reference to `gzopen64@ZLIB_1.2.3.3'
> | collect2: ld returned 1 exit status
> `----
>
> This patch disables iconv support for native builds fixing the error.
>
> Signed-off-by: Otavio Salvador <otavio@ossystems.com.br>
> ---
> meta-oe/recipes-devtools/php/php.inc | 1 +
> 1 file changed, 1 insertion(+)
>
> diff --git a/meta-oe/recipes-devtools/php/php.inc b/meta-oe/recipes-devtools/php/php.inc
> index 030c090..6bdae78 100644
> --- a/meta-oe/recipes-devtools/php/php.inc
> +++ b/meta-oe/recipes-devtools/php/php.inc
> @@ -35,6 +35,7 @@ EXTRA_OECONF = "--enable-mbstring \
> "
> EXTRA_OECONF_virtclass-native = " \
> --with-zlib=${STAGING_LIBDIR_NATIVE}/.. \
> + --without-iconv \
> ${COMMON_EXTRA_OECONF} \
> "
>
>
next prev parent reply other threads:[~2014-08-28 2:38 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-08-24 19:39 [meta-oe][PATCH] php: Fix native build due mistakenly linking against host's iconv Otavio Salvador
2014-08-24 19:45 ` Otavio Salvador
2014-08-24 20:36 ` Martin Jansa
2014-08-28 2:37 ` akuster808 [this message]
2014-08-28 9:26 ` Martin Jansa
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=53FE9607.3000203@gmail.com \
--to=akuster808@gmail.com \
--cc=openembedded-devel@lists.openembedded.org \
--cc=otavio@ossystems.com.br \
/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