summaryrefslogtreecommitdiff
path: root/dev-python/python-fastimport
diff options
context:
space:
mode:
authorMichael Orlitzky <mjo@gentoo.org>2017-06-18 09:43:45 -0400
committerMichael Orlitzky <mjo@gentoo.org>2017-08-11 11:25:25 -0400
commit8f36aaf184fd8aeb5387d51f22246179b6dd349c (patch)
tree257ce608956f2f78ed9955045fdf040e465db0ac /dev-python/python-fastimport
parentefb447520ee5333ab19edaf277c77f6adec07a76 (diff)
downloadgentoo-8f36aaf184fd8aeb5387d51f22246179b6dd349c.tar.gz
gentoo-8f36aaf184fd8aeb5387d51f22246179b6dd349c.tar.bz2
gentoo-8f36aaf184fd8aeb5387d51f22246179b6dd349c.zip
apache-2.eclass: don't enable maintainer-mode with USE=debug.
The --enable-maintainer-mode flag serves two purposes: first, it enables compile-time warnings; and second, it forces all compiled modules to be loaded at runtime. To achieve the first goal, the build system checks for the "-std=c89" compiler flag and appends it to CFLAGS if found. This can cause a problem later, because the CFLAGS used to build apache are used by apxs to build extension modules. In particular, if you have an extension that relies on C99 or some later standard, and if apache was built with --enable-maintainer-mode, then apxs will attempt to build that extension according to C89 and fail. This failure can be observed in in bugs 621686, 621756, and 621794 when apache is built with USE=debug, because USE=debug sets the --enable-maintainer-mode flag. Since there is not much reason for an end user to enable maintainer- mode, the simplest fix for this is the wholesale removal of the --enable-maintainer-mode flag from USE=debug. This prevents us from having to append CFLAGS to each extension package that uses a later standard, or from having to add a USE dependency forbidding USE=debug in apache (which would create conflicts with e.g. mod_backtrace). Gentoo-Bug: 621686 Gentoo-Bug: 621756 Gentoo-Bug: 621794
Diffstat (limited to 'dev-python/python-fastimport')
0 files changed, 0 insertions, 0 deletions