From: Lu Chong <Chong.Lu@windriver.com>
To: <openembedded-devel@lists.openembedded.org>
Subject: Re: [PATCH meta-networking] modphp: enable endian check
Date: Tue, 10 Dec 2013 17:34:05 +0800 [thread overview]
Message-ID: <52A6E00D.5080306@windriver.com> (raw)
In-Reply-To: <1386664325-15756-1-git-send-email-Chong.Lu@windriver.com>
Please ignore this one. I will resend.
Best Regards
Chong
On 12/10/2013 04:32 PM, Chong.Lu@windriver.com wrote:
> From: Chong Lu <Chong.Lu@windriver.com>
>
> Previously, modphp estimates endian on host rather than checks it on
> target. If the host is little-endian and the target is big-endian,
> modphp claims that endian is little. As a result, a memory location
> that it is not allowed to access when calling libphp5.so module on
> target. It will occur segmentation fault.
> This patch enables endian check support for modphp.
>
> Signed-off-by: Chong Lu <Chong.Lu@windriver.com>
> ---
> recipes-php/modphp/modphp5.inc | 2 ++
> 1 file changed, 2 insertions(+)
>
> diff --git a/recipes-php/modphp/modphp5.inc b/recipes-php/modphp/modphp5.inc
> index 19f1be9..425faa2 100644
> --- a/recipes-php/modphp/modphp5.inc
> +++ b/recipes-php/modphp/modphp5.inc
> @@ -44,6 +44,8 @@ EXTRA_OECONF = "--with-apxs2=${STAGING_BINDIR_CROSS}/apxs \
> --enable-mbstring \
> --with-config-file-path=${sysconfdir}/php/apache2-php5"
>
> +EXTRA_OECONF += "${@base_conditional('SITEINFO_ENDIANNESS', 'le', 'ac_cv_c_bigendian_php=no', 'ac_cv_c_bigendian_php=yes', d)}"
> +
> PACKAGECONFIG ??= "mysql"
> PACKAGECONFIG[mysql] = "--with-mysqli=${STAGING_BINDIR_CROSS}/mysql_config,--without-mysqli,mysql5"
> PACKAGECONFIG[pgsql] = "--with-pgsql=${STAGING_DIR_TARGET}${exec_prefix},--without-pgsql,mysql5"
prev parent reply other threads:[~2013-12-10 9:34 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-12-10 8:32 [PATCH meta-networking] modphp: enable endian check Chong.Lu
2013-12-10 9:34 ` Lu Chong [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=52A6E00D.5080306@windriver.com \
--to=chong.lu@windriver.com \
--cc=openembedded-devel@lists.openembedded.org \
/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