From: klink@clouddancer.com (Colonel)
To: linux-kernel@vger.kernel.org
Subject: Re: rwsem.o undefined reference to __builtin_expect
Date: Mon, 23 Apr 2001 15:08:41 -0700 (PDT) [thread overview]
Message-ID: <20010423220841.949546808@mail.clouddancer.com> (raw)
In-Reply-To: <9c18id$bb$1@ns1.clouddancer.com>
In-Reply-To: <Pine.LNX.4.33.0104231211530.519-100000@boston.corp.fedex.com> <9c18id$bb$1@ns1.clouddancer.com>
In list.kernel, you wrote:
>
>
>cannot compile 2.4.4-pre6. This may have been reported, but I
>haven't seen it.
There was a solution mentioned Saturday.
>rwsem.o(.text+0x30): undefined reference to `__builtin_expect'
>rwsem.o(.text+0x73): undefined reference to `__builtin_expect'
>make: *** [vmlinux] Error 1
in asm-alpha/compiler.h you will find a definition. The above
solution created a new file (asm-i386/compiler.h) with the definition,
I just added it to rwsem.c.
BTW: 2.4.4-pre6 is the fastest kernel yet! YMMV
prev parent reply other threads:[~2001-04-23 22:10 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-04-23 4:14 rwsem.o undefined reference to __builtin_expect Jeff Chua
[not found] ` <9c18id$bb$1@ns1.clouddancer.com>
2001-04-23 22:08 ` Colonel [this message]
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=20010423220841.949546808@mail.clouddancer.com \
--to=klink@clouddancer.com \
--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