Message18814
Logged In: YES
user_id=876734
I'm running into issues trying to come up with a clean version
of this. I'd like to know what you think of some of these
before I try to port what I've got into 2.4 and come up with
patches.
1) setup.py seems to have no way to be selective about
which modules to build. What if I don't want to try (and then
fail make install) to build, for example, ssl?
2) setup.py makes assumptions about pathnames. It always
puts /usr/local/lib into the build path. On a 64-bit solaris or HP
system, this can lead to a mess, if the 64 bit libraries are
somewhere else.
3) There is an existing provision to add additional libs to the
build in setup.py, but it's disabled if the prefix is /usr. Why?
I have this feeling that someone had a plan here that I'm too
obtuse to make out which would offer a shorter path to a
solution then I'm getting tangled up in, for managing the build
of these modules.
|
|
| Date |
User |
Action |
Args |
| 2007-08-23 14:17:56 | admin | link | issue832799 messages |
| 2007-08-23 14:17:56 | admin | create | |
|