This issue tracker has been migrated to GitHub, and is currently read-only.
For more information, see the GitHub FAQs in the Python's Developer Guide.

Author goertzen
Recipients
Date 2006-07-04.16:48:45
SpamBayes Score
Marked as misclassified
Message-id
In-reply-to
Content
Logged In: YES 
user_id=843814

This stuff is becoming hazy for me, but I'll try to offer
some ideas:

- Does it help if you put your build directory outside of
the source directory?

- Why is the system looking for struct.so when you told it
to be static?  I suspect static support is broken for a lot
of modules.  Does it go better when you take the static
switch out?  Assuming you have a few other apps in your
system besides python (a shell, busybox maybe), I question
wether static would actually save any memory.  It perhaps is
a little more complex to get all the libraries in their
correct location, but I'll bet coaxing a python system to be
static is way harder.

- It is normal for some things to bomb out while compiling
because the python build scripts always check the build
system for library availability.  In many cases you don't
need those broken libraries.  It is also often possible to
hack up the install scripts to work properly for a cross
compiled system.  That said, simple things like struct
should be working properly without hackery.

Cheers,
Dan.
History
Date User Action Args
2007-08-23 15:39:18adminlinkissue1006238 messages
2007-08-23 15:39:18admincreate