linuxppc-dev.lists.ozlabs.org archive mirror
 help / color / mirror / Atom feed
From: linas@austin.ibm.com (Linas Vepstas)
To: Geoff Levand <geoffrey.levand@am.sony.com>,
	Arnd Bergmann <arnd@arndb.de>
Cc: linuxppc-dev@ozlabs.org
Subject: Bug report: CELL on linux-2.6.19-git7 won't build,
Date: Wed, 6 Dec 2006 13:27:45 -0600	[thread overview]
Message-ID: <20061206192745.GC17931@austin.ibm.com> (raw)


Hi Arnd, Geoff,

At this time, linux-2.6.19-git7 won't build when CELL is enabled, with the error

  CHECK   include/asm/spu_info.h
/kernels/kernel.org/linux-2.6.19-git7/usr/include/asm/spu_info.h requires asm/spu.h, which does not exist in exported headers

So I modified include/asm-powerpc/Kbuild only to get

  CHECK   include/asm/spu.h
/kernels/kernel.org/linux-2.6.19-git7/usr/include/asm/spu.h requires linux/workqueue.h, which does not exist in exported
headers

So I stripped everything out. I'm not sure what the correct fix is
suposed to be.

--linas

----
 include/asm-powerpc/Kbuild |    3 ++-
 1 file changed, 2 insertions(+), 1 deletion(-)

Index: linux-2.6.19-git7/include/asm-powerpc/Kbuild
===================================================================
--- linux-2.6.19-git7.orig/include/asm-powerpc/Kbuild	2006-12-05 17:11:02.000000000 -0600
+++ linux-2.6.19-git7/include/asm-powerpc/Kbuild	2006-12-06 13:13:08.000000000 -0600
@@ -17,7 +17,8 @@ header-y += ipc.h
 header-y += poll.h
 header-y += shmparam.h
 header-y += sockios.h
-header-y += spu_info.h
+# header-y += spu_info.h
+# header-y += spu.h
 header-y += ucontext.h
 header-y += ioctl.h
 header-y += linkage.h

             reply	other threads:[~2006-12-06 19:28 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-12-06 19:27 Linas Vepstas [this message]
2006-12-06 19:45 ` Bug report: CELL on linux-2.6.19-git7 won't build, Geoff Levand
2006-12-06 20:01   ` Linas Vepstas
2006-12-07 14:34     ` David Woodhouse

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=20061206192745.GC17931@austin.ibm.com \
    --to=linas@austin.ibm.com \
    --cc=arnd@arndb.de \
    --cc=geoffrey.levand@am.sony.com \
    --cc=linuxppc-dev@ozlabs.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).