public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Russell King - ARM Linux <linux@arm.linux.org.uk>
To: Kristoffer Ericson <kristoffer.ericson@gmail.com>
Cc: Linux-arm <linux-arm-kernel@lists.arm.linux.org.uk>,
	linux-main <linux-kernel@vger.kernel.org>
Subject: Re: [BUG] : kernel/built-in.o(.text+0x18db4):kernel/workqueue.c:823: undefined reference to `.L343'
Date: Fri, 2 Nov 2007 19:48:18 +0000	[thread overview]
Message-ID: <20071102194818.GA22719@flint.arm.linux.org.uk> (raw)
In-Reply-To: <20071102202931.deb09211.Kristoffer.ericson@gmail.com>

On Fri, Nov 02, 2007 at 08:29:31PM -0700, Kristoffer Ericson wrote:
> Greetings,
> 
> Haven't found anyone reporting this. Taken from the very latest linux-2.6.git pull.
> 
> dnsdomainname: Unknown host
>   UPD     include/linux/compile.h
>   CC      init/version.o
>   LD      init/built-in.o
>   LD      .tmp_vmlinux1
> kernel/built-in.o(.text+0x18db0): In function `destroy_workqueue':
> kernel/workqueue.c:823: undefined reference to `.L342'
> kernel/built-in.o(.text+0x18db4):kernel/workqueue.c:823: undefined reference to `.L343'
> make: *** [.tmp_vmlinux1] Error 1

I think you'll have to look at the assembly produced for workqueue.c and
work out why GCC is referencing an undefined label.  You can get the
assembly for that by doing:

make ARCH=arm ...etc... kernel/workqueue.s

and then you'll have a kernel/workqueue.s in your object tree.

  reply	other threads:[~2007-11-02 19:48 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-11-03  3:29 [BUG] : kernel/built-in.o(.text+0x18db4):kernel/workqueue.c:823: undefined reference to `.L343' Kristoffer Ericson
2007-11-02 19:48 ` Russell King - ARM Linux [this message]
2007-11-02 20:10   ` Sam Ravnborg
2007-11-03  7:04     ` Kristoffer Ericson
2007-11-03  0:04       ` Russell King - ARM Linux
2007-11-03  8:43         ` Kristoffer Ericson

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=20071102194818.GA22719@flint.arm.linux.org.uk \
    --to=linux@arm.linux.org.uk \
    --cc=kristoffer.ericson@gmail.com \
    --cc=linux-arm-kernel@lists.arm.linux.org.uk \
    --cc=linux-kernel@vger.kernel.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox