[omniORB] Minor build problem with omniORBpy

Julian Satchell j.satchell@eris.qinetiq.com
Wed Sep 18 10:01:01 2002


I tried to build omniORBpy to use a different python installation to the
system default one, by including the definition
PYTHON=/my/wacky/bin/python on the configure line. Configure ran without
complaint, and said plausible things.

Make worked fine, but make install wanted to put everything in
$prefix/lib/pythonX.Y/site-packages, where X.Y  matched the default
system python.  I wanted things to go into
/my/wacky/lib/pythonN.M/site-packages, where the non-standard python
(version N.M) expects to find modules.  A little bit of hand editing of
mk/beforeauto.mk fixed all this, but I thought I should report it, as a
corner case that the current build system does not handle perfectly;
different settings where needed omniidl and the rest of the system, as I
chose to use the system python for omniidl. 

If you don't want fix it before the main release, maybe you should add a
sentence to the README, warning that this case may need some hand
intervention.

Why would anybody want to do something so odd? I did it to fit in with
an existing Zope installation, which has its own python interpreter.

Julian Satchell