From: Peter Korsgaard <jacmet@uclibc.org>
To: buildroot@busybox.net
Subject: [Buildroot] init: I won't write compressed data to a terminal.
Date: Wed, 07 Jul 2010 22:49:56 +0200 [thread overview]
Message-ID: <871vbf585n.fsf@macbook.be.48ers.dk> (raw)
In-Reply-To: <4C34E693.9040307@gmx.net> (Ossy's message of "Wed, 07 Jul 2010 22:41:55 +0200")
>>>>> "Ossy" == Ossy <ossy1980@gmx.net> writes:
Hi,
>> What does strings -n 25 bin/busybox|head give?
Ossy> ossy at debian-virtual:/exports/rootfs/rfs1$ strings -n 25 bin/busybox|head
Ossy> bzip2: I'm not configured correctly for this platform!
Ossy> I require Int32, Int16 and Char to have sizes
Ossy> of 4, 2 and 1 bytes to run properly, and they don't.
Ossy> Probably you can fix this by defining them correctly,
Ossy> is suspiciously (more than %d chars) long.
Ossy> Try using a reasonable file name instead. Sorry! :-)
Ossy> %s: Deleting output file %s, if it exists.
Ossy> %s: WARNING: deletion of output file (apparently) failed.
Ossy> %s: WARNING: deletion of output file suppressed
Ossy> %s: since input file no longer exists. Output file
Ossy> ossy at debian-virtual:/exports/rootfs/rfs1$
Ok, as expected - Somehow your busybox binary got overwritten by bzip2.
Ossy> I'm compiling for target arm926 on an amd64 debian squeeze.
Ossy> My busybox is not 500kb big ... (shared vs. static?):
Ossy> ossy at debian-virtual:/exports/rootfs/rfs1/bin$ ls -la busybox
Ossy> -rwsr-xr-x 1 root root 78480 28. Jun 15:40 busybox
No, it's because it's bzip2 instead of busybox.
I'm doing a test build right now to see what goes wrong.
--
Bye, Peter Korsgaard
next prev parent reply other threads:[~2010-07-07 20:49 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-07-06 22:16 [Buildroot] init: I won't write compressed data to a terminal Ossy
2010-07-07 0:35 ` Mitch Davis
2010-07-07 20:20 ` Ossy
2010-07-07 20:33 ` Peter Korsgaard
2010-07-07 20:41 ` Ossy
2010-07-07 20:49 ` Peter Korsgaard [this message]
2010-07-07 21:39 ` Peter Korsgaard
2010-07-09 19:46 ` Ossy
2010-07-11 18:52 ` Peter Korsgaard
2010-07-07 20:45 ` Peter Korsgaard
2010-07-07 5:52 ` Peter Korsgaard
2010-07-07 6:14 ` Mitch Davis
2010-07-07 18:00 ` Ossy
2010-07-07 18:59 ` Peter Korsgaard
2010-07-07 20:14 ` Ossy
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=871vbf585n.fsf@macbook.be.48ers.dk \
--to=jacmet@uclibc.org \
--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