Re: [RFC] Crash sourcing Python script on Windows

Joel Brobecker
2011-09-29T04:07:05Z

> FILE is supposed to be an opaque type and as such noone except of
> the libc which defines it is supposed to "poke" at its internals.
> however it is common practice in GNU software to assume everybody
> uses GLIBC and poke around in internal stuff thats not supposed to
> be accessibly at all in userland.

It could be something simpler than that. Python was built on one
system, using an unknown build environment. when then use that
library to link it against some code on a version of Windows that
is most likely different, with a compiler that is also most likely
different. If each compiler used a libc where the definition of
that type is different, then we have an incompatibility.

--
Joel