Groups > linux.debian.maint.python > #11431

Re: overriding default compile flags when building python extensions

From	Drew Parsons <dparsons@debian.org>
Newsgroups	linux.debian.maint.python, linux.debian.bugs.dist
Subject	Re: overriding default compile flags when building python extensions
Date	2019-05-03 16:40 +0200
Message-ID	<xTHvX-82q-3@gated-at.bofh.it> (permalink)
References	<xTERr-6ns-3@gated-at.bofh.it>
Organization	The Debian Project

Cross-posted to 2 groups.

Show all headers | View raw

Ansgar wrote:
> On Fri, 2019-05-03 at 19:49 +0800, Drew Parsons wrote:
> > The first -g is the problem (in "-DNDEBUG -g -fwrapv -O2 -Wall").
> 
> 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.
> +---

Thanks Ansgar. Weird (dangerous, even) if the flags can't be controlled 
directly.
But I can try the -g0 trick and see if it solves the problem.

Drew

Back to linux.debian.maint.python | Previous | Next — Previous in thread | Find similar | Unroll thread

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