[omniORB] ANNOUNCE: omniORB 4.1 testing

Al Slater al.slater at scluk.com
Thu Jan 27 11:51:18 GMT 2005


-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

Alex Tingle wrote:
| Well, Python has its own way of finding module files, depending upon how
| it was installed. Optional packages are usually supposed to go into a
| directory called 'site-packages' which is in /usr/lib/python2.3 on most
| Unix systems.
|
| If your omniORB4.0 install was packaged by your OS distributor, your old
| omniidl backends are probably in /usr/lib/python2.3/site-packages.
| (Assuming you're using Python 2.3.)
|
| By default omniORB installs itself into /usr/local, so your new backends
| will be in /usr/local/lib/python2.3/site-packages. Python won't look
| there by default, so you need to set
| PYTHONPATH=/usr/local/lib/python2.3/site-packages
|
| Obviously the details may be different on your system, but I hope you
| get the gist. ;-)
|

Thanks, setting PYTHONPATH explicitly fixes the problem.  Python was
using /usr/local/lib/python2.2/site-packages by default, and that
contained an errant omniidl package.

- --
Al Slater

Technical Director
Stanton Consultancy


-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.0 (MingW32)
Comment: Using GnuPG with Thunderbird - http://enigmail.mozdev.org

iD8DBQFB+NW2z4fTOFL/EDYRAn/kAJ97/UvborVu+YKvTYwfmpq0Wj7VpQCdGhOZ
vJujR2BqrLlihi6Gt1LkNwg=
=cjL9
-----END PGP SIGNATURE-----




More information about the omniORB-list mailing list