-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Andrew Wilkinson wrote:
Excellent, we're getting somewhere. I've pushed another patch to correct that.
Unfortunately I'm completly guessing as to which files need to be compiled for libffi to work on ppc platforms.
Now the error is: gcc -I. -Idepends/ctypes/libffi/include - -Idepends/ctypes/libffi/src/powerpc -Idepends/ctypes/libffi/include - -Idepends/ctypes/libffi/src/powerpc -Idepends/ctypes/libffi -c -o depends/ctypes/libffi/src/powerpc/sysv.o depends/ctypes/libffi/src/powerpc/sysv.S depends/ctypes/libffi/src/powerpc/sysv.S:29:25: error: powerpc/asm.h: No such file or directory scons: *** [depends/ctypes/libffi/src/powerpc/sysv.o] Error 1 scons: building terminated because of errors. There is a depends/ctypes/libffi/src/powerpc/asm.h that I assume it's trying to include, (also there is src/runtime/libffi/src/powerpc/asm.h ...), hmm...
If it doesn't work you could try fiddling with the files listed in /local/d0p6/aw/yhc/build, line 25. The files in that list need to be taken from yhc/depends/ctypes/libffi/src/powerpc (apart from the first two).
I can't find whatever file "/local/d0p6/aw/yhc/build" you're referring to... What is Yhc doing that depends on the machine architecture? Is all this ctypes, libffi, endianness testing, etc, just for the Haskell Foreign Function Interface? Maybe it would help if I understood the organization of these platform-specific things (if there is any yet). (speculation) : Maybe it would be good to separate them out into one place so that it's easy to see where any such thing occurs, and check that (if things need to be split into cases by architecture) all supported cases are covered. It would be nice to be able to build the completely-portable parts of Yhc (i.e. everything but the FFI) without relying on anything but a bytecode interpreter (ANSI C compiler for usual Yhc bytecode interpreter, .NET, whatever). Then we could be at least as portable as Lua, though maybe not as memory-efficient. :) (And I could test the parts of Yhc that do work for me.) Isaac -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.2.2 (GNU/Linux) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org iD8DBQFEzjJCHgcxvIWYTTURArHvAJsGSd5EsJ4yyB+d/HRCSkh3Byd5fQCfTltZ 7yLuprOydmJifhELnWhLvAo= =WEmd -----END PGP SIGNATURE-----