Richard Emslie wrote:
listdir()
:-) Yes arrrggghhhh!! But no fault of yours - just that we use a
(llvm) C compiler for externs. If a local compiler is not available, we
go to a remote machine to generate llvm code. So local includes are not
possible - hence in genllvm we manually include C files from #include
statements. :-(
Now listdir() uses opaque (dont know if you introduced this or someone
else) - and llvm doesnt have proper support for opaque types... yet. So
we cannot compile pypy right now.
No, it was Armin :-)
I had the same trouble, windows didn't compile any longer, so I had
to build support. Now you have the same problem :-)
Maybe easiest to get around this is to just comment the interface
away. Then you have time.
Sorry for the negativeness. It would be interesting however to have the
core developers opinion(s) about backends in general and whether it is
believed maintaining it (the llvm one) is a worthwhile goal.
I felt a little like this for windows, although without reason because
it is really needed.
In a sense, someone jumps into a direction and we have to follow,
this is not bad after all.
But I think it makes sense to ask what the plans concerning LLVM
are, and who is willing to support it. Maybe pypy-sync?
ciao - chris
--
Christian Tismer :^) <mailto:[EMAIL PROTECTED]>
tismerysoft GmbH : Have a break! Take a ride on Python's
Johannes-Niemeyer-Weg 9A : *Starship* http://starship.python.net/
14109 Berlin : PGP key -> http://wwwkeys.pgp.net/
work +49 30 802 86 56 mobile +49 173 24 18 776 fax +49 30 80 90 57 05
PGP 0x57F3BF04 9064 F4E1 D754 C2FF 1619 305B C09C 5A3B 57F3 BF04
whom do you want to sponsor today? http://www.stackless.com/
_______________________________________________
[email protected]
http://codespeak.net/mailman/listinfo/pypy-dev
