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
319cfb5f
Commit
319cfb5f
authored
Jun 22, 2018
by
Victor Stinner
Committed by
GitHub
Jun 22, 2018
Browse files
Options
Browse Files
Download
Email Patches
Plain Diff
bpo-30345: Add -g to LDFLAGS for LTO (GH-7709) (GH-7825)
Add -g to LDFLAGS when compiling with LTO to get debug symbols.
parent
7b383a57
Changes
3
Hide whitespace changes
Inline
Side-by-side
Showing
3 changed files
with
15 additions
and
0 deletions
+15
-0
Misc/NEWS.d/next/Build/2018-06-15-18-18-16.bpo-30345.j-xRE1.rst
...EWS.d/next/Build/2018-06-15-18-18-16.bpo-30345.j-xRE1.rst
+1
-0
configure
configure
+7
-0
configure.ac
configure.ac
+7
-0
No files found.
Misc/NEWS.d/next/Build/2018-06-15-18-18-16.bpo-30345.j-xRE1.rst
0 → 100644
View file @
319cfb5f
Add -g to LDFLAGS when compiling with LTO to get debug symbols.
configure
View file @
319cfb5f
...
...
@@ -6481,6 +6481,13 @@ if test "$Py_LTO" = 'true' ; then
esac
;;
esac
if
test
"
$ac_cv_prog_cc_g
"
=
"yes"
then
# bpo-30345: Add -g to LDFLAGS when compiling with LTO
# to get debug symbols.
LTOFLAGS
=
"
$LTOFLAGS
-g"
fi
fi
...
...
configure.ac
View file @
319cfb5f
...
...
@@ -1455,6 +1455,13 @@ if test "$Py_LTO" = 'true' ; then
esac
;;
esac
if test "$ac_cv_prog_cc_g" = "yes"
then
# bpo-30345: Add -g to LDFLAGS when compiling with LTO
# to get debug symbols.
LTOFLAGS="$LTOFLAGS -g"
fi
fi
...
...
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