From: Arkadiy Chapkis - Arc <achapkis@mail.dls.net>
To: LINUX-KERNEL@vger.kernel.org
Subject: thread_info implementation
Date: Mon, 11 Feb 2002 11:39:02 -0600 [thread overview]
Message-ID: <00A09679.2A996F5D.164@mail.dls.net> (raw)
[1.] One line summary of the problem: Can't compile kernel 2.5.4
[2.] Full description of the problem/report: After configuring and starting
compilation, there are messages:
In file included from
/usr/local/src/test/linux-2.5.4/include/linux/spinlock.h:7,
from
/usr/local/src/test/linux-2.5.4/include/linux/module.h:11,
from loop.c:55:
/usr/local/src/test/linux-2.5.4/include/linux/thread_info.h:10:29:
asm/thread_info.h: No such file or directory
[4.] Kernel version (from /proc/version): Current is 2.4.16, downloaded is
2.5.4
# cat /proc/version
Linux version 2.4.16 (root@yakov.dls.net) (gcc version 2.96 20000731 (Red Hat
Linux 7.1 2.96-99))
[7.] Environment AlphaStation 200 4/233
[7.2.] Processor information (from /proc/cpuinfo):
# cat /proc/cpuinfo
cpu : Alpha
cpu model : EV4
cpu variation : 0
cpu revision : 0
cpu serial number : Linux_is_Great!
system type : Avanti
system variation : 0
system revision : 0
system serial number : MILO-2.0.35-c5.
cycle frequency [Hz] : 233313780
timer frequency [Hz] : 1024.00
page size [bytes] : 8192
phys. address bits : 34
max. addr. space # : 63
BogoMIPS : 458.36
kernel unaligned acc : 90143620 (pc=fffffc00004db7b0,va=fffffc000056830a)
user unaligned acc : 90 (pc=1200bb3f0,va=12028b87a)
platform string : N/A
cpus detected : 0
[X.] Other notes, patches, fixes, workarounds: Apperently the thread_info
implementation for sparc platform broke alpha platform as there is no
asm/thread_info.h file.
Thanks you,
Arc C.
achapkis@dls.net
achapkis@shark.dls.net
next reply other threads:[~2002-02-11 17:41 UTC|newest]
Thread overview: 56+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-02-11 17:39 Arkadiy Chapkis - Arc [this message]
2002-02-11 20:19 ` thread_info implementation Robert Love
2002-02-11 20:42 ` Luigi Genoni
2002-02-11 20:48 ` Robert Love
2002-02-11 23:37 ` Jeff Garzik
2002-02-11 23:49 ` Richard Henderson
2002-02-12 0:09 ` Dave Jones
2002-02-12 0:20 ` Jeff Garzik
2002-02-12 0:24 ` Dave Jones
-- strict thread matches above, loose matches on Subject: below --
2002-02-11 21:08 Roman Zippel
2002-02-11 20:50 ` Anton Blanchard
2002-02-12 0:46 ` David S. Miller
2002-02-12 0:57 ` Roman Zippel
2002-02-12 0:57 ` David S. Miller
2002-02-12 1:10 ` Roman Zippel
2002-02-12 13:01 ` Bjorn Wesen
2002-02-12 13:49 ` David S. Miller
2002-02-12 1:01 ` David Mosberger
2002-02-12 1:07 ` David S. Miller
2002-02-12 1:21 ` David Mosberger
2002-02-12 1:32 ` David S. Miller
2002-02-12 1:36 ` David Mosberger
2002-02-12 1:41 ` David S. Miller
2002-02-12 1:53 ` David Mosberger
2002-02-12 2:22 ` David S. Miller
2002-02-12 2:30 ` David Mosberger
2002-02-12 2:36 ` David S. Miller
2002-02-12 2:46 ` David Mosberger
2002-02-12 2:51 ` David S. Miller
2002-02-12 3:01 ` David Mosberger
2002-02-12 3:04 ` David S. Miller
2002-02-12 3:18 ` David Mosberger
2002-02-12 3:23 ` David S. Miller
2002-02-12 3:32 ` David Mosberger
2002-02-12 3:42 ` David S. Miller
2002-02-12 4:16 ` David Mosberger
2002-02-12 4:21 ` David S. Miller
2002-02-12 4:33 ` David Mosberger
2002-02-12 5:26 ` Richard Henderson
2002-02-12 5:32 ` David S. Miller
2002-02-12 5:50 ` David Mosberger
2002-02-12 5:57 ` Richard Henderson
2002-02-13 11:18 ` Anton Blanchard
2002-02-12 17:14 ` Pavel Machek
2002-02-13 0:46 ` David S. Miller
2002-02-13 1:30 ` Roman Zippel
2002-02-12 9:12 ` Roman Zippel
2002-02-12 9:30 ` Jeff Garzik
2002-02-12 10:14 ` Roman Zippel
2002-02-12 13:21 ` David Howells
2002-02-12 19:15 ` David Mosberger
2002-02-12 19:38 ` David Howells
2002-02-12 2:49 ` Davide Libenzi
2002-02-12 0:01 ` Roman Zippel
2002-02-12 0:10 ` David Howells
2002-02-12 0:22 ` Roman Zippel
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=00A09679.2A996F5D.164@mail.dls.net \
--to=achapkis@mail.dls.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