| FazBrowse GitHub Viewer | Trending | | Home |
| Tools: [Download Repo ZIP] [Original HTTPS Page] |
Sorry, something went wrong.
|
|
||
| #ifdef _AIX | ||
| /* issue #18259, not declared in any useful header file */ | ||
| #if defined(_AIX) || (defined(__sun) && defined(__SVR4) && SUNOS_VERSION == 510) |
There was a problem hiding this comment.
wow, that's very spefic. It was available before and after, but not at version 510? :-)
Sorry, something went wrong.
| # in most compilers, so we define one here. | ||
| SUNOS_VERSION=`echo $ac_sys_release | tr -d '.'` | ||
| AC_DEFINE_UNQUOTED([SUNOS_VERSION], [$SUNOS_VERSION], | ||
| [The version of SunOS/Solaris as reported by `uname -r' without the dot.]) |
There was a problem hiding this comment.
How do you distinguish Solaris 5.10 and Solaris 51.0?
Maybe multiply the major version by 100 or 1000? or use a shift of 8 bits? The usage would be:
major = VERSION >> 8 minor = VERSION & 255
The disavantage is the need to write versions in hexadecimal :-(
Sorry, something went wrong.
There was a problem hiding this comment.
@erlend-aasland: Should we prefix new pyconfig.h constants by Py_ ? see: capi-workgroup/problems#46
Sorry, something went wrong.
There was a problem hiding this comment.
I think we should follow the PEP-7 recommendations: https://peps.python.org/pep-0007/#naming-conventions
Sorry, something went wrong.
There was a problem hiding this comment.
How do you distinguish Solaris 5.10 and Solaris 51.0?
I see what you mean, but that's not happening. The leading 5 was dropped from the name 25 years ago and while e.g. uname and compilation targets still use it, nobody today calls it Solaris/SunOS 5.10; only Solaris 10. If we ever release Solaris 51, uname -r should report it as 5.51.
That said, I am not strongly against changing it if you still prefer your suggestion.
I think we should follow the PEP-7 recommendations: https://peps.python.org/pep-0007/#naming-conventions
Thanks, I missed that. It's fixed now.
Sorry, something went wrong.
|
When was Solaris 10 release? Is it still supported? Does this change better to forks of Solaris? |
Sorry, something went wrong.
Sorry for such a long delay. As mentioned in the issue, Solaris 10, while in the "extended support stage" intended mostly for critical fixes, is still supported (ATM at least until January 2025). There are still people using it and possibly installing newer Python onto it. As for the Solaris forks, this doesn't affect those because the first open version was Solaris 11. |
Sorry, something went wrong.
Co-authored-by: Victor Stinner <vstinner@python.org>
|
Is this a bug-fix? If so, we should backport it and add a NEWS entry. |
Sorry, something went wrong.
Do you use "make regen-configure"? See: https://docs.python.org/dev/using/configure.html#generated-files @kulikjak: Anyway, I push directly into your branch to fix the configure script (regenerate it). |
Sorry, something went wrong.
There was a problem hiding this comment.
LGTM.
Sorry, something went wrong.
|
@kulikjak: I also replaced Py_SUNOS_VERSION == 510 with Py_SUNOS_VERSION <= 510. |
Sorry, something went wrong.
Sigh, sorry. Normally, I do, but this time I thought that I could quickly edit it myself, ... and I was wrong. Thanks for fixing it.
I guess it is (fixing a build on Solaris <= 10). I can add a NEWS entry, although now there is a skip-news tag, so I am not sure whether I should do so? Other than that, the build failure doesn't seem to be related, so that's good. |
Sorry, something went wrong.
|
GH-110580 is a backport of this pull request to the 3.12 branch. |
Sorry, something went wrong.
|
GH-110581 is a backport of this pull request to the 3.11 branch. |
Sorry, something went wrong.
⚠️⚠️⚠️ Buildbot failure ⚠️⚠️⚠️Hi! The buildbot s390x SLES 3.x has failed when building commit 3b1580a. What do you need to do:
You can take a look at the buildbot page here: https://buildbot.python.org/all/#builders/540/builds/6801 Failed tests:
Failed subtests:
Summary of the results of the build (if available): == Click to see traceback logsTraceback (most recent call last):
File "/home/dje/cpython-buildarea/3.x.edelsohn-sles-z/build/Lib/test/test_signal.py", line 1374, in test_stress_modifying_handlers
self.assertGreater(num_received_signals, 0)
AssertionError: 0 not greater than 0
|
Sorry, something went wrong.
…9447) Add OS version specific macro for Solaris: Py_SUNOS_VERSION.
| Back | FazBrowse Home | New Git URL |
As discussed in the issue, sethostname is missing from Solaris 10 headers but is available on Solaris 11.
And because there isn't an OS version specific macro for Solaris, I had to "create" one.