Vikram Noel Ambrose wrote: > Joshua Brindle wrote: >> Vikram Noel Ambrose wrote: >> >>> Here's the fix to that libselinux ld error you were getting. >>> >>> >> >> Ok, applied and built fine. One interesting thing is that even without >> building the swig wrappers (--disable-swig) it still installs >> lib/python2.5/site-packages/selinux, which obviously wouldn't work >> without the accompanying .so file. >> >> > > I'll have a look at that, thanks. > >> Also, it looks like any library that installs to /lib will also put >> their python stuff in /lib/python2.5. I don't know if python even >> knows to look there, and even if it does there is really no reason to >> put them there. libselinux.so and libsepol.so will need to go to /lib >> but the python stuff should go to /usr/lib and I don't see a different >> argument for the python stuff (only --libdir). >> >> >> > Here you are referring to libpy*.so? if so then, Yes, python does know > to look for it in its site-packages/$pkg/ folder. > I know that, I mean no python .so files or .py files are put in /lib/python2.5, they are all put in /usr/lib/python2.5. However, since libselinux.so and libsepol.so (the real libs) have to be in /lib/ there is no way to tell configure to split those up (since they both use libdir) > > And in regards to the AUTHORS file, it obviously would be in source > control and as the persons in question patch the tree, they could > obviously patch the file with their names as well, its not set in stone > or anything. > > > Vikram > > -- This message was distributed to subscribers of the selinux mailing list. If you no longer wish to subscribe, send mail to majordomo@xxxxxxxxxxxxx with the words "unsubscribe selinux" without quotes as the message.
