Trouble Compressing the Kernel

Trouble Compressing the Kernel

Post by Wolfgang Steine » Wed, 14 Oct 1998 04:00:00



Hi to all!

I am trying to create an new kernel v.2.0.35 for my system. For this I
am
using gcc 2.8.1 and binutils 2.9.1.  Everything goes well until the
compression
of the kernel. At this point there are entries in the makefiles at
arch/i386/boot and arch/i386/boot/compressed, that use the utility
objdump with the options -k -q and -o <start-address>.
Apparently my version of objdump does not recognise these options and
I do not know, what they are supposed to do.
Is it possible to do the required step in the makefiles with binutils
2.9.1 or
do I have to revert to an earlier version????

Thanks in advance, Wolfgang

 
 
 

1. Compressed 2.2 kernel about 35% larger than compressed 2.0.x?

Hi,

I downloaded, complied and installed v 2.2 yesterday. The compilation
went without a hitch and the kernel booted up correctly. Everything is
working perfectly. But I notice that the kernel size has increased by
a considerable amount compared to 2.0.x, compiled with exactly the
same features.

Size of /vmlinuz for 2.0.33 on my system: ~325 kB.

Size of /vmlinuz for 2.2.0 with same features: ~450 kB.

Is this normal? Thanks for any help.

Hari.
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^


-------------------------------------------------------

2. Installation help

3. Compressed kernel messages from an actual extraction from kernel source

4. Memory problem - E250 server

5. Tech reason upgrading compress would cause trouble.

6. Never ending Script

7. troubles with ppp: missing module ppp-compress

8. adaptec 2940uw

9. COMPRESS (how much does it compress?)

10. Compressed filesystem or Compressed loop?

11. compressing on the fly: father process seems to end before popened compress

12. To compress or not to compress, that is the question.

13. Kernel way of mind (kmalloc trouble) kernel 2.2.18 mandrake 7.2 x86 arch