And hence you are stuck between a rock and a hard-place.... either hack-up a Frankenstein toolchain or somehow revert future-proof correct upstream code, for sake of older buggy gcc.
I wonder if greenlet could somehow detect buggy compiler and still build with it... 😂
I think I get it all now.....
https:/ /github. com/python- greenlet/ greenlet/ commit/ 9c8a65fddcffe16 1f38679a0b3289d e9b25e2bc6. patch -> unbreaks with new gcc-7, but broken again with old gcc-5 again
And hence you are stuck between a rock and a hard-place.... either hack-up a Frankenstein toolchain or somehow revert future-proof correct upstream code, for sake of older buggy gcc.
I wonder if greenlet could somehow detect buggy compiler and still build with it... 😂