New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
./configure --with-pydebug on FreeBSD results in -O2 -pipe eventually ending up in CFLAGS. #59961
Comments
All the FreeBSD build slaves seem to be experiencing the same symptom: ./configure --with-pydebug eventually results in this:
What I find odd: % grep -e '-O2' Makefile | wc -l There are references to -O2 elsewhere, like in configure.ac|configure, but, the Makefile doesn't source any of those. (Right?) This is occurring on all of my slaves as well as others, so I'm pretty sure it's not just specific to my environment. |
Ah! % gmake % make % make So, the default BSD make likes to add in -O2 -pipe. I'll do a bit more digging. |
So, looks like FreeBSD's /usr/share/mk/sys.mk is to blame here. It unconditionally sets CFLAGS to [trent@hydrogen/ttypts/1(~s/cpython)%] uname -a [trent@hydrogen/ttypts/1(~s/cpython)%] grep -A3 'bsd_make_test' Makefile [trent@hydrogen/ttypts/1(~s/cpython)%] make bsd_make_test [trent@hydrogen/ttypts/1(~s/cpython)%] make CFLAGS= bsd_make_test I can think of a few ways to work around this... some better than others.
Some of the less desirable ones:
|
I've been debugging this once, too. My conclusion was that if the OS is set up All important features of --with-pydebug should also work if -O0 is overridden So I think that FreeBSD users who really want -O0 should change sys.mk |
Trent, do you want to keep this open? I think sys.mk is behaving exactly |
Note: these values reflect the state of the issue at the time it was migrated and might not reflect the current state.
Show more details
GitHub fields:
bugs.python.org fields:
The text was updated successfully, but these errors were encountered: