From: Jan Nieuwenhuizen <janneke@gnu.org>
To: linuxppc-dev@lists.linuxppc.org
Subject: silly config problem with .30
Date: Tue, 07 Dec 1999 14:07:23 +0100 [thread overview]
Message-ID: <199912071307.OAA07349@appel.flower> (raw)
How do these kind of silly problems get in, without being noticed/fixed?
(No offence intended, I just wonder where to jump into this process)
Where to get latest kernels, if not from kernel.org or vger (I heard
ppc is dead, at vger?)
--- /usr/src/linux/arch/ppc/config.in.30 Tue Dec 7 13:47:09 1999
+++ /usr/src/linux/arch/ppc/config.in Tue Dec 7 13:47:22 1999
@@ -85,9 +85,9 @@
if [ "$CONFIG_APUS" = "y" ]; then
define_bool CONFIG_PCI n
-else if [ "$CONFIG_OAK" = "y" ]; then
+elif [ "$CONFIG_OAK" = "y" ]; then
define_bool CONFIG_PCI n
-else if [ "$CONFIG_8xx" = "y" ]; then
+elif [ "$CONFIG_8xx" = "y" ]; then
bool 'QSpan PCI' CONFIG_PCI
else
define_bool CONFIG_PCI y
Jan.
--
Jan Nieuwenhuizen <janneke@gnu.org> | GNU LilyPond - The music typesetter
http://www.xs4all.nl/~jantien/ | http://www.lilypond.org/
** Sent via the linuxppc-dev mail list. See http://lists.linuxppc.org/
reply other threads:[~1999-12-07 13:07 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=199912071307.OAA07349@appel.flower \
--to=janneke@gnu.org \
--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).