From: Martin Jansa <martin.jansa@gmail.com>
To: openembedded-devel@lists.openembedded.org
Cc: yocto@mindchasers.com
Subject: Re: [meta-oe][PATCH 1/3] libhugetlbfs: use ARCH ppc/ppc64 for powerpc/powerpc64
Date: Wed, 16 Jul 2014 15:27:25 +0200 [thread overview]
Message-ID: <20140716132725.GX2433@jama> (raw)
In-Reply-To: <1405491841-24744-2-git-send-email-ting.liu@freescale.com>
[-- Attachment #1: Type: text/plain, Size: 1698 bytes --]
On Wed, Jul 16, 2014 at 02:23:59PM +0800, ting.liu@freescale.com wrote:
> From: Ting Liu <b28495@freescale.com>
>
> In recent libhugetlbfs source, powerpc/powerpc64 is changed back to
> ppc/ppc64 (to match with the output of `uname -a`).
>
> Update the recipe to avoid build issue for now.
>
> Signed-off-by: Ting Liu <b28495@freescale.com>
> ---
> .../libhugetlbfs/libhugetlbfs_git.bb | 5 ++++-
> 1 files changed, 4 insertions(+), 1 deletions(-)
>
> diff --git a/meta-oe/recipes-benchmark/libhugetlbfs/libhugetlbfs_git.bb b/meta-oe/recipes-benchmark/libhugetlbfs/libhugetlbfs_git.bb
> index e8e0787..e554b26 100644
> --- a/meta-oe/recipes-benchmark/libhugetlbfs/libhugetlbfs_git.bb
> +++ b/meta-oe/recipes-benchmark/libhugetlbfs/libhugetlbfs_git.bb
> @@ -25,7 +25,10 @@ S = "${WORKDIR}/git"
> COMPATIBLE_HOST = "(x86_64|powerpc|powerpc64|aarch64|arm).*-linux*"
>
> LIBARGS = "LIB32=${baselib} LIB64=${baselib}"
> -EXTRA_OEMAKE = "'ARCH=${TARGET_ARCH}' 'OPT=${CFLAGS}' 'CC=${CC}' ${LIBARGS} V=1"
> +LIBHUGETLBFS_ARCH = "${TARGET_ARCH}"
> +LIBHUGETLBFS_ARCH_powerpc = "ppc"
> +LIBHUGETLBFS_ARCH_powerpc64 = "ppc64"
> +EXTRA_OEMAKE = "'ARCH=${LIBHUGETLBFS_ARCH}' 'OPT=${CFLAGS}' 'CC=${CC}' ${LIBARGS} V=2"
> PARALLEL_MAKE = ""
> CFLAGS += "-fexpensive-optimizations -frename-registers -fomit-frame-pointer -g0"
libhugetlbfs is currently failing with
http://logs.nslu2-linux.org/buildlogs/oe/world/log.dependencies.20140714_130534.log/3_min/failed/libhugetlbfs.log
and it also fails to build for qemux86-64 (log in last world status
e-mail).
Can we please fix it first?
--
Martin 'JaMa' Jansa jabber: Martin.Jansa@gmail.com
[-- Attachment #2: Digital signature --]
[-- Type: application/pgp-signature, Size: 188 bytes --]
next prev parent reply other threads:[~2014-07-16 13:27 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-07-16 6:23 [meta-oe][PATCH 0/3] libhugetlbfs and luajit update ting.liu
2014-07-16 6:23 ` [meta-oe][PATCH 1/3] libhugetlbfs: use ARCH ppc/ppc64 for powerpc/powerpc64 ting.liu
2014-07-16 13:27 ` Martin Jansa [this message]
2014-07-17 7:09 ` ting.liu
2014-07-23 8:51 ` Martin Jansa
2014-07-23 10:19 ` ting.liu
2014-07-16 6:24 ` [meta-oe][PATCH 2/3] libhugetlbfs: not build obj32 for powerpc64 ting.liu
2014-07-16 6:24 ` [meta-oe][PATCH 3/3] luajit: replace MACHINEOVERRIDES fslmachine with qoriq-ppc ting.liu
2014-07-16 7:14 ` Martin Jansa
2014-07-16 8:48 ` ting.liu
2014-07-16 13:43 ` Martin Jansa
2014-07-16 17:58 ` Martin Jansa
2014-12-09 10:31 ` [meta-oe][PATCH 0/3] libhugetlbfs and luajit update 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=20140716132725.GX2433@jama \
--to=martin.jansa@gmail.com \
--cc=openembedded-devel@lists.openembedded.org \
--cc=yocto@mindchasers.com \
/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