Buildroot Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Andreas Kuehn <Andreas.Kuehn@gin.de>
To: buildroot@busybox.net
Subject: [Buildroot] kernel image size depends on toolchain? -Solved-
Date: Wed, 11 Jun 2008 17:08:24 +0200	[thread overview]
Message-ID: <484FEA68.2060507@gin.de> (raw)
In-Reply-To: <87fxrkjcp8.fsf@macbook.be.48ers.dk>

Hi Peter!

	Strike!

Created:      Wed Jun 11 16:51:42 2008
Image Type:   ARM Linux Kernel Image (uncompressed)
Data Size:    1402212 Bytes = 1369.35 kB = 1.34 MB  <--<< Groovy !

You were right, that patch was missing.
Really great support.
Thank you
	akuehn  :-)




Peter Korsgaard wrote:
>>>>>> "Andreas" == Andreas Kuehn <Andreas.Kuehn@gin.de> writes:
> 
> Hi,
> 
>  Andreas> Right from the .config file....
>  Andreas> BR2_BINUTILS_VERSION="2.18"
>  Andreas> BR2_EXTRA_BINUTILS_CONFIG_OPTIONS=""
> 
>  Andreas> I suppose version 2.18 is the "old" version?  Meanwhile, I
>  Andreas> changed to version 2.18.50.0.1 and did a complete rebuild
>  Andreas> with a well known result:
> 
>  Andreas> Image Type:   ARM Linux Kernel Image (uncompressed)
>  Andreas> Data Size:    4528100 Bytes = 4421.97 kB = 4.32 MB
> 
>  Andreas> I don't know where that commit you mentioned has gone to
>  Andreas> (where does that 1e621a8e3752367d4aae78a8ab00a18fb2793f34
>  Andreas> belong to). Is it the kernel tree or the binutils and
>  Andreas> finally which version?
> 
> It's from the kernel git tree. It's a simple oneliner, you could maybe
> patch it by hand in your Linux checkout:
> 
> diff --git a/arch/arm/Makefile b/arch/arm/Makefile
> index fa4ea9f..6c2d539 100644
> --- a/arch/arm/Makefile
> +++ b/arch/arm/Makefile
> @@ -12,7 +12,7 @@
>  
>  LDFLAGS_vmlinux        :=-p --no-undefined -X
>  CPPFLAGS_vmlinux.lds = -DTEXT_OFFSET=$(TEXT_OFFSET)
> -OBJCOPYFLAGS   :=-O binary -R .note -R .comment -S
> +OBJCOPYFLAGS   :=-O binary -R .note -R .note.gnu.build-id -R .comment -S
>  GZFLAGS                :=-9
>  #CFLAGS                +=-pipe
>  # Explicitly specifiy 32-bit ARM ISA since toolchain default can be -mthumb:
> 

  reply	other threads:[~2008-06-11 15:08 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-06-11  7:40 [Buildroot] kernel image size depends on toolchain? Andreas Kuehn
2008-06-11  7:55 ` Peter Korsgaard
2008-06-11  8:38   ` Andreas Kuehn
2008-06-11  9:31     ` Peter Korsgaard
2008-06-11 10:20       ` Andreas Kuehn
2008-06-11 11:09         ` Peter Korsgaard
2008-06-11 13:00           ` Andreas Kuehn
2008-06-11 13:58             ` Peter Korsgaard
2008-06-11 15:08               ` Andreas Kuehn [this message]
2008-06-11 19:24                 ` [Buildroot] kernel image size depends on toolchain? -Solved- Peter Korsgaard
2008-06-11 21:30     ` [Buildroot] kernel image size depends on toolchain? Markus Heidelberg
2008-06-11  8:30 ` Matthew Dombroski
2008-06-11  8:49   ` Andreas Kuehn

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=484FEA68.2060507@gin.de \
    --to=andreas.kuehn@gin.de \
    --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