Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]
Groups > linux.debian.maint.python > #11429
| From | Ansgar <ansgar@debian.org> |
|---|---|
| Newsgroups | linux.debian.maint.python |
| Subject | Re: overriding default compile flags when building python extensions |
| Date | 2019-05-03 14:10 +0200 |
| Message-ID | <xTFaN-6JL-1@gated-at.bofh.it> (permalink) |
| References | <xTERr-6ns-3@gated-at.bofh.it> |
| Organization | linux.* mail to news gateway |
On Fri, 2019-05-03 at 19:49 +0800, Drew Parsons wrote: > The first -g is the problem (in "-DNDEBUG -g -fwrapv -O2 -Wall"). The > advice from the internet (stackoverflow) is exceedingly poor on this > question, in most cases addressing how to add flags, not how to change > the existing default flags. Alternatives like > OPT="" python3 ./setup.py > simply do not work. Not sure about setup.py, but `-g0` (after `-g`) should also disable debug information: +--- | Level 0 produces no debug information at all. Thus, -g0 negates -g. +--- Ansgar
Back to linux.debian.maint.python | Previous | Next — Previous in thread | Next in thread | Find similar | Unroll thread
overriding default compile flags when building python extensions Drew Parsons <dparsons@debian.org> - 2019-05-03 13:50 +0200 Re: overriding default compile flags when building python extensions Ansgar <ansgar@debian.org> - 2019-05-03 14:10 +0200 Re: overriding default compile flags when building python extensions Drew Parsons <dparsons@debian.org> - 2019-05-03 16:40 +0200
csiph-web