Message 13125 - Python tracker

➜

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.

Recipients
Author	jribbens
Date	2002年11月11日.02:16:01
SpamBayes Score
Marked as misclassified
Message-id
In-reply-to

Content
Logged In: YES user_id=76089 The patch nearly works. The line "if test $define_xopen_source=yes" you have added to configure should read "if test $define_xopen_source = yes" (i.e. with spaces around the equals sign). With the patch, amended, it fixes the problem. Please though could you change it to 'OpenBSD/' instead of 'OpenBSD/2.' and 'OpenBSD/3.[012]'? I think it is much more likely to cause problems in the future that _XOPEN_SOURCE is defined in the as-yet- hypothetical OpenBSD/3.3 than if it were not defined since I don't suspect that OpenBSD will suddenly start requiring people to define this value that would break compatibility with all older OpenBSDs ;-) Many thanks.

Content

Logged In: YES 
user_id=76089
The patch nearly works. The line "if test 
$define_xopen_source=yes" you have added to configure 
should read "if test $define_xopen_source = yes" (i.e. with 
spaces around the equals sign).
With the patch, amended, it fixes the problem. Please though 
could you change it to 'OpenBSD/*' instead of 'OpenBSD/2.*' 
and 'OpenBSD/3.[012]'?
I think it is much more likely to cause problems in the future 
that _XOPEN_SOURCE *is* defined in the as-yet-
hypothetical OpenBSD/3.3 than if it were not defined since I 
don't suspect that OpenBSD will suddenly start requiring 
people to define this value that would break compatibility with 
all older OpenBSDs ;-)
Many thanks.

History
Date	User	Action	Args
2007年08月23日 14:08:00	admin	link	issue635034 messages
2007年08月23日 14:08:00	admin	create

homepage