All of lore.kernel.org
 help / color / mirror / Atom feed
From: weber@corscience.de (Thomas Weber)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCHv2] ARM: zImage: Use $(CROSS_COMPILE)size to get .bss size
Date: Wed, 02 Nov 2011 13:35:28 +0100	[thread overview]
Message-ID: <4EB13910.8010203@corscience.de> (raw)
In-Reply-To: <alpine.LFD.2.02.1110131454340.17040@xanadu.home>

Am 13.10.2011 20:56, schrieb Nicolas Pitre:
> On Thu, 13 Oct 2011, Russell King - ARM Linux wrote:
>
>> On Thu, Oct 13, 2011 at 08:50:22AM +0200, Thomas Weber wrote:
>>> Use $(CROSS_COMPILE)size to determine the bss size
>>> from vmlinux.
>>>
>>> The problem is introduced in:
>>>
>>> commit 5ffb04f6690d71fab241b3562ebf52b893ac4ff1
>>> ARM: zImage: make sure appended DTB doesn't get
>>> overwritten by kernel .bss
>>>
>>> This fixes following error message:
>>>
>>> size: arch/arm/boot/compressed/../../../../vmlinux:
>>> File format is ambiguous
>>>
>>> size: Matching formats:
>>> elf32-littlearm
>>> elf32-littlearm-symbian
>>> elf32-littlearm-vxworks
>>>
>>> Acked-by: Nicolas Pitre <nicolas.pitre@linaro.org>
>>> Acked-by: Tony Lindgren <tony@atomide.com>
>>> Signed-off-by: Thomas Weber <weber@corscience.de>
>> This is going to totally break my ability to build any kernels at the
>> moment - for some reason I don't have an arm-linux-size with all the
>> other bits of binutils, so I've been relying on the x86 version so far.
> Naive suggestion: ln -s /usr/bin/size arm-linux-size
>
>
> Nicolas
>
>
Hello Russell,

what is the status of this patch?

Thomas

      reply	other threads:[~2011-11-02 12:35 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-10-13  6:50 [PATCHv2] ARM: zImage: Use $(CROSS_COMPILE)size to get .bss size Thomas Weber
2011-10-13  8:38 ` Russell King - ARM Linux
2011-10-13 18:56   ` Nicolas Pitre
2011-11-02 12:35     ` Thomas Weber [this message]

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=4EB13910.8010203@corscience.de \
    --to=weber@corscience.de \
    --cc=linux-arm-kernel@lists.infradead.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.