All of lore.kernel.org
 help / color / mirror / Atom feed
From: graeme.russ@gmail.com (Graeme Russ)
To: kernelnewbies@lists.kernelnewbies.org
Subject: x86 kernel build chain - how bzImage gets created
Date: Tue, 22 Nov 2011 22:06:09 +1100	[thread overview]
Message-ID: <4ECB8221.7070506@gmail.com> (raw)
In-Reply-To: <CAEnQRZCq4fiPgVksTz7i07Npg22JFTFTKmhovU36JQzBnPK5Kg@mail.gmail.com>

Hi Daniel

On 22/11/11 21:59, Daniel Baluta wrote:
> On Tue, Nov 22, 2011 at 12:46 PM, Graeme Russ <graeme.russ@gmail.com> wrote:
>> Hi All,
>>
>> Hopefully this will help demystify the build process
>>
>> Notation:
>> <primary input file> (<file size in bytes>)
>>  |
>>  + <additional input file>
>>  |
>>  * <command>
>>  |
>>  \-> <output file> (<file size in bytes>)
>>
>> The file sizes are arbitrary and are based on the current configuration
>> options I have set for a small kernel. They are simply there to illustrate
>> the relative differences in file sizes.
> 
> Great! Thanks for sharing this.

Your welcome :)

> 
>> Note that vmlinux.o is not used to generate bzImage but I've included it
>> for completeness
> 
> [...]
>> + net/built-in.o
>> |
>> * ld -m elf_i386 -r -o vmlinux.o
>> |
>> \->vmlinux.o (2,889,050)
> 
> What is the purpose of vmlinux.o then?

I don't know - Anyone?

Regards,

Graeme

  reply	other threads:[~2011-11-22 11:06 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-11-22 10:46 x86 kernel build chain - how bzImage gets created Graeme Russ
2011-11-22 10:59 ` Daniel Baluta
2011-11-22 11:06   ` Graeme Russ [this message]
2011-11-22 17:54 ` Mulyadi Santosa
2011-11-27 21:41   ` Graeme Russ

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=4ECB8221.7070506@gmail.com \
    --to=graeme.russ@gmail.com \
    --cc=kernelnewbies@lists.kernelnewbies.org \
    /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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.