From: Yi Zhao <yi.zhao@windriver.com>
To: <openembedded-devel@lists.openembedded.org>, <martin.jansa@gmail.com>
Subject: Re: [meta-oe][PATCH 1/3] luajit: fix build failure for multilib
Date: Fri, 12 Jun 2015 16:14:35 +0800 [thread overview]
Message-ID: <557A94EB.6090908@windriver.com> (raw)
In-Reply-To: <20150611103956.GA2394@jama>
在 2015年06月11日 18:39, Martin Jansa 写道:
> On Thu, Jun 04, 2015 at 03:48:11PM +0800, Yi Zhao wrote:
>> Fix libdir in Makefile
>>
>> Signed-off-by: Yi Zhao <yi.zhao@windriver.com>
>> ---
>> meta-oe/recipes-devtools/luajit/luajit_2.0.3.bb | 4 ++--
>> 1 file changed, 2 insertions(+), 2 deletions(-)
>>
>> diff --git a/meta-oe/recipes-devtools/luajit/luajit_2.0.3.bb b/meta-oe/recipes-devtools/luajit/luajit_2.0.3.bb
>> index 48137e3..f3235c9 100644
>> --- a/meta-oe/recipes-devtools/luajit/luajit_2.0.3.bb
>> +++ b/meta-oe/recipes-devtools/luajit/luajit_2.0.3.bb
>> @@ -16,8 +16,8 @@ inherit pkgconfig binconfig
>> BBCLASSEXTEND = "native"
>>
>> do_configure_prepend() {
>> - sed -i -e s:/usr/local:${prefix}:g ${S}/Makefile
>> - sed -i -e s:/lib$:${base_libdir}:g ${S}/Makefile
>> + sed -i 's:PREFIX= /usr/local:PREFIX= ${prefix}:g' ${S}/Makefile
>> + sed -i 's:MULTILIB= lib:MULTILIB= ${base_libdir}:g' ${S}/Makefile
>> }
> This seems to break qemux86 build
>
> | ==== Successfully installed LuaJIT 2.0.3 to /home/jenkins/oe/world/shr-core/tmp-glibc/sysroots/x86_64-linux/usr ====
> | rmdir: failed to remove `/home/jenkins/oe/world/shr-core/tmp-glibc/work/x86_64-linux/luajit-native/2.0.3-r0/image/home/jenkins/oe/world/shr-core/tmp-glibc/sysroots/x86_64-linux/usr/lib/lua/5.*': No such file or directory
> | rmdir: failed to remove `/home/jenkins/oe/world/shr-core/tmp-glibc/work/x86_64-linux/luajit-native/2.0.3-r0/image/home/jenkins/oe/world/shr-core/tmp-glibc/sysroots/x86_64-linux/usr/lib/lua': No such file or directory
> | WARNING: exit code 1 from a shell command.
> | ERROR: Function failed: do_install (log file is located at /home/jenkins/oe/world/shr-core/tmp-glibc/work/x86_64-linux/luajit-native/2.0.3-r0/temp/log.do_install.31954)
> NOTE: recipe luajit-native-2.0.3-r0: task do_install: Failed
> ERROR: Task 31965 (virtual:native:/home/jenkins/oe/world/shr-core/meta-openembedded/meta-oe/recipes-devtools/luajit/luajit_2.0.3.bb, do_install) failed with exit code '1'
>
Thanks, Martin. I can reproduce it. A patch will be sent later.
Yi
>>
>> EXTRA_OEMAKE = 'CROSS=${HOST_PREFIX} \
>> --
>> 1.7.9.5
>>
>> --
>> _______________________________________________
>> Openembedded-devel mailing list
>> Openembedded-devel@lists.openembedded.org
>> http://lists.openembedded.org/mailman/listinfo/openembedded-devel
next prev parent reply other threads:[~2015-06-12 8:14 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-06-04 7:48 [meta-oe][PATCH 0/3] 3 fixes for multilib Yi Zhao
2015-06-04 7:48 ` [meta-oe][PATCH 1/3] luajit: fix build failure " Yi Zhao
2015-06-11 10:39 ` Martin Jansa
2015-06-12 8:14 ` Yi Zhao [this message]
2015-06-04 7:48 ` [meta-oe][PATCH 2/3] nodejs: " Yi Zhao
2015-06-04 7:48 ` [meta-oe][PATCH 3/3] llvm: fix libdir " Yi Zhao
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=557A94EB.6090908@windriver.com \
--to=yi.zhao@windriver.com \
--cc=martin.jansa@gmail.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