On 03/27/2012 06:56 PM, j wrote:
> On 03/27/2012 06:28 PM, Mark Russell wrote:
>> Hi Gutembert,
>>
>> I am sorry but I cant remember the exact procedure on how i solve the
>> issue.
>> If I remember correctly, I bitbake the task-gstreamer-ti the second
>> time to
>> solve the issue. I also use the command "bitbake -k task-gstreamer-ti"
>> instead of "bitbake task-gstreamer-ti".
>>
>> Just to check, did you set the kernel version correctly before bitbake
>> task-gstreamer-ti ?
>>
>> If really my solution above cannot solve your problem, you should try
>> out on
>> Zoso1234 methods. Very sorry cant help you much.
>>
>> Mark Russell
>>
>> --
>> View this message in context:
>> http://gumstix.8.n6.nabble.com/Error-in-building-task-gstreamer-ti-tp636576p4662779.html
>> Sent from the Gumstix mailing list archive at Nabble.com.
>>
>> ------------------------------------------------------------------------------
>>
>> This SF email is sponsosred by:
>> Try Windows Azure free for 90 days Click Here
>> http://p.sf.net/sfu/sfd2d-msazure
>> _______________________________________________
>> gumstix-users mailing list
>> gumstix-users@...
>> https://lists.sourceforge.net/lists/listinfo/gumstix-users
> I am in the process of trying the exact thing I am on a VM of Ubuntu
> 10.04 64bit, nothing done but what the wiki states. What I had to do
> is bitbake -k task-gstreamer-ti. Then once it was done, bitbake -c
> clean task-gstreamer-ti; bitbake task-gstreamer-ti. Let it build until
> it fails and will give you just the set of packages that fail. For
> dsplink all I had to do then was, bitbake -c clean ti-dsplink; bitbake
> ti-dsplink. It then rebuilt, there were a total of 4 failures building
> it for me each were solved by going through one by one and cleaning it
> and rebuilding if it failed due to one of the other packages not being
> built first, clean that one and rebuild then go back until all have
> cleared up. Then task-gstreamer-ti built for me completely.
>
> Though now that I have added it to my image in the manner shown on the
> jump page everyone is using it fails building into my actual image
> with linker issues while building gstreamer-ti, giving me this error.
>
> | arm-angstrom-linux-gnueabi-libtool: link: warning: library
> `/home/flubber/overo-oe/tmp/sysroots/armv7a-angstrom-linux-gnueabi/usr/lib/libgstbase-0.10.la'
> was moved.
> | /bin/grep:
> /home/flubber/overo-oe/tmp/sysroots/overo-angstrom-linux-gnueabi/usr/lib/libgstreamer-0.10.la:
> No such file or directory
> | /bin/sed: can't read
> /home/flubber/overo-oe/tmp/sysroots/overo-angstrom-linux-gnueabi/usr/lib/libgstreamer-0.10.la:
> No such file or directory
> | arm-angstrom-linux-gnueabi-libtool: link:
> `/home/flubber/overo-oe/tmp/sysroots/overo-angstrom-linux-gnueabi/usr/lib/libgstreamer-0.10.la'
> is not a valid libtool archive
> | make[3]: *** [libgstticodecplugin.la] Error 1
> | make[3]: Leaving directory
> `/home/flubber/overo-oe/tmp/work/overo-angstrom-linux-gnueabi/gstreamer-ti-svnr822-r83+r103/gstreamer_ti/ti_build/ticodecplugin/src'
> | make[2]: *** [all] Error 2
> | make[2]: Leaving directory
> `/home/flubber/overo-oe/tmp/work/overo-angstrom-linux-gnueabi/gstreamer-ti-svnr822-r83+r103/gstreamer_ti/ti_build/ticodecplugin/src'
> | make[1]: *** [all-recursive] Error 1
> | make[1]: Leaving directory
> `/home/flubber/overo-oe/tmp/work/overo-angstrom-linux-gnueabi/gstreamer-ti-svnr822-r83+r103/gstreamer_ti/ti_build/ticodecplugin'
> | make: *** [all] Error 2
> | + die 'oe_runmake failed'
> | + oefatal 'oe_runmake failed'
> | + echo FATAL: 'oe_runmake failed'
> | FATAL: oe_runmake failed
> | + exit 1
>
>
> which to me makes no sense since it just built without being put into
> the image, I even just rm -rf tmp/ and rebuilt task-gstreamer-ti first
> built completely then built the image and it fails on the gstreamer-ti
> recipe, very confusing.
>
> Hope some of this helps
Well I was able to work through this stated issue I had with what I
already said as well as applying this patch to the gstreamer-ti.inc recipe.
It is from 6/23/11
http://cgit.openembedded.org/openembedded/patch/?id=ea41560b2cadfa184de8122e0395b92fd7c35c39
You can either apply it yourself or just apply the 2 new lines yourself
if unsure on patching. Do others have local changes they have had to do
but not mentioned on the boards? I have had to do other changes but only
checksums so far, and when I test built the omap3-desktop-image empathy
failed to build but I did not look into as I do not need it and went to
building my image.
How I found this patch was searching for the name of the recipe and the
issue at hand which for me was libtool. Which led me to a few things
close until I found this.
Hope this helps someone.
|