From: Mike Davies <busybox_mail@rovoreed.com>
To: buildroot@busybox.net
Subject: [Buildroot] tar failing to build with latest buildroot
Date: Tue, 15 Mar 2016 18:33:36 +0000 [thread overview]
Message-ID: <1458066816.2333.1.camel@rovoreed.com> (raw)
In-Reply-To: <87fuvsdc3t.fsf@dell.be.48ers.dk>
On Mon, 2016-03-14 at 21:43 +0100, Peter Korsgaard wrote:
>
> Can you please retry with our default uclibc config?
>
Thanks for the reply.
I can confirm that that fixes the problem.
prev parent reply other threads:[~2016-03-15 18:33 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
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 [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=1458066816.2333.1.camel@rovoreed.com \
--to=busybox_mail@rovoreed.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 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.