Openembedded Devel Discussions
 help / color / mirror / Atom feed
From: Koen Kooi <k.kooi@student.utwente.nl>
To: openembedded-devel@lists.openembedded.org
Subject: Re: Request for branch merge
Date: Sun, 02 May 2010 16:13:38 +0200	[thread overview]
Message-ID: <hrk1ai$psn$1@dough.gmane.org> (raw)
In-Reply-To: <1272756489.30647.1938.camel@rex>

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

On 02-05-10 01:28, Richard Purdie wrote:
> On Tue, 2010-04-13 at 09:06 +0200, Koen Kooi wrote:
>> On 13-04-10 05:46, Richard Purdie wrote:
>>> On Tue, 2010-04-13 at 00:19 +0200, Koen Kooi wrote:
>>>> OK, I reproduced the abiword failure, it's in enchant:
>>>>
>>>> | /bin/sh ../../arm-angstrom-linux-gnueabi-libtool --tag=CC
>>>> - --mode=link ccache arm-angstrom-linux-gnueabi-gcc -march=armv7-a
>>>> - -mtune=cortex-a8 -mfpu=neon -mfloat-abi=softfp
>>>> -
>>>> -isystem/OE/angstrom-dev/sysroots/armv7a-angstrom-linux-gnueabi/usr/include
>>>> - -fexpensive-optimizations -frename-registers -fomit-frame-pointer -O2
>>>> - -ggdb3 -module -avoid-version -no-undefined
>>>> - -L/OE/angstrom-dev/sysroots/armv7a-angstrom-linux-gnueabi/usr/lib
>>>> -
>>>> -Wl,-rpath-link,/OE/angstrom-dev/sysroots/armv7a-angstrom-linux-gnueabi/usr/lib
>>>> - -Wl,-O1 -Wl,--hash-style=gnu -o libenchant_aspell.la -rpath
>>>> /usr/lib/enchant aspell_provider.lo -Wl,--export-dynamic -pthread
>>>> - -lgmodule-2.0 -lrt -lglib-2.0
>>>> - -L/OE/angstrom-dev/sysroots/armv7a-angstrom-linux-gnueabi/usr/lib
>>>> - -laspell ../../src/libenchant.la
>>>> | /bin/grep:
>>>> /OE/angstrom-dev/cross/armv7a/arm-angstrom-linux-gnueabi/lib/libstdc++.la:
>>>> No such file or directory
>>>> | /bin/sed: can't read
>>>> /OE/angstrom-dev/cross/armv7a/arm-angstrom-linux-gnueabi/lib/libstdc++.la:
>>>> No such file or directory
>>>> | arm-angstrom-linux-gnueabi-libtool: link:
>>>> `/OE/angstrom-dev/cross/armv7a/arm-angstrom-linux-gnueabi/lib/libstdc++.la'
>>>> is not a valid libtool archive
>>>>
>>>> The file referenced
>>>> (/OE/angstrom-dev/cross/armv7a/arm-angstrom-linux-gnueabi/lib/libstdc++.la)
>>>> doesn't exist since it is located in
>>>> /OE/angstrom-dev/sysroots/armv7a-angstrom-linux-gnueabi/usr/lib/libstdc++.la
>>>> instead.
>>>>
>>>> Any clues in which direction I should look to debug this?
>>>
>>> Sorry I've not been able to spend the time I'd like on this stuff, work
>>> and travel have got in the way and are probably going to tie me up for a
>>> while yet if I'm realistic. Anyone at ELC should say hello btw! :) 
>>
>>
>>> Jet lag prevents me thinking too clearly at the moment but whats
>>> happening above is that the sysroot is starting to look more like the
>>> real target filesystem and libstdc++ is moving to what I would say is
>>> the correct place for it. This is good but it seems something, probably
>>> a .la file has the incorrect path? Is this a build from scratch or an
>>> old build? I suspect it would work with a build from scratch but if this
>>> was one, there is some more subtle problem :/.
>>
>> It's a complete build from scratch (rm tmp -rf ; bitbake abiword).
> 
> Sorry about the delay, this commit should fix it (reproduced and tested
> locally):
> 
> http://git.openembedded.net/cgit.cgi/openembedded/commit/?h=rpurdie/work-in-progress&id=bb53e48f79dab0877c8b8ce487a051d29cae31e3

Awesome, that removes the last of my concerns, please merge it :) I have
time next week to deal with possible fallout.

regards,

Koen
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.5 (Darwin)

iD8DBQFL3YiSMkyGM64RGpERAh93AJ4+VaaUA5ZjK4FTck/X23LiPYPOKQCglzfg
O4zXrxxiRVfcsJ1ULnrxbZs=
=K19A
-----END PGP SIGNATURE-----




      reply	other threads:[~2010-05-02 14:17 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
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 [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='hrk1ai$psn$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