From: "Iain Sandoe" <iain@sandoe.co.uk>
To: Rolf Liu <rolfl@sc23.sc.mcel.mot.com>, linuxppc-dev@lists.linuxppc.org
Subject: Re: problems about __cli()
Date: Thu, 20 Jul 2000 10:19:54 +0100 [thread overview]
Message-ID: <200007200919.KAA12257@hyperion.valhalla.net> (raw)
Hi Rolf,
Thu, Jul 20, 2000, Rolf Liu wrote:
> I am currently compiling the kernel 2.2.13.
> A problem occours, it said the "__cli() is not defined".
> I wonder where the __cli() is defined in the kernel tree, which file is it
> in ?
> thanks a lot.
(at 2.2.17preZZ - any reason for using 2.2.13?)
Where "your-kernel-foo-bar" is the source tree you are working with:
__cli() is defined in:
/usr/src/your-kernel-foo-bar/include/asm-ppc/system.h
asm-ppc is symlinked to /usr/src/your-kernel-foo-bar/include/asm by the
build process.
the function is implemented in:
/usr/src/your-kernel-foo-bar/arch/ppc/kernel/misc.S
It is *vital* to make sure that there is a symlink named 'linux' in /usr/src
that points to your /usr/src/your-kernel-foo-bar/ because there are symlinks
in /usr/include that expect to use this to find the build-specific headers.
hope this helps,
Iain.
** Sent via the linuxppc-dev mail list. See http://lists.linuxppc.org/
next reply other threads:[~2000-07-20 9:19 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2000-07-20 9:19 Iain Sandoe [this message]
2000-07-20 12:55 ` problems about __cli() Josh Huber
2000-07-20 13:36 ` Michael Schmitz
-- strict thread matches above, loose matches on Subject: below --
2000-07-21 14:37 Iain Sandoe
2000-07-20 13:45 Iain Sandoe
2000-07-20 15:44 ` Josh Huber
2000-07-22 14:10 ` Geert Uytterhoeven
2000-07-22 18:11 ` Martin Costabel
2000-07-24 12:19 ` Josh Huber
2000-07-24 15:01 ` Jeff Garzik
2000-07-21 14:15 ` Michel Dänzer
2000-07-20 7:29 Rolf Liu
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=200007200919.KAA12257@hyperion.valhalla.net \
--to=iain@sandoe.co.uk \
--cc=linuxppc-dev@lists.linuxppc.org \
--cc=rolfl@sc23.sc.mcel.mot.com \
/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).