From: Peter Cordes <peter@llama.nslug.ns.ca>
To: linuxppc-dev@lists.linuxppc.org
Subject: bk tree doesn't build because of cputable.h
Date: Sat, 14 Apr 2001 22:56:06 -0300 [thread overview]
Message-ID: <20010414225606.A7020@llama.nslug.ns.ca> (raw)
For some reason, the patch in
http://lists.linuxppc.org/listarcs/linuxppc-dev/200104/msg00130.html
was applied to the bk tree. (I rsync'ed against it from
penguinppc.org/linux-2.4-bk yesterday, and again today.) cputable.h doesn't
exist in that tree, so it breaks when I try to build the kernel. Removing
the #include makes the kernel build succeed. Somebody should fix this. :>
(please CC on reply, I'm not subscribed to the list.)
--
#define X(x,y) x##y
Peter Cordes ; e-mail: X(peter@llama.nslug. , ns.ca)
"The gods confound the man who first found out how to distinguish the hours!
Confound him, too, who in this place set up a sundial, to cut and hack
my day so wretchedly into small pieces!" -- Plautus, 200 BCE
** Sent via the linuxppc-dev mail list. See http://lists.linuxppc.org/
next reply other threads:[~2001-04-15 1:56 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-04-15 1:56 Peter Cordes [this message]
2001-04-15 13:24 ` bk tree doesn't build because of cputable.h Benjamin Herrenschmidt
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=20010414225606.A7020@llama.nslug.ns.ca \
--to=peter@llama.nslug.ns.ca \
--cc=linuxppc-dev@lists.linuxppc.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).