From: Bernhard Fischer <rep.dot.nop@gmail.com>
To: buildroot@busybox.net
Subject: [Buildroot] failing to build the buildroot
Date: Mon, 30 Jul 2007 11:24:14 +0200 [thread overview]
Message-ID: <20070730092414.GD23273@aon.at> (raw)
In-Reply-To: <OF54359986.7DD332CA-ONC2257328.0032AEDA-C3257328.002CFE8E@visonic.com>
On Mon, Jul 30, 2007 at 01:15:33PM +0400, Shai Lifshitz wrote:
>maybe you give me a hint how to solve the problem? I'll appreciate it
>alot.
>I am trying to build the buildroot for a week with no success
>
>
>
>
>
>Bernhard Fischer <rep.dot.nop@gmail.com>
>07/30/2007 01:09 PM
>
> To: Shai Lifshitz <ShaiL@visonic.com>
> cc: buildroot at uclibc.org
> Subject: Re: [Buildroot] failing to build the buildroot
>
>
>On Mon, Jul 30, 2007 at 12:51:31PM +0400, Shai Lifshitz wrote:
>>Dir Sir,
>>
>>I downloaded today the buildroot-snapshot.tar.bz2.tar file from the FTP
>
>>10:28:27 (9.77 KB/s)
>>-`/home/shail/downloads/tt3/buildroot/dl/gcc-4.2.0.tar.bz2'
>>saved[44,057,527/44,057,527]
>>
>>mkdir -p /home/shail/downloads/tt3/buildroot/toolchain_build_arm
>>rm -rf /home/shail/downloads/tt3/buildroot/toolchain_build_arm/gcc-4.2.0
>>bzcat /home/shail/downloads/tt3/buildroot/dl/gcc-4.2.0.tar.bz2 | tar -C
>>/home/shail/downloads/tt3/buildroot/toolchain_build_arm -xf -
>>
>>tar: Skipping to next header
>>tar: Archive contains obsolescent base-64 headers
>>
>>bzcat: Data integrity error when decompressing.
>> Input file =
>>/home/shail/downloads/tt3/buildroot/dl/gcc-4.2.0.tar.bz2, output file =
>>(stdout)
>>
>>It is possible that the compressed file(s) have become corrupted.
>
>Well, this says about all..
[please keep this on the list, thanks]
rm -f dl/gcc-4.2*tar*
make distclean && make
prev parent reply other threads:[~2007-07-30 9:24 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-07-30 8:51 [Buildroot] failing to build the buildroot Shai Lifshitz
2007-07-30 9:09 ` Bernhard Fischer
[not found] ` <OF54359986.7DD332CA-ONC2257328.0032AEDA-C3257328.002CFE8E@visonic.com>
2007-07-30 9:24 ` Bernhard Fischer [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=20070730092414.GD23273@aon.at \
--to=rep.dot.nop@gmail.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