If you only care about this running on a single machine to get some coverage and don't care about all architectures, you can change Misc/build.sh to add the configure option.
n On Mon, Jan 26, 2009 at 2:31 PM, Antoine Pitrou <solip...@pitrou.net> wrote: > Martin v. Löwis <martin <at> v.loewis.de> writes: >> >> Me. Does it have to be a configure option? It is difficult to invoke >> different commands in different branches; better if the configures in >> all branches get the same options. > > Well, after a quick test, it seems that configure doesn't complain if you pass > it an unknown option (at least one that begins with '--with'). So we can still > use the same options on all branches. > > (as for the need for it to be a configure option, it was the consensus which > emerged after discussion in the tracker entry, both to provide some > flexibility > and for fear that enabling it by default could trigger some compiler bugs -- > although the latter is of course unlikely) > > Regards > > Antoine. > > > _______________________________________________ > Python-Dev mailing list > Python-Dev@python.org > http://mail.python.org/mailman/listinfo/python-dev > Unsubscribe: > http://mail.python.org/mailman/options/python-dev/nnorwitz%40gmail.com > _______________________________________________ Python-Dev mailing list Python-Dev@python.org http://mail.python.org/mailman/listinfo/python-dev Unsubscribe: http://mail.python.org/mailman/options/python-dev/archive%40mail-archive.com
