Le dimanche 30 janvier 2005 � 21:59 +0100, Joerg Budischewski a �crit : ... (Part deleted) ...
> > Debian itself might choose to provide binary rpms to ship both a python > and OpenOffice.org, that play well together. > > Or you choose to build both python and OOo by from source. > > Or you use the python coming with ooo. > > But in general you can't make a binary debian python package run with a > binary OpenOffice downloaded from somewhere else. Even if you can work > around the the above issue as described, it may not work, because python > and OOo were built with incompatible compiler versions (currently, this > does not seem to be the case but may and will occur in not so distant > future). What I don't understand is that I compiled the python-uno bridge and the needed dependent modules on my Debian system. This means they are indeed compiled with the same gcc version than the Debian supplied OpenOffice.org and python2.3 and of course the pyuno bridge is supposed to be used with them. The stock pyuno does not work however in that case on my system when I follow the instructions given in the python-uno bridge faq to compile the bridge except if I do the previously cited modifications. > > There is no way to workaround this until there is a binary compatible > python (and even before a binary compatible g++). And this seems notto > be going to happen ... > > Bye, > > Joerg > > > --------------------------------------------------------------------- > To unsubscribe, e-mail: [EMAIL PROTECTED] > For additional commands, e-mail: [EMAIL PROTECTED] -- Pierre Martineau mail: [EMAIL PROTECTED] Bibus home: http://bibus-biblio.sourceforge.net/ --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
