[omniORB] Installing OmniOrb from a user account?

[Oliver Frick]

I have compiled OmniOrb 4.1.3 under a Mac user account and
configured a user writable directory for the installation.
OO configures and compiles fine, but when I say make install,
it stops here:
....
install: /Library/Python/2.5/site-packages/_omniidlmodule.so.4.1: Permission denied
+ cd /Library/Python/2.5/site-packages
+ rm -f _omniidlmodule.so.4
+ ln -s _omniidlmodule.so.4.1 _omniidlmodule.so.4
ln: _omniidlmodule.so.4: Permission denied
+ rm -f _omniidlmodule.so
+ ln -s _omniidlmodule.so.4 _omniidlmodule.so
ln: _omniidlmodule.so: Permission denied
make[4]: *** [install] Error 1
....

It tries to install _omniidlmodule.so in /Library/Python/... which is
a system directory.
Does OmniOrb always need admin permissions to install? How can
I configure a different Python site-packages directory or turn Python
support off globally?

Oliver

[Duncan Grisby]

Post by Oliver Frick
I have compiled OmniOrb 4.1.3 under a Mac user account and
configured a user writable directory for the installation.
OO configures and compiles fine, but when I say make install,
....
install: /Library/Python/2.5/site-packages/_omniidlmodule.so.4.1: Permission denied

How did you configure it? What options did you give to the configure
script? It should work fine if you give the --prefix option to
configure.

Cheers,

Duncan.

[Oliver Frick]

Post by Duncan Grisby

Post by Oliver Frick
I have compiled OmniOrb 4.1.3 under a Mac user account and
configured a user writable directory for the installation.
OO configures and compiles fine, but when I say make install,
....
install: /Library/Python/2.5/site-packages/_omniidlmodule.so.4.1: Permission denied

How did you configure it? What options did you give to the configure
script? It should work fine if you give the --prefix option to
configure.

Yes that's what I did:
./configure --prefix=<user-wriable-dir>
Now I have also set the $PYTHONHOME env variable to a user
writable directory before calling configure.
When I do that, configure sets
'${prefix}/lib/python2.5/site-packages' as the packages dir,
instead of
'/Library/Python/2.5/site-packages'.
But now make fails after compiling a few files:
[...]
g++ -c -O2 -fno-common -bind_at_load -DIDLMODULE_VERSION="\"0x2630\"" -I/Users/oliver/OhneBackup/Entwicklung/Installiert/Python/include -DPYTHON_INCLUDE="<python2.5/Python.h>" -fPIC -I. -I. -I../../../../include -I../../../../include -D__OSVERSION__=1 -D__darwin__ -D__powerpc__ -o idlpython.o idlpython.cc
+ rm -f _omniidlmodule.so.4.1
+ g++ -bundle -flat_namespace -undefined suppress -bind_at_load -o _omniidlmodule.so.4.1 -L../../../../lib -L../../../../lib y.tab.o lex.yy.o idlerr.o idlutil.o idltype.o idlrepoId.o idlscope.o idlexpr.o idlast.o idlvalidate.o idldump.o idlconfig.o idlfixed.o idlpython.o
+ /usr/bin/install -c -m 0644 _omniidlmodule.so.4.1 ../../../../lib
+ cd ../../../../lib
+ rm -f _omniidlmodule.so.4
+ ln -s _omniidlmodule.so.4.1 _omniidlmodule.so.4
+ rm -f _omniidlmodule.so
+ ln -s _omniidlmodule.so.4 _omniidlmodule.so
making export in src/tool/omniidl/python...
making export in src/tool/omniidl/python/omniidl...
+ ../../../../../bin/scripts/omkdirhier ../../../../../lib/python/omniidl
+ /usr/bin/install -c -m 0644 __init__.py ../../../../../lib/python/omniidl
+ /usr/bin/install -c -m 0644 main.py ../../../../../lib/python/omniidl
+ /usr/bin/install -c -m 0644 idlast.py ../../../../../lib/python/omniidl
+ /usr/bin/install -c -m 0644 idltype.py ../../../../../lib/python/omniidl
+ /usr/bin/install -c -m 0644 idlutil.py ../../../../../lib/python/omniidl
+ /usr/bin/install -c -m 0644 idlvisitor.py ../../../../../lib/python/omniidl
+ /usr/bin/install -c -m 0644 output.py ../../../../../lib/python/omniidl
'import site' failed; use -v for traceback
Traceback (most recent call last):
File "<string>", line 1, in <module>
ImportError: No module named compileall
make[5]: *** [export] Error 1
make[4]: *** [export] Error 1
make[3]: *** [export] Error 1
make[2]: *** [export] Error 1
make[1]: *** [export] Error 1
make: *** [all] Error 1

Oliver

[Duncan Grisby]

Post by Oliver Frick

Post by Duncan Grisby
How did you configure it? What options did you give to the configure
script? It should work fine if you give the --prefix option to
configure.

./configure --prefix=<user-wriable-dir>
Now I have also set the $PYTHONHOME env variable to a user
writable directory before calling configure.

You shouldn't have to do that, and I can imagine it would confuse
things.

Can you send me your config.log, created with configure when PYTHONHOME
is not set? It would be helpful if you could also send the output of
"env", so I can see any environment variables that may be affecting you.

Cheers,

Duncan.