All of lore.kernel.org
 help / color / mirror / Atom feed
From: Saul Wold <sgw@linux.intel.com>
To: Yannis Damigos <giannis.damigos@gmail.com>
Cc: yocto@yoctoproject.org
Subject: Re: Possible issue when supported distros update their GNU tar package to version 1.27
Date: Fri, 11 Oct 2013 13:51:19 -0700	[thread overview]
Message-ID: <525864C7.40509@linux.intel.com> (raw)
In-Reply-To: <20131011120949.GA664@xekarfwtos-lp>

On 10/11/2013 05:09 AM, Yannis Damigos wrote:
> Hi everyone,
>
> I work on Archlinux (64bit) and build a beagleboard image.
> Build Configuration:
> BB_VERSION        = "1.20.0"
> BUILD_SYS         = "x86_64-linux"
> NATIVELSBSTRING   = "Arch-Linux"
> TARGET_SYS        = "arm-poky-linux-gnueabi"
> MACHINE           = "beagleboard"
> DISTRO            = "poky"
> DISTRO_VERSION    = "1.5"
> TUNE_FEATURES     = "armv7a vfp neon"
> TARGET_FPU        = "vfp-neon"
> meta
> meta-yocto
> meta-yocto-bsp    = "master:102bf5e0f640fe85068452a42b85077f1c81e0c9"
>
> The build process stops at the task "quilt-native_0.60.bb, do_populate_sysroot"
> with the following error:
>      tar: --same-order option cannot be used with -c
>      Try 'tar --help' or 'tar --usage' for more information.
>      tar: This does not look like a tar archive
>      tar: Exiting with failure status due to previous errors
>
> Searching around I found out that the problem was found at the file
> meta/classes/staging.bbclass at line 16:
>      tar -cf - -C "$src" -ps . | tar -xf - -C "$dest"
>
> The issue comes up if user's distro is using  GNU tar version 1.27
> Here is a link to the tar patch that causing the problem:
> http://git.savannah.gnu.org/cgit/tar.git/commit/?id=74ce228f6df956e6b7be9fd4f993bada4b7ea645
>
> If I downgrade the tar package to version 1.26, the build ends with success.
>

It's just a little too late to get this fixed for 1.5, we are in the 
middle of the final full pass test.  But you can also use the Buildtools 
SDK Tarball.

This was created for systems that don't have the correct versions of 
Python, Git, Tar and Make.  It can be downloaded from the following link:

https://www.yoctoproject.org/download/buildtools-sdk

Sau!

> Here is a list with all the files that should be updated/patched
> ./meta/lib/oe/path.py: cmd = 'tar -cf - -C %s -ps . | tar -xf - -C %s' % (src, dst)
> ./meta/lib/oe/path.py: cmd = 'cd %s; find . -type d -print | tar -cf - -C %s -ps --files-from - | tar -xf - -C %s' % (src, src, dst)
> ./meta/classes/package.bbclass: cmd = 'tar -cf - -C %s -ps . | tar -xf - -C %s' % (dest, dvar)
> ./meta/classes/populate_sdk_deb.bbclass: tar -cf - -C ${STAGING_ETCDIR_NATIVE} -ps apt | tar -xf - -C ${target_rootfs}/etc
> ./meta/classes/libc-package.bbclass: tar -cf - -C ${LOCALETREESRC}${datadir} -ps i18n | tar -xf - -C $treedir/${datadir}
> ./meta/classes/libc-package.bbclass: tar -cf - -C ${LOCALETREESRC}${base_libdir} -ps . | tar -xf - -C $treedir/${base_libdir}
> ./meta/classes/libc-package.bbclass: tar -cf - -C ${STAGING_DIR_NATIVE}/${prefix_native}/${base_libdir} -ps libgcc_s.* | tar -xf - -C $treedir/${base_libdir}
> ./meta/classes/libc-package.bbclass: tar -cf - -C $treedir/$parent -ps $(basename ${localedir}) | tar -xf - -C ${PKGD}$parent
> ./meta/classes/staging.bbclass: tar -cf - -C "$src" -ps . | tar -xf - -C "$dest"
> ./bitbake/lib/bb/fetch2/__init__.py: #cmd = 'tar -cf - -C "%d" -ps . | tar -xf - -C "%s/%s/"' % (file, rootdir, destdir)
>
> Best regards,
> Yannis
> _______________________________________________
> yocto mailing list
> yocto@yoctoproject.org
> https://lists.yoctoproject.org/listinfo/yocto
>
>


      reply	other threads:[~2013-10-11 20:51 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-10-11 12:09 Possible issue when supported distros update their GNU tar package to version 1.27 Yannis Damigos
2013-10-11 20:51 ` Saul Wold [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=525864C7.40509@linux.intel.com \
    --to=sgw@linux.intel.com \
    --cc=giannis.damigos@gmail.com \
    --cc=yocto@yoctoproject.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.