on further investigation there are only 2 symbols that mess it up
the first one is __fdelt_chk - its used by the _FORTIFY_SOURCE feature of some FD_* macros related to select, requiring 2.15 abi.
the second one is requiring memcpy on the 2.14 abi as far as i can tell all other symbols go for the old versions -- Ronny On 01/11/2013 11:56 AM, Ronny Pfannschmidt wrote:
Hello, since glibc actually carries backward compatible abi versions, i just wondered if it was possible to link to those older abi versions even on new systems in order to support older systems. so i goggled a bit and found an answer on http://stackoverflow.com/questions/4032373/linking-against-an-old-version-of-libc-to-provide-greater-application-coverage it appears that its enough to emit something like __asm__(".symver realpath,realpath@GLIBC_2.2.5"); in order to request the older symbol versions i think if instructions like those where added when writing out the c code, the night-lies could work on other systems like Debian again. i'd like to ask for opinions on adding such statements and a starting point on how to integrate it with the ExternalCompilationInfo. best, Ronny _______________________________________________ pypy-dev mailing list pypy-dev@python.org http://mail.python.org/mailman/listinfo/pypy-dev
_______________________________________________ pypy-dev mailing list pypy-dev@python.org http://mail.python.org/mailman/listinfo/pypy-dev
