Change by Gagan :
--
resolution: not a bug -> rejected
___
Python tracker
<https://bugs.python.org/issue35583>
___
___
Python-bugs-list mailing list
Unsubscrib
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 libgnui
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
<https://bugs.python.org/issue35
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-fel
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
<https://bugs.pyth
New submission from Gagan :
Hello everyone.
I am currently trying to compile Python 3.7.x on a MIPS(el, little endian; 32
bit) platform, and I am having issues producing a functioning interpreter to
continue the compilation.
I have no issue compiling either 2.7.x or 3.6.x versions on this
