On Mon, Mar 26, 2012 at 7:47 PM, Laurent Bigonville <bigon@xxxxxxxxxx> wrote:
> Hi,
>
> Do not link python module with libpython, the interpreter is already linked against it.
ah, that reminds me: does the python debian build infrastructure cope
with 2.6, 2.7 etc. etc. producing multiple versions of this c-based
module? if not i know of a way to do that, but it uses an earlier
version of the debian helper tools, and also needs automake not just
autoconf.
for another project i had to write an m4 automake macro which used
python2.{insertversion}-config to record the various includes and
library versions etc.
let me know if this is of any use?
l.
--
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.
