On Thu, Nov 28, 2013 at 04:49:01PM +0100, Christian Weisgerber wrote: > 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 > ...
When I was helping with the port on openbsd-wip, I tried the compilation without libcompat and pypy didn't compile. Unfortunatelly, I don't remember what was the error. -- Juan Francisco Cantero Hurtado http://juanfra.info
