From: Peter Korsgaard <peter@korsgaard.com>
To: buildroot@busybox.net
Subject: [Buildroot] tar failing to build with latest buildroot
Date: Mon, 14 Mar 2016 21:43:34 +0100 [thread overview]
Message-ID: <87fuvsdc3t.fsf@dell.be.48ers.dk> (raw)
In-Reply-To: <1457982423.1938.1.camel@rovoreed.com> (Mike Davies's message of "Mon, 14 Mar 2016 19:07:03 +0000")
>>>>> "Mike" == Mike Davies <busybox_mail@rovoreed.com> writes:
Hi,
> Thanks for the reply. I tried a full rebuild with a 'make clean all'
> and it fails exactly the same again.
> Here is my defconfig. You'll see I have my own config file for uClibc.
> That follows the defconfig, and you'll see that WCHAR is enabled.
> BR2_arm=y
> BR2_cortex_a7=y
> BR2_ARM_FPU_NEON_VFPV4=y
> BR2_KERNEL_HEADERS_4_1=y
> BR2_UCLIBC_CONFIG="uClibc_armv7.config"
Why are you using a custom uClibc configuration? Judging from the
hostname and packages enabled, it doesn't seem like you need to squeeze
the last few bytes out of the system.
> uClibc_armv7.config ...
Diffing this with our default uclibc config, I see:
> # UCLIBC_HAS_OBSTACK is not set
Whereas our config has it enabled. Judging from the error message this
is most likely the reason it fails for you.
Can you please retry with our default uclibc config?
--
Venlig hilsen,
Peter Korsgaard
next prev parent reply other threads:[~2016-03-14 20:43 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 [this message]
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=87fuvsdc3t.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