Skip to content
Projects
Groups
Snippets
Help
Loading...
Help
Support
Keyboard shortcuts
?
Submit feedback
Contribute to GitLab
Sign in / Register
Toggle navigation
C
cpython
Project overview
Project overview
Details
Activity
Releases
Repository
Repository
Files
Commits
Branches
Tags
Contributors
Graph
Compare
Issues
0
Issues
0
List
Boards
Labels
Milestones
Merge Requests
0
Merge Requests
0
Analytics
Analytics
Repository
Value Stream
Wiki
Wiki
Members
Members
Collapse sidebar
Close sidebar
Activity
Graph
Create a new issue
Commits
Issue Boards
Open sidebar
Kirill Smelkov
cpython
Commits
f0d5f791
Commit
f0d5f791
authored
Aug 15, 2004
by
Skip Montanaro
Browse files
Options
Browse Files
Download
Email Patches
Plain Diff
Match the def'n of _XOPEN_SOURCE on Solaris 8/9 to suppress redefinition
warning from GCC. Closes patch #1006629.
parent
8d3b9dd0
Changes
2
Expand all
Hide whitespace changes
Inline
Side-by-side
Showing
2 changed files
with
3100 additions
and
1287 deletions
+3100
-1287
configure
configure
+3088
-1285
configure.in
configure.in
+12
-2
No files found.
configure
View file @
f0d5f791
This diff is collapsed.
Click to expand it.
configure.in
View file @
f0d5f791
...
...
@@ -170,8 +170,18 @@ esac
if test $define_xopen_source = yes
then
AC_DEFINE(_XOPEN_SOURCE, 600,
Define to the level of X/Open that your system supports)
# On Solaris w/ g++ it appears that _XOPEN_SOURCE has to be
# defined precisely as g++ defines it
case $ac_sys_system/$ac_sys_release in
SunOS/5.8|SunOS/5.9)
AC_DEFINE(_XOPEN_SOURCE, 500,
Define to the level of X/Open that your system supports)
;;
*)
AC_DEFINE(_XOPEN_SOURCE, 600,
Define to the level of X/Open that your system supports)
;;
esac
# On Tru64 Unix 4.0F, defining _XOPEN_SOURCE also requires
# definition of _XOPEN_SOURCE_EXTENDED and _POSIX_C_SOURCE, or else
...
...
Write
Preview
Markdown
is supported
0%
Try again
or
attach a new file
Attach a file
Cancel
You are about to add
0
people
to the discussion. Proceed with caution.
Finish editing this message first!
Cancel
Please
register
or
sign in
to comment