From: Gary Thomas <gary@mlbassoc.com>
To: openembedded-devel@lists.openembedded.org
Subject: Re: Can't build gstreamer-ti
Date: Wed, 09 Mar 2011 09:55:29 -0700 [thread overview]
Message-ID: <4D77B101.4040204@mlbassoc.com> (raw)
In-Reply-To: <4D77210E.8040602@gmail.com>
On 03/08/11 23:41, Khem Raj wrote:
>> | arm-angstrom-linux-gnueabi-libtool: link: warning: library
>> `/work/local/Angstrom_BeagleBoard/tmp/sysroots/armv7a-angstrom-linux-gnueabi/usr/lib/libgstbase-0.10.la'
>> was moved.
>> | /bin/grep:
>> /work/local/Angstrom_BeagleBoard/tmp/sysroots/beagleboard-angstrom-linux-gnueabi/usr/lib/libgstreamer-0.10.la:
>> No such file or directory
>> | /bin/sed: can't read
>> /work/local/Angstrom_BeagleBoard/tmp/sysroots/beagleboard-angstrom-linux-gnueabi/usr/lib/libgstreamer-0.10.la:
>> No such file or directory
>> | arm-angstrom-linux-gnueabi-libtool: link:
>> `/work/local/Angstrom_BeagleBoard/tmp/sysroots/beagleboard-angstrom-linux-gnueabi/usr/lib/libgstreamer-0.10.la'
>> is not a valid libtool archive
>>
>> Any ideas how to fix this?
>
> seems libtool is looking in machine sysroot where as it should be looking in arch sysroot
>
> could you try adding EXTRA_OECONF += "--with-libtool-sysroot=${STAGING_DIR_TARGET}" to corresponding recipe and see if that helps ?
No change, sorry.
--
------------------------------------------------------------
Gary Thomas | Consulting for the
MLB Associates | Embedded world
------------------------------------------------------------
next prev parent reply other threads:[~2011-03-09 16:57 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-03-07 23:42 Can't build gstreamer-ti Gary Thomas
2011-03-08 7:19 ` Maksym Parkachov
2011-03-09 6:41 ` Khem Raj
2011-03-09 16:55 ` Gary Thomas [this message]
2011-04-19 22:39 ` Tim Harvey
[not found] <mailman.0.1289314919.16967.angstrom-distro-devel@linuxtogo.org>
2010-11-09 15:06 ` Matt Johnson
2010-11-09 18:14 ` Gary Thomas
2010-11-09 18:28 ` Matt Johnson
2010-11-09 21:55 ` Henning Heinold
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=4D77B101.4040204@mlbassoc.com \
--to=gary@mlbassoc.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.