public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Kristoffer Ericson <kristoffer.ericson@gmail.com>
To: Sam Ravnborg <sam@ravnborg.org>
Cc: Russell King - ARM Linux <linux@arm.linux.org.uk>,
	Kristoffer Ericson <kristoffer.ericson@gmail.com>,
	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: Sat, 3 Nov 2007 00:04:06 -0700	[thread overview]
Message-ID: <20071103000406.30654cff.Kristoffer.ericson@gmail.com> (raw)
In-Reply-To: <20071102201023.GA16670@uranus.ravnborg.org>

On Fri, 2 Nov 2007 21:10:23 +0100
Sam Ravnborg <sam@ravnborg.org> wrote:

> On Fri, Nov 02, 2007 at 07:48:18PM +0000, Russell King - ARM Linux wrote:
> > 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
> Or make that:
> 
> make ARCH=arm ...etc... kernel/workqueue.lst
> 
> to get intermixed C and assenbly
> 
> 	Sam
arm-unknown-linux-gnu- kernel/workqueue.1strrent:)$ make ARCH=arm CROSS_COMPILE=a
make: *** No rule to make target `kernel/workqueue.1st'.  Stop.
arm-unknown-linux-gnu- kernel/workqueue.lstrrent:)$ make ARCH=arm CROSS_COMPILE=a
  CHK     include/linux/version.h
make[1]: `include/asm-arm/mach-types.h' is up to date.
  CHK     include/linux/utsrelease.h
  CALL    scripts/checksyscalls.sh
<stdin>:1097:2: warning: #warning syscall fadvise64 not implemented
<stdin>:1265:2: warning: #warning syscall migrate_pages not implemented
<stdin>:1321:2: warning: #warning syscall pselect6 not implemented
<stdin>:1325:2: warning: #warning syscall ppoll not implemented
<stdin>:1365:2: warning: #warning syscall epoll_pwait not implemented
  MKLST   kernel/workqueue.lst
No System.map

  reply	other threads:[~2007-11-02 23:04 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
2007-11-02 20:10   ` Sam Ravnborg
2007-11-03  7:04     ` Kristoffer Ericson [this message]
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=20071103000406.30654cff.Kristoffer.ericson@gmail.com \
    --to=kristoffer.ericson@gmail.com \
    --cc=linux-arm-kernel@lists.arm.linux.org.uk \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux@arm.linux.org.uk \
    --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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox