From: Martin Jansa <martin.jansa@gmail.com>
To: openembedded-devel@lists.openembedded.org
Cc: Anders Darander <anders@chargestorm.se>
Subject: Re: [meta-oe] [PATCH 1/1] breakpad: install static library
Date: Wed, 1 Oct 2014 17:19:52 +0200 [thread overview]
Message-ID: <20141001151952.GD25706@jama> (raw)
In-Reply-To: <c3982a9e7a7182cfb3f0147477202f0c7b15858a.1411996185.git.anders@chargestorm.se>
[-- Attachment #1: Type: text/plain, Size: 2477 bytes --]
On Mon, Sep 29, 2014 at 03:10:30PM +0200, Anders Darander wrote:
> In order to build against breakpad when using an SDK, we need to also package
> libbreakpad_client.a.
>
> The SDK will then need to add breakpad-staticdev to TOOLCHAIN_TARGET_TASK.
Fails in world builds:
| ( cd '/home/jenkins/oe/world/shr-core/tmp-glibc/work/armv5te-oe-linux-gnueabi/breakpad/svn-r0/image/usr/lib' && arm-oe-linux-gnueabi-ranlib libbreakpad.a )
| ( cd '/home/jenkins/oe/world/shr-core/tmp-glibc/work/armv5te-oe-linux-gnueabi/breakpad/svn-r0/image/usr/lib' && arm-oe-linux-gnueabi-ranlib libbreakpad_client.a )
| make[1]: Leaving directory `/home/jenkins/oe/world/shr-core/tmp-glibc/work/armv5te-oe-linux-gnueabi/breakpad/svn-r0/build'
| install: cannot stat `/home/jenkins/oe/world/shr-core/tmp-glibc/work/armv5te-oe-linux-gnueabi/breakpad/svn-r0/trunk/src/client/linux/libbreakpad_client.a': 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/armv5te-oe-linux-gnueabi/breakpad/svn-r0/temp/log.do_install.11600)
NOTE: recipe breakpad-svn-r0: task do_install: Failed
I guess it should be installed from ${B}
Please re-test and re-send.
>
> Signed-off-by: Anders Darander <anders@chargestorm.se>
> ---
> meta-oe/recipes-devtools/breakpad/breakpad_svn.bb | 3 +++
> 1 file changed, 3 insertions(+)
>
> diff --git a/meta-oe/recipes-devtools/breakpad/breakpad_svn.bb b/meta-oe/recipes-devtools/breakpad/breakpad_svn.bb
> index 2c5941d..571e1d3 100644
> --- a/meta-oe/recipes-devtools/breakpad/breakpad_svn.bb
> +++ b/meta-oe/recipes-devtools/breakpad/breakpad_svn.bb
> @@ -56,6 +56,9 @@ do_install_append() {
>
> install -d ${D}${includedir}/breakpad/third_party/lss
> install -m 0644 ${S}/src/third_party/lss/linux_syscall_support.h ${D}${includedir}/breakpad/third_party/lss/linux_syscall_support.h
> +
> + install -d ${D}${libdir}
> + install -m 0644 ${S}/src/client/linux/libbreakpad_client.a ${D}${libdir}/libbreakpad_client.a
> }
>
> PACKAGES =+ "${PN}-minidump-upload ${PN}-sym-upload"
> --
> 2.1.1
>
> --
> _______________________________________________
> Openembedded-devel mailing list
> Openembedded-devel@lists.openembedded.org
> http://lists.openembedded.org/mailman/listinfo/openembedded-devel
--
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-10-01 15:18 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-09-29 13:10 [meta-oe] [PATCH 0/1] Make it possible to use breakpad in an SDK Anders Darander
2014-09-29 13:10 ` [meta-oe] [PATCH 1/1] breakpad: install static library Anders Darander
2014-10-01 15:19 ` Martin Jansa [this message]
2014-10-02 9:47 ` Anders Darander
2014-10-03 7:09 ` Anders Darander
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=20141001151952.GD25706@jama \
--to=martin.jansa@gmail.com \
--cc=anders@chargestorm.se \
--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