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
15daa35d
Commit
15daa35d
authored
Dec 13, 2012
by
Trent Nelson
Browse files
Options
Browse Files
Download
Email Patches
Plain Diff
IRIX: force MIPSpro to treat #errors as errors, not warnings.
parent
64ab35e1
Changes
2
Hide whitespace changes
Inline
Side-by-side
Showing
2 changed files
with
66 additions
and
0 deletions
+66
-0
configure
configure
+33
-0
configure.ac
configure.ac
+33
-0
No files found.
configure
View file @
15daa35d
...
...
@@ -3238,6 +3238,39 @@ then
(it is also a good idea to do 'make clean' before compiling)"
"
$LINENO
"
5
fi
if
test
"
$MACHDEP
"
=
"irix6"
&&
test
"
$CC
"
!=
"gcc"
;
then
# Normally, MIPSpro CC treats #error directives as warnings, which means
# a successful exit code is returned (0). This is a problem because IRIX
# has a bunch of system headers with this guard at the top:
#
# #ifndef __c99
# #error This header file is to be used only for c99 mode compilations
# #else
#
# When autoconf tests for such a header, like stdint.h, this happens:
#
# configure:4619: cc -c conftest.c >&5
# cc-1035 cc: WARNING File = /usr/include/stdint.h, Line = 5
# #error directive: This header file is to be used only for c99 mode
# compilations
#
# #error This header file is to be used only for c99 mode compilations
# ^
#
# configure:4619: $? = 0
# configure:4619: result: yes
#
# Therefore, we use `-diag_error 1035` to have the compiler treat the
# warning as an error, which causes cc to return a non-zero result,
# which autoconf can interpret correctly.
CFLAGS
=
"
$CFLAGS
-diag_error 1035"
# Whilst we're here, we might as well make sure CXX defaults to something
# sensible if we're not using gcc.
if
test
-z
"
$CXX
"
;
then
CXX
=
"CC"
fi
fi
# If the user set CFLAGS, use this instead of the automatically
# determined setting
preset_cflags
=
"
$CFLAGS
"
...
...
configure.ac
View file @
15daa35d
...
...
@@ -507,6 +507,39 @@ then
(it is also a good idea to do 'make clean' before compiling)])
fi
if test "$MACHDEP" = "irix6" && test "$CC" != "gcc"; then
# Normally, MIPSpro CC treats #error directives as warnings, which means
# a successful exit code is returned (0). This is a problem because IRIX
# has a bunch of system headers with this guard at the top:
#
# #ifndef __c99
# #error This header file is to be used only for c99 mode compilations
# #else
#
# When autoconf tests for such a header, like stdint.h, this happens:
#
# configure:4619: cc -c conftest.c >&5
# cc-1035 cc: WARNING File = /usr/include/stdint.h, Line = 5
# #error directive: This header file is to be used only for c99 mode
# compilations
#
# #error This header file is to be used only for c99 mode compilations
# ^
#
# configure:4619: $? = 0
# configure:4619: result: yes
#
# Therefore, we use `-diag_error 1035` to have the compiler treat the
# warning as an error, which causes cc to return a non-zero result,
# which autoconf can interpret correctly.
CFLAGS="$CFLAGS -diag_error 1035"
# Whilst we're here, we might as well make sure CXX defaults to something
# sensible if we're not using gcc.
if test -z "$CXX"; then
CXX="CC"
fi
fi
# If the user set CFLAGS, use this instead of the automatically
# determined setting
preset_cflags="$CFLAGS"
...
...
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