From mboxrd@z Thu Jan  1 00:00:00 1970
From: graeme.russ@gmail.com (Graeme Russ)
Date: Tue, 22 Nov 2011 22:06:09 +1100
Subject: x86 kernel build chain - how bzImage gets created
In-Reply-To: <CAEnQRZCq4fiPgVksTz7i07Npg22JFTFTKmhovU36JQzBnPK5Kg@mail.gmail.com>
References: <4ECB7D87.3030601@gmail.com>
	<CAEnQRZCq4fiPgVksTz7i07Npg22JFTFTKmhovU36JQzBnPK5Kg@mail.gmail.com>
Message-ID: <4ECB8221.7070506@gmail.com>
To: kernelnewbies@lists.kernelnewbies.org
List-Id: kernelnewbies.lists.kernelnewbies.org

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