Mysteriously, PyPy appears to link with libcompat during the build. >From a brief look, I couldn't even figure out where this is coming from. Anybody know what this is about? It's hard to imagine that PyPy would actually need libcompat.
[translation:info] [PyPy 2.1.0] [platform:msg] Set platform with 'host' cc=None, using cc='cc' [translation:info] Translating target as defined by targetpypystandalone [platform:execute] cc -c -pthread -fomit-frame-pointer -D_BSD_SOURCE -O2 -pipe -I/usr/local/include /usr/obj/pypy-2.1/usession/gcctest.c -o /usr/obj/pypy-2.1/usession/gcctest.o [platform:execute] cc /usr/obj/pypy-2.1/usession/gcctest.o -L/usr/local/lib -pthread -lcompat -lintl -liconv -o /usr/obj/pypy-2.1/usession/gcctest [platform:execute] cc -c -pthread -fomit-frame-pointer -D_BSD_SOURCE -O2 -pipe -I/usr/local/include /usr/obj/pypy-2.1/usession/gcctest.c -o /usr/obj/pypy-2.1/usession/gcctest.o [platform:execute] cc /usr/obj/pypy-2.1/usession/gcctest.o -L/usr/local/lib -pthread -lcompat -lintl -liconv -o /usr/obj/pypy-2.1/usession/gcctest ... -- Christian "naddy" Weisgerber na...@mips.inka.de
