From: Koen Kooi <k.kooi@student.utwente.nl>
To: openembedded-devel@lists.openembedded.org
Subject: Re: Request for branch merge
Date: Sat, 03 Apr 2010 09:21:20 +0200 [thread overview]
Message-ID: <hp6q9g$di5$1@dough.gmane.org> (raw)
In-Reply-To: <1270244497.4993.185.camel@rex>
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
On 02-04-10 23:41, Richard Purdie wrote:
> On Fri, 2010-04-02 at 16:35 +0200, Koen Kooi wrote:
>> And lots of:
>>
>> : QA Issue with staging: libssp_nonshared.la failed sanity test
>> (installed) in path
>> /OE/angstrom-dev/sysroots/armv7a-angstrom-linux-gnueabi/usr/lib
>
> This one I can guess the reason for, we're missing the lamangler
> function helper for cross packages. At the bottom of cross.bbclass, try
> changing:
>
> mv ${SYSROOT_DESTDIR}${target_base_libdir}/* ${SYSROOT_DESTDIR}${STAGING_DIR_TARGET}${target_base_libdir}/ || true
> mv ${SYSROOT_DESTDIR}${target_libdir}/* ${SYSROOT_DESTDIR}${STAGING_DIR_TARGET}${target_libdir}/ || true
>
> to become
>
> rm -rf ${SYSROOT_DESTDIR}${target_base_libdir}/
> rm -rf ${SYSROOT_DESTDIR}${target_libdir}/
> sysroot_stage_libdir ${D}${target_base_libdir} ${SYSROOT_DESTDIR}${STAGING_DIR_TARGET}${target_base_libdir}
> sysroot_stage_libdir ${D}${target_libdir} ${SYSROOT_DESTDIR}${STAGING_DIR_TARGET}${target_libdir}
>
> which should mean the mangling happens correctly. Sorry I can't
> test/push this right at the moment.
I pushed that to
http://gitorious.org/angstrom/openembedded/commits/koen/rpurdie-wip-rebased
regards,
Koen
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.5 (Darwin)
iD8DBQFLtuxwMkyGM64RGpERAoeZAKCEnMZNc1/LwWLkfKAPFT8oFVqrfACbBm04
G8xIY0k4bvzPyLHPUJEhgB4=
=jHZ6
-----END PGP SIGNATURE-----
next prev parent reply other threads:[~2010-04-03 7:24 UTC|newest]
Thread overview: 49+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-04-01 15:33 Request for branch merge Richard Purdie
2010-04-01 15:41 ` Tom Rini
2010-04-01 15:43 ` Tom Rini
2010-04-01 16:07 ` Richard Purdie
2010-04-01 16:45 ` Tom Rini
2010-04-01 18:09 ` Richard Purdie
2010-04-01 18:33 ` Tom Rini
2010-04-01 18:43 ` Richard Purdie
2010-04-01 16:05 ` Richard Purdie
2010-04-01 16:46 ` Tom Rini
2010-04-01 15:46 ` Khem Raj
2010-04-01 16:09 ` Richard Purdie
2010-04-01 16:18 ` Andrea Adami
2010-04-01 16:29 ` Richard Purdie
2010-04-01 16:37 ` Gary Thomas
2010-04-01 17:17 ` Joshua Lock
2010-04-01 17:55 ` Koen Kooi
2010-04-01 18:17 ` Richard Purdie
2010-04-01 20:03 ` Chris Larson
2010-04-01 20:34 ` Tom Rini
2010-04-01 21:08 ` Koen Kooi
2010-04-01 21:25 ` Tom Rini
2010-04-01 21:27 ` Philip Balister
2010-04-01 22:26 ` Tom Rini
2010-04-02 13:40 ` Koen Kooi
2010-04-02 14:35 ` Koen Kooi
2010-04-02 21:41 ` Richard Purdie
2010-04-03 7:21 ` Koen Kooi [this message]
2010-04-02 21:29 ` Richard Purdie
2010-04-03 7:23 ` Koen Kooi
2010-04-08 15:40 ` Joshua Lock
2010-04-03 13:24 ` Koen Kooi
2010-04-12 8:37 ` Koen Kooi
2010-04-12 15:59 ` Tom Rini
2010-04-12 16:46 ` Joshua Lock
2010-05-01 23:29 ` Richard Purdie
2010-05-03 16:46 ` Tom Rini
2010-05-04 18:10 ` Richard Purdie
2010-05-04 18:55 ` Tom Rini
2010-05-05 23:22 ` Richard Purdie
2010-05-05 23:30 ` Tom Rini
2010-04-12 16:45 ` Joshua Lock
2010-04-12 17:47 ` Koen Kooi
2010-04-12 20:55 ` Koen Kooi
2010-04-12 22:19 ` Koen Kooi
2010-04-13 3:46 ` Richard Purdie
2010-04-13 7:06 ` Koen Kooi
2010-05-01 23:28 ` Richard Purdie
2010-05-02 14:13 ` Koen Kooi
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='hp6q9g$di5$1@dough.gmane.org' \
--to=k.kooi@student.utwente.nl \
--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