From: "Brian T" <btuch@usa.net>
To: <linux-mtd@lists.infradead.org>
Subject: Re: undefined reference to `__ffs'
Date: Fri, 27 Aug 2004 10:35:42 -0500 [thread overview]
Message-ID: <045201c48c4b$8407dc40$fd0ba8c0@briantpc> (raw)
In-Reply-To: 042901c48c42$2593cd30$fd0ba8c0@briantpc
> drivers/mtd/mtdlink.o: In function `cfi_intelext_partition_fixup':
> drivers/mtd/mtdlink.o(.text+0x76c6): undefined reference to `__ffs'
> make: *** [vmlinux] Error 1
>
Hmmm,
Looks like _ffs is defined in :
[root@Smog include]# grep -l -r "__ffs" *
asm-ia64/topology.h
asm-ia64/bitops.h
asm-ppc64/bitops.h
but in asm-i386/bitops.h it is defined as ffs()
So, should there be a macro rule for ffs->__ffs for compiling for i386?
-Brian
next prev parent reply other threads:[~2004-08-27 15:35 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-08-27 14:28 undefined reference to `__ffs' Brian T
2004-08-27 15:35 ` Brian T [this message]
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='045201c48c4b$8407dc40$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