Hello Martin,
> > You mean I should list all of these in "Modules/Setup"?
> Exactly so. They are already listed - just uncomment them all
> (with proper command line flags and libraries where necessary).
OK, I will try to get it compiled and tested.
Meanwhile, you asked so:
> I still don't unders
>> 2. Don't use extension modules. Edit Modules/Setup to statically link
>>all extension modules into the interpreter binary.
> This is the way. But how to do that?
>
> Shell output:
> ../configure --disable-shared
--disable-shared should be the default, so you don't need to specify
it explic
Hello Martin,
Thanks very much for answering.
> As for the static vs. shared libpython: On Unix, Python is typically
> built as a single executable (only linked shared with the system
> libraries). The challenge is then with extension modules, which are
> shared libraries. In particular, it is a c
> My first attempt to build failed due to the makefile insisted on linking as
> shared libraries (works only in x86 with GNU ld). Tried autoreconf to get
> rid of libtool - no luck.
> Q1: Is the static build broken?
> Q2: Anyone have a useable Makefile.am?
Are you sure you are talking about Python
Hello all,
I'm in need of an advise how to handle sizeof long in python. I wanted a
x86_64 compile of python for Interix (that is NT POSIX subsystem with x86_64
Interix 6 SDK).
My first attempt to build failed due to the makefile insisted on linking as
shared libraries (works only in x86 with GNU
