From: Peter Korsgaard <peter@korsgaard.com>
To: buildroot@busybox.net
Subject: [Buildroot] tar failing to build with latest buildroot
Date: Mon, 14 Mar 2016 13:40:40 +0100 [thread overview]
Message-ID: <874mc9dygn.fsf@dell.be.48ers.dk> (raw)
In-Reply-To: <1457951104.2051.1.camel@rovoreed.com> (Mike Davies's message of "Mon, 14 Mar 2016 10:25:04 +0000")
>>>>> "Mike" == Mike Davies <busybox_mail@rovoreed.com> writes:
> Title says it all really. 'tar' (the real one not the busybox version)
> fails to build in the latest stable version. I'm using uClibc 1.0.12
> [mike at ceri buildroot-2016.02]$ make
>>>> tar 1.28 Building
> PATH="/home/mike/work/kodi/buildroot
> -2016.02/output/host/bin:/home/mike/work/kodi/buildroot
> -2016.02/output/host/sbin:/home/mike/work/kodi/buildroot
> -2016.02/output/host/usr/bin:/home/mike/work/kodi/buildroot
> -2016.02/output/host/usr/sbin:/usr/lib64/qt
> -3.3/bin:/usr/local/bin:/usr/bin:/bin:/usr/local/sbin:/usr/sbin:/home/m
> ike/bin:/sbin:/home/mike/.local/bin:/home/mike/bin:/home/mike/bin:/sbin
> " /usr/bin/make -j5 -C /home/mike/work/kodi/buildroot
> -2016.02/output/build/tar-1.28/
> /usr/bin/make all-recursive
> Making all in doc
> make[4]: Nothing to be done for 'all'.
Is this with a clean build? E.G. tar needs wchar, so if you didn't have
that enabled in the toolchain configuration you will need to rebuild the
toolchain.
It works for me with current git with this defconfig:
cat defconfig
BR2_arm=y
BR2_TOOLCHAIN_BUILDROOT_WCHAR=y
BR2_PACKAGE_BUSYBOX_SHOW_OTHERS=y
BR2_PACKAGE_TAR=y
What is your configuration exactly? (E.G. run make savedefconfig and
post your defconfig file).
--
Bye, Peter Korsgaard
next prev parent reply other threads:[~2016-03-14 12:40 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-03-14 10:25 [Buildroot] tar failing to build with latest buildroot Mike Davies
2016-03-14 12:40 ` Peter Korsgaard [this message]
2016-03-14 13:40 ` Thomas Petazzoni
2016-03-14 19:07 ` Mike Davies
2016-03-14 20:43 ` Peter Korsgaard
2016-03-15 18:33 ` Mike Davies
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=874mc9dygn.fsf@dell.be.48ers.dk \
--to=peter@korsgaard.com \
--cc=buildroot@busybox.net \
/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