I tried this compile with the debian 2.624 and 2.625 kernels and with the custom.deb source that had speakup compiled. Each time I got the same error, which I will show below. I think that without modification speakup won't compile on powerpc. I believe the reason to be the byte-order difference.I don't know the technical explanation but I know that the difference in byte-order was why I had to wait until brltty was modified to accommodate ppc; brltty itself would work but the characters that came up on the screen were some repetitive characters and not the text. I also know that espeak apparently doesn't work without having something done to espeak-data and I believe that also has to do with byte order, although I know it's possible because there's now an espeak install that works on Macosx--I believe on both ppc and intel. Since i do use brltty this isn't a major problem for me, but I was hoping to get speakup working. I just thought I'd post here so somebody else wouldn't spend a lot of time on this unless, of course, the person knows a way to fix the problem. Of course my theory could also be wrong, but I'm reasonably sure. Here's the error--it looks a little funny because i had a line length problem and did a paragraph fill. CHK include/linux/version.h CHK include/linux/utsrelease.h CALL scripts/checksyscalls.sh CHK include/linux/compile.h CALL arch/powerpc/kernel/systbl_chk.sh CC drivers/char/speakup/paramhelpers.o drivers/char/speakup/paramhelpers.c:23: error: conflicting types for ???set_bits??? include/asm/bitops.h:216: error: previous definition of ???set_bits??? was here make[3]: *** [drivers/char/speakup/paramhelpers.o] Error 1 make[2]: *** [drivers/char/speakup] Error 2 make[1]: *** [drivers/char] Error 2 make: *** [drivers] Error 2 -- Cheryl "Where your treasure is, there will your heart be also."
