Compiling PyPy 1.5 fails on Slackware 13.37
Hi, I've reported this on #pypy yesterday, but I thought this might be a better place for this kind of information. I've tried to build PyPy 1.5 from source on Slackware 13.37 (32-bit LXC container, while the host and kernel are 64-bit; both systems Slackware) and got an exception[0] in the last stage of the build process (compilation). [0] http://paste.pocoo.org/show/387121/ Here are some bits of information about the system used: gcc 4.5.2, glibc 2.13. If you need anything else, I'll be happy to report it. I also still have all the .c files created by translation process, if any of those are needed, just tell me where to send them. -- Audrius Kažukauskas
2011/5/12 Audrius Kažukauskas <audrius@neutrino.lt>:
Hi,
I've reported this on #pypy yesterday, but I thought this might be a better place for this kind of information.
I've tried to build PyPy 1.5 from source on Slackware 13.37 (32-bit LXC container, while the host and kernel are 64-bit; both systems Slackware) and got an exception[0] in the last stage of the build process (compilation).
[0] http://paste.pocoo.org/show/387121/
Here are some bits of information about the system used: gcc 4.5.2, glibc 2.13. If you need anything else, I'll be happy to report it. I also still have all the .c files created by translation process, if any of those are needed, just tell me where to send them.
testing_1.s or testing_1.c would be cool to have
-- Audrius Kažukauskas
_______________________________________________ pypy-dev mailing list pypy-dev@python.org http://mail.python.org/mailman/listinfo/pypy-dev
On Thu, 2011-05-12 at 12:12:15 +0200, Maciej Fijalkowski wrote:
Here are some bits of information about the system used: gcc 4.5.2, glibc 2.13. If you need anything else, I'll be happy to report it. I also still have all the .c files created by translation process, if any of those are needed, just tell me where to send them.
testing_1.s or testing_1.c would be cool to have
See attached both testing_1.c and testing_1.s. -- Audrius Kažukauskas
Hi, The problem should be fixed now (017e187b2716). Can you try again? Hopefully I didn't break Windows or Mac builds, but I cannot easily be sure. Feel free to blame me if I did :-) A bientôt, Armin.
participants (3)
-
Armin Rigo
-
Audrius Kažukauskas
-
Maciej Fijalkowski