[issue35583] (glibc2.28/MIPS32EL) python 3.7.x interpreter segmentation fault (3.6.x/2.7.x compile fine)

Change by Gagan : -- resolution: not a bug -> rejected ___ Python tracker ___ ___ Python-bugs-list mailing list Unsubscribe: https:

[issue35583] (glibc2.28/MIPS32EL) python 3.7.x interpreter segmentation fault (3.6.x/2.7.x compile fine)

Gagan added the comment: hello everyone. the core problem was that the 3.x series configure file includes a "-lintl" flag when it discovers the libintl header. in 2.x, this was not the case. so when configure is checking for wchar_t, the inclusion of -lintl (as opposed to libgnuintl, which

[issue35583] (glibc2.28/MIPS32EL) python 3.7.x interpreter segmentation fault (3.6.x/2.7.x compile fine)

Gagan added the comment: of course you have more time to get sanctimonious than provide a substantive or insight comment as to what the problem is. i am not surprised, at all. -- ___ Python tracker ___

[issue35583] (glibc2.28/MIPS32EL) python 3.7.x interpreter segmentation fault (3.6.x/2.7.x compile fine)

Mariatta Wijaya added the comment: Your disrespectful comments and insults are not welcome here. -- nosy: +Mariatta ___ Python tracker ___

[issue35583] (glibc2.28/MIPS32EL) python 3.7.x interpreter segmentation fault (3.6.x/2.7.x compile fine)

Gagan added the comment: i tried compiling using "--without-pymalloc" and experienced the same problem. there is no REASONABLE explanation for how this anomaly has arisen within SUBVERSIONS. in the words of some infamous rappers: "what, the 'embedded' (ARM-fellating) [east coast] crew doesn

[issue35583] (glibc2.28/MIPS32EL) python 3.7.x interpreter segmentation fault (3.6.x/2.7.x compile fine)

Change by Gagan : -- title: python 3.7.x interpreter segmentation fault (3.6.x/2.7.x compile fine) -> (glibc2.28/MIPS32EL) python 3.7.x interpreter segmentation fault (3.6.x/2.7.x compile fine) ___ Python tracker