Ah it was --disable-foreign. --disable-libffi is to use the bundled ffi instead of the host one, or something.
On 07/28/2011 11:42 AM, Jon Rafkind wrote: > I am trying to compile racket for a different architecture that libffi > is not ported to so I tried to use --disable-libffi but foreign/libffi > still gets configured. A) should that be happening and B) is there a way > around it? > > $ ../configure --disable-libffi --host=x86 > ... > configure: error: "libffi has not been ported to x86-unknown-none." > configure: error: ../../../foreign/libffi/configure failed for > foreign/libffi > > _________________________________________________ > For list-related administrative tasks: > http://lists.racket-lang.org/listinfo/dev _________________________________________________ For list-related administrative tasks: http://lists.racket-lang.org/listinfo/dev
