From: Robert Zach <rza1@so-logic•net>
To: linuxppc-embedded@ozlabs•org
Subject: bootstrap loader + gzip 1.3.5 --> huge image!?
Date: Tue, 11 Mar 2008 15:37:31 +0100 [thread overview]
Message-ID: <47D6992B.6060208@so-logic.net> (raw)
hi list!
I am using the xilinx git tree with the included bootstrap loader.
Everthing works fine when i use binutils-2.16.1-gcc-3.4.6-uClibc-0.9.29.
But when useing binutils-2.18.50-gcc-4.2.0-uClibc-0.9.29 (generated
with buildroot) i get the following problem:
At the end of the kernel build process the vmlinux image gets compressed
(for the bootstrap loader).
something like:
gzip -f -9 < arch/ppc/boot/images/vmlinux.bin >
arch/ppc/boot/images/vmlinux.gz.$$
when i compiled the kernel with binutils-2.16.1-gcc-3.4.6-uClibc-0.9.29
the resulting image size is smaller then the original and everything
works (the bootstrap loader uncompresses, the kernel boots, ..)
But when using the binutils-2.18.50-gcc-4.2.0-uClibc-0.9.29
cross-toolchain i get the following:
du arch/ppc/boot/images/vmlinux.bin
1264 arch/ppc/boot/images/vmlinux.bin
gzip -f -9 < arch/ppc/boot/images/vmlinux.bin >
arch/ppc/boot/images/vmlinux.gz.$$
du arch/ppc/boot/images/vmlinux.gz.$$
3640 arch/ppc/boot/images/vmlinux.gz
The resulting huge zImage.elf file does not work (the bootstraploader
stops somewhere early).
Its the same for all other toolchains i tryed using binutils > 2.16.
what does gzip do?
I use the following version
gzip --version
gzip 1.3.5
(2002-09-30)
Copyright 2002 Free Software Foundation
Copyright 1992-1993 Jean-loup Gailly
Does anybody know this problem?
any suggestions for a solution.
thanks in advanced!
greets!
robert
next reply other threads:[~2008-03-11 14:47 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-03-11 14:37 Robert Zach [this message]
2008-03-11 15:45 ` bootstrap loader + gzip 1.3.5 --> huge image!? rza1
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=47D6992B.6060208@so-logic.net \
--to=rza1@so-logic$(echo .)net \
--cc=linuxppc-embedded@ozlabs$(echo .)org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
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