[OE-core] tar: This does not look like a tar archive; bzip2-native folder has empty binaries

[Sriram Sundararajan]

I'm using Ubuntu-12.04 to build.


On Sun, Aug 26, 2012 at 1:33 PM, Khem Raj <raj.khem at gmail.com> wrote:

> On Sun, Aug 26, 2012 at 11:33 AM, Sriram Sundararajan
> <sriram.sundararajan at gmail.com> wrote:
> > I was able to compile a 'core-image-minimal' on 08/23/12 without any
> issues.
> > On 08/25 however, I came across the following issue for the same (bitbake
> > core-image-minimal)
> >
> > ERROR: Function failed: Unpack failure for URL:
> > 'http://www.python.org/ftp/python/2.7.3/Python-2.7.3.tar.bz2'. Unpack
> > command
> >
> PATH="/opt/oe/oe-core/scripts/native-intercept:/opt/oe/oe-core/build/tmp-eglibc/sysroots/x86_64-linux/usr/bin/bzip2-native:blah:blah"
> > bzip2 -dc /opt/oe/oe-core/build/downloads/Python-2.7.3.tar.bz2 | tar x
> > --no-same-owner -f - failed with return value 2
> > ERROR: Logfile of failure stored in:
> >
> /opt/oe/oe-core/build/tmp-eglibc/work/x86_64-linux/python-native-2.7.3-r0.1/temp/log.do_unpack.3125
> > Log data follows:
> > | DEBUG: Executing python function do_unpack
> > | DEBUG: Executing python function base_do_unpack
> > | NOTE: Unpacking /opt/oe/oe-core/build/downloads/Python-2.7.3.tar.bz2 to
> >
> /opt/oe/oe-core/build/tmp-eglibc/work/x86_64-linux/python-native-2.7.3-r0.1/
> > | tar: This does not look like a tar archive
> > | tar: Exiting with failure status due to previous errors
> > | DEBUG: Python function base_do_unpack finished
> > | DEBUG: Python function do_unpack finished
> >
> > The bzip2-native binary files (including appropriate symlinks) were
> present
> > under tmp-eglibc/sysroots/x86_64-linux/usr/bin/bzip2-native, but were all
> > empty! I was able to copy my /bin/bz* to
> > /tmp-eglibc/sysroots/x86_64-linux/usr/bin/bzip2-native and move on.
>  Don't
> > know much about bzip2-native, but bitbake bzip2-native had no effect.
>  Both
> > my installs were performed from scratch on identical ubuntu 12.04
> installs.
> > The oe-core sources were cloned from gibhub. One on 08/23 and another on
> > 08/25. There was a checkin reference to bzip2-native for
> > python-native_2.7.3.bb about a month back according to github.
> >
> > Can anyone shed any light on why bzip tools were not compiled or
> installed
> > properly? What could've changed during these two days? I did a `find . |
> > grep bzip2-native` and saw some references to a folder
> > bzip2-native-1.0.6-r5. However, I could not find any references to
> > bzip2-full-native_1.0.6.bb or bzip2-native_1.0.6.bb. Now I'm scratching
> my
> > head and thinking where did this package come from in the first place?
> Any
> > help appreciated!
>
> what is your build host OS?
>
> >
> > Thanks
> > Sriram
> >
> > _______________________________________________
> > Openembedded-core mailing list
> > Openembedded-core at lists.openembedded.org
> > http://lists.linuxtogo.org/cgi-bin/mailman/listinfo/openembedded-core
> >
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.openembedded.org/pipermail/openembedded-core/attachments/20120826/26e220a0/attachment-0002.html>