This issue tracker has been migrated to GitHub, and is currently read-only.
For more information, see the GitHub FAQs in the Python's Developer Guide.

Author ddvento@ucar.edu
Recipients ddvento@ucar.edu, pitrou
Date 2013-01-31.18:52:54
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <510ABD8F.5070101@ucar.edu>
In-reply-to <1359656934.32.0.813938210487.issue17092@psf.upfronthosting.co.za>
Content
Antoine, the exact reason why I want to disable TIPC in configure, is 
that either the test suite or the TIPC test case or both has/have a bug 
(not my system). Therefore I suggest that you re-post your comment in 
Issue17085, and I'll be happy to provide more details that would be 
off-topic here.

However, regardless of my particular needs, disabling TIPC in configure 
is something useful for a variety of other reasons (e.g. one having a 
functional TIPC but not wanting to have it enabled in python), and 
therefore I asked it here.
It is customary to have autotools being able to individually select 
packages that one wants or does not want to use. In fact ./configure 
--help reports the --without-PACKAGE option which does not work for TIPC 
and this is the bug of present Issue17092
History
Date User Action Args
2013-01-31 18:52:54ddvento@ucar.edusetrecipients: + ddvento@ucar.edu, pitrou
2013-01-31 18:52:54ddvento@ucar.edulinkissue17092 messages
2013-01-31 18:52:54ddvento@ucar.educreate