Message13119
| Author |
jribbens |
| Recipients |
| Date |
2002年11月09日.20:02:56 |
| SpamBayes Score |
| Marked as misclassified |
| Message-id |
| In-reply-to |
| Content |
Logged In: YES
user_id=76089
It would be a great deal of effort to make separate bug reports
(I would have to individually test every Python feature by
hand), and it wouldn't gain anything.
The problem is that OpenBSD is buggy, has been since
version 2.0 and still is in the very latest CVS. For example, if
you define _XOPEN_SOURCE (its value doesn't make any
difference, just if it is defined) then there is absolutely no way
to get the select(), fd_set, etc, they are simply not available
in any header file. You can't use select() in a C program that
#defines _XOPEN_SOURCE.
I don't see why you say there is "no way" to withdraw the
definition of _XOPEN_SOURCE - instead of making the
addition of _XOPEN_SOURCE to the header file
unconditional, simply detect OpenBSD in ./configure and
don't define it in that case. Why is that difficult?
Why is _XOPEN_SOURCE being defined anyway? Because
it breaks everything so badly on OpenBSD, and nobody has
noticed this before, I am suspecting that almost no programs
out there except Python define it. This makes it likely to
break things on many different platforms. |
|
History
|
|---|
| Date |
User |
Action |
Args |
| 2007年08月23日 14:07:59 | admin | link | issue635034 messages |
| 2007年08月23日 14:07:59 | admin | create |
|