linuxppc-dev.lists.ozlabs.org archive mirror
 help / color / mirror / Atom feed
From: Andreas Bogk <andreas@andreas.org>
To: linuxppc-dev@lists.linuxppc.org
Subject: Re: 2.3.3 compile error on ppc
Date: 19 May 1999 20:09:22 +0200	[thread overview]
Message-ID: <m31zgd0w4t.fsf@soma.andreas.org> (raw)
In-Reply-To: Hollis R Blanchard's message of "Wed, 19 May 1999 13:19:20 -0400 (EDT)"


Hollis R Blanchard <hollis+@andrew.cmu.edu> writes:

> be broken for us for a little. Were you having problems with 2.2.x?

There is a problem with 2.2.9, and here's the patch:

diff -r -u linux-2.2.9/arch/ppc/kernel/syscalls.c linux/arch/ppc/kernel/syscalls.c
--- linux-2.2.9/arch/ppc/kernel/syscalls.c	Sat May  8 20:14:01 1999
+++ linux/arch/ppc/kernel/syscalls.c	Wed May 19 18:36:23 1999
@@ -30,6 +30,7 @@
 #include <linux/shm.h>
 #include <linux/stat.h>
 #include <linux/mman.h>
+#include <linux/file.h>
 #include <linux/sys.h>
 #include <linux/ipc.h>
 #include <linux/utsname.h>

I wonder why such trivial problems creep into so-called stable
releases of the Linux kernel again and again. Does nobody care that on
i386, you just go to ftp.kernel.org and download the latest version
and it just works, whereas on PowerPC you have to find out:

- what CVS is
- what vger is
- what CVS tags are
- which tag the one is which gives you a stable version ?

I don't care that the development kernel breaks on PPC. But that the
official stable kernel breaks is a huge problem.

Andreas

-- 
Reality is two's complement. See:
ftp://ftp.netcom.com/pub/hb/hbaker/hakmem/hacks.html#item154

[[ This message was sent via the linuxppc-dev mailing list.  Replies are ]]
[[ not  forced  back  to the list, so be sure to Cc linuxppc-dev if your ]]
[[ reply is of general interest. Please check http://lists.linuxppc.org/ ]]
[[ and http://www.linuxppc.org/ for useful information before posting.   ]]

  reply	other threads:[~1999-05-19 18:09 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
1999-05-19 16:14 2.3.3 compile error on ppc Mark Lin
1999-05-19 17:19 ` Hollis R Blanchard
1999-05-19 18:09   ` Andreas Bogk [this message]
1999-05-19 19:30     ` Tom Rini
1999-05-19 22:19       ` Hollis R Blanchard
1999-05-19 21:21     ` Martin Costabel
1999-05-19 21:01   ` Martin Costabel
1999-05-19 21:20     ` Mark Lin
1999-05-19 21:41       ` Martin Costabel

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=m31zgd0w4t.fsf@soma.andreas.org \
    --to=andreas@andreas.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).