From: Klaus Knopper <knopper@knopper.net>
To: linux-kernel@vger.kernel.org
Subject: compile error for 2.6.18-git19 with CONFIG_RWSEM_GENERIC_SPINLOCK=y
Date: Tue, 3 Oct 2006 21:20:00 +0200 [thread overview]
Message-ID: <20061003192000.GG6710@knopper.net> (raw)
Hello everyone,
Since the "reporting bugs" FAQ told me to post here in case I can't
identify the right person to ask, and have not found any mention of this
problem on the list and anywhere else yet, I do.
Problem description: Compiling 2.6.18-git19 (gcc-3.3 and 4.1) fails for
processor family i386 (when CONFIG_RWSEM_GENERIC_SPINLOCK=y) is set,
with
arch/i386/lib/lib.a(semaphore.o): In function `call_rwsem_down_read_failed':
arch/i386/lib/semaphore.S:(.sched.text+0x5f): undefined reference to `rwsem_down_read_failed'
arch/i386/lib/lib.a(semaphore.o): In function `call_rwsem_down_write_failed':
arch/i386/lib/semaphore.S:(.sched.text+0x6a): undefined reference to `rwsem_down_write_failed'
arch/i386/lib/lib.a(semaphore.o): In function `call_rwsem_wake':
arch/i386/lib/semaphore.S:(.sched.text+0x76): undefined reference to `rwsem_wake'
arch/i386/lib/lib.a(semaphore.o): In function `call_rwsem_downgrade_wake':
arch/i386/lib/semaphore.S:(.sched.text+0x7f): undefined reference to `rwsem_downgrade_wake'
This option is present in .config when setting processor family to
plain "i386" in make menuconfig.
Using CONFIG_RWSEM_XCHGADD_ALGORITHM=y INSTEAD of
CONFIG_RWSEM_GENERIC_SPINLOCK=y (i486 and up) kind of "fixes" the
compile error, but I'm not sure if the resulting code would still run on
a real i386.
This problem also exists for ealier gits, but I can't tell exactly when
it started.
Regards
-Klaus Knopper
PS: Please CC any answers to me, since I'm not a subscriber to this list.
next reply other threads:[~2006-10-03 19:20 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-10-03 19:20 Klaus Knopper [this message]
2006-10-05 8:16 ` [PATCH] Re: compile error for 2.6.18-git19 with CONFIG_RWSEM_GENERIC_SPINLOCK=y Jarek Poplawski
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=20061003192000.GG6710@knopper.net \
--to=knopper@knopper.net \
--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