From: "Brian T" <btuch@usa.net>
To: <linux-mtd@lists.infradead.org>
Subject: undefined reference to `__ffs'
Date: Fri, 27 Aug 2004 09:28:38 -0500 [thread overview]
Message-ID: <042901c48c42$2593cd30$fd0ba8c0@briantpc> (raw)
Hi,
With kernel 2.4.27 and the snapshot patch from 8/26 (yesterday) I am getting
the following error :
make[1]: Leaving directory
`/usr/src/Lineo/current_build2/linux-2.4.27/arch/i386/lib'
ld -m elf_i386 -T
/usr/src/Lineo/current_build2/linux-2.4.27/arch/i386/vmlinux.lds -e stext
arch/i386/kernel/head.o arch/i386/kernel/init_task.o init/main.o
init/version.o init/do_mounts.o \
--start-group \
arch/i386/kernel/kernel.o arch/i386/mm/mm.o kernel/kernel.o mm/mm.o
fs/fs.o ipc/ipc.o \
drivers/char/char.o drivers/block/block.o drivers/misc/misc.o
drivers/net/net.o drivers/pci/driver.o drivers/mtd/mtdlink.o
drivers/net/pcmcia/pcmcia_net.o drivers/media/media.o \
net/network.o \
/usr/src/Lineo/current_build2/linux-2.4.27/arch/i386/lib/lib.a
/usr/src/Lineo/current_build2/linux-2.4.27/lib/lib.a
/usr/src/Lineo/current_build2/linux-2.4.27/arch/i386/lib/lib.a \
--end-group \
-o vmlinux
drivers/mtd/mtdlink.o: In function `cfi_intelext_partition_fixup':
drivers/mtd/mtdlink.o(.text+0x76c6): undefined reference to `__ffs'
make: *** [vmlinux] Error 1
Any ideas?
-Brian
next reply other threads:[~2004-08-27 14:28 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-08-27 14:28 Brian T [this message]
2004-08-27 15:35 ` undefined reference to `__ffs' Brian T
2004-08-27 16:05 ` Nicolas Pitre
2004-08-27 18:04 ` Brian T
2004-08-27 18:10 ` Josh Boyer
2004-08-27 18:26 ` David Woodhouse
2004-08-27 18:25 ` Thomas Gleixner
2004-08-27 19:22 ` Brian T
2004-08-30 16:36 ` Brian T
2004-08-30 17:52 ` Josh Boyer
2004-08-30 18:20 ` Brian T
2004-08-30 18:35 ` Josh Boyer
2004-08-30 18:53 ` Nicolas Pitre
2004-08-30 19:04 ` Josh Boyer
2004-08-30 20:03 ` Nicolas Pitre
2004-08-30 20:20 ` Josh Boyer
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='042901c48c42$2593cd30$fd0ba8c0@briantpc' \
--to=btuch@usa.net \
--cc=linux-mtd@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox