Ah, I see. Again, thanks for the clarifications! Yes, I was indeed using
PyPy instead of CPython, it looks to me that the logic that pipes the
printed values into the rpython toolchain is broken, since in my MinGW /tmp
directory I can see that the executables were built without issues and
running t
On 19/6/23 10:45, Julian Waters wrote:
I'm working with the MinGW team; I can create a patch to help, but a
quick low down on how the build_executable_cache and related logic
works would help me out a little
Also: Is MinGW not used by the core team?
best**regards,
Julian
Thanks for giving P
I'm working with the MinGW team; I can create a patch to help, but a quick
low down on how the build_executable_cache and related logic works would
help me out a little
Also: Is MinGW not used by the core team?
best regards,
Julian
___
pypy-dev mailing
On 19/6/23 10:08, Julian Waters wrote:
When I try to build PyPy with MinGW, I get the following:
...
It seems as if the ask_gcc function is broken for MinGW, and I can't
tell why at a first glance. Is a fix possible?
Someone who uses mingw would have to suggest a patch.
Matti
__
When I try to build PyPy with MinGW, I get the following:
[translation:info] Translating target as defined by targetpypystandalone
Traceback (most recent call last):
File "../../rpython/bin/rpython", line 20, in
main()
File
"D:\eclipse-php-2022-06-R-win32-x86_64\Projects\pypy-release-pypy
