All of lore.kernel.org
 help / color / mirror / Atom feed
From: Russell King <rmk+lkml@arm.linux.org.uk>
To: Linux Kernel List <linux-kernel@vger.kernel.org>
Cc: Sam Ravnborg <sam@ravnborg.org>
Subject: More ARM binutils fuckage
Date: Tue, 5 Dec 2006 19:33:57 +0000	[thread overview]
Message-ID: <20061205193357.GF24038@flint.arm.linux.org.uk> (raw)

There's not much to say about this, other than scream and go hide in the
corner.  ARM toolchains are just basically fscked.

  arm-linux-ld -EL  -p --no-undefined -X -o .tmp_vmlinux1 -T
 arch/arm/kernel/vmlinux.lds arch/arm/kernel/head.o
 arch/arm/kernel/init_task.o  init/built-in.o --start-group
  usr/built-in.o  arch/arm/kernel/built-in.o  arch/arm/mm/built-in.o
  arch/arm/common/built-in.o  arch/arm/mach-versatile/built-in.o
  arch/arm/nwfpe/built-in.o  arch/arm/vfp/built-in.o  kernel/built-in.o
  mm/built-in.o  fs/built-in.o  ipc/built-in.o  security/built-in.o
  crypto/built-in.o  block/built-in.o  arch/arm/lib/lib.a  lib/lib.a
  arch/arm/lib/built-in.o  lib/built-in.o  drivers/built-in.o
  sound/built-in.o  net/built-in.o --end-group

Produces no error, but:

$ arm-linux-nm ../build/versatile/.tmp_vmlinux1 |grep ' U '
         U __divdi3
         U __udivdi3
         U __umoddi3

Duh.

Result is you get successful kernel builds without any error, but a *bad*
incomplete image.  IOW, you do not know whether or not your kernel is
_safe_ to execute.

That's binutils 2.17.  binutils 2.16 had this problem and I tried to get a
patch into the kernel to use 'nm' to detect this fsckage.  We *need* this
patch in the kernel.

Sam, can we resurrect my attempts to do this please?

-- 
Russell King
 Linux kernel    2.6 ARM Linux   - http://www.arm.linux.org.uk/
 maintainer of:

             reply	other threads:[~2006-12-05 19:34 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-12-05 19:33 Russell King [this message]
2006-12-05 23:29 ` More ARM binutils fuckage Michael K. Edwards
2006-12-06  0:22   ` Russell King
2006-12-06  1:08     ` Lennert Buytenhek
2006-12-06  6:43       ` Re[2]: " Paul Sokolovsky
2006-12-06  8:17         ` Koen Kooi
2006-12-06 14:37         ` Re[2]: " Bruce Ashfield
2006-12-06  1:34     ` Michael K. Edwards
2006-12-06  0:25 ` Russell King

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=20061205193357.GF24038@flint.arm.linux.org.uk \
    --to=rmk+lkml@arm.linux.org.uk \
    --cc=linux-kernel@vger.kernel.org \
    --cc=sam@ravnborg.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.