From: Russell King <rmk@arm.linux.org.uk>
To: Jochen Striepe <jochen@tolot.escape.de>
Cc: linux-kernel@vger.kernel.org
Subject: Re: 2.4.4-pre6 does not compile
Date: Sat, 21 Apr 2001 21:34:30 +0100 [thread overview]
Message-ID: <20010421213430.D7576@flint.arm.linux.org.uk> (raw)
In-Reply-To: <20010421221728.C4077@tolot.escape.de>
In-Reply-To: <20010421221728.C4077@tolot.escape.de>; from jochen@tolot.escape.de on Sat, Apr 21, 2001 at 10:17:28PM +0200
On Sat, Apr 21, 2001 at 10:17:28PM +0200, Jochen Striepe wrote:
> 2.4.4-pre6 actually is the 4th 2.4.4pre-Patch that does not compile
> without further patching on my system. :-(
> rwsem.o(.text+0x30): undefined reference to `__builtin_expect'
> rwsem.o(.text+0x73): undefined reference to `__builtin_expect'
Its because you're using a version of gcc which doesn't have
__builtin_expect (eg, egcs 1.1.2, some versions of gcc 2.95).
I'm told that gcc 2.95.[12] are not suitable for kernel compilation...
I've currently got the following in my tree (sorry, no diff since I've
got other changes in this file). lib/rwsem.c, line 9, add:
#if __GNUC__ < 2 || (__GNUC__ == 2 && __GNUC_MINOR__ < 96)
#define __builtin_expect(exp,c) (exp)
#endif
I'm not sure if this is correct, or which compilers work, which don't
(so don't anyone go and drop it into Linus/Alans kernels), but it
seems to work for me.
--
Russell King (rmk@arm.linux.org.uk) The developer of ARM Linux
http://www.arm.linux.org.uk/personal/aboutme.html
next prev parent reply other threads:[~2001-04-21 20:34 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-04-21 20:17 2.4.4-pre6 does not compile Jochen Striepe
2001-04-21 20:34 ` Russell King [this message]
2001-04-21 20:44 ` Philip Blundell
2001-04-23 20:14 Jörn Nettingsmeier
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=20010421213430.D7576@flint.arm.linux.org.uk \
--to=rmk@arm.linux.org.uk \
--cc=jochen@tolot.escape.de \
--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;
as well as URLs for NNTP newsgroup(s).