<div><div class="gmail_quote">2011/8/19 Caleb Hattingh <span dir="ltr"><<a href="mailto:caleb.hattingh@gmail.com">caleb.hattingh@gmail.com</a>></span><br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex;">
<div class="im">On 19 August 2011 14:48, Caleb Hattingh <<a href="mailto:caleb.hattingh@gmail.com">caleb.hattingh@gmail.com</a>> wrote:<br>
> I have tried placing ffi.h (and ffi_common.h and ffitarget.h) in<br>
> various strategic places, but to no avail.<br>
<br>
</div>It seems this particular problem (libffi for mingw) was discussed in<br>
IRC by Varriount:<br>
<br>
<a href="http://www.tismer.com/pypy/irc-logs/pypy/pypy.2011-07-21.log.html" target="_blank">http://www.tismer.com/pypy/irc-logs/pypy/pypy.2011-07-21.log.html</a><br>
<br>
Unfortunately, the chat logs shed no light.<br></blockquote><div> </div><div>I had the same issue with a machine where libffi-dev is not available.</div><div><br></div><div>The first fix is to modify pypy/jit/metainterp/optimizeopt/fficall.py</div>
<div>and move the line "from pypy.rlib.libffi import Func" shortly before</div><div>the place where "Func" is used.</div><div><br></div><div>Then, I don't remember whether the options "--withoutmod-_ffi --withoutmod-_rawffi"</div>
<div>were necessary. These modules (i.e ctypes) won't be available anyway.<br><div><br></div><div><br></div><div>-- </div></div></div>Amaury Forgeot d'Arc<br>
</div>