Summary: | dev-libs/libmemcached-1.0.18 - configure misinterprets --disable-debug | ||
---|---|---|---|
Product: | Gentoo Linux | Reporter: | Dmitry Faleychik <fadimko> |
Component: | [OLD] Library | Assignee: | Robin Johnson <robbat2> |
Status: | RESOLVED FIXED | ||
Severity: | normal | CC: | mattsch, prometheanfire |
Priority: | Normal | ||
Version: | unspecified | ||
Hardware: | All | ||
OS: | Linux | ||
URL: | https://bugs.launchpad.net/libmemcached/+bug/1400560 | ||
Whiteboard: | |||
Package list: | Runtime testing required: | --- | |
Attachments: | libmemcached-1.0.18-fix_debug_flag.patch |
Description
Dmitry Faleychik
2014-06-24 18:41:44 UTC
That's a well-known problem with AC_ARG_ENABLE. It's nothing the ebuild is to blame for (but could work around). (In reply to Jeroen Roovers from comment #1) > That's a well-known problem with AC_ARG_ENABLE. It's nothing the ebuild is > to blame for (but could work around). The big problem is, that when I compile libmemcached and include it to my project, I get TONS of debug logs in my php-fpm.log, which are turned on (as I investigated) at compile time and can't be turned on/off otherwise. These logs make php-fpm unreadable and waste much space on disk. So, I believe, in this case it is a serious bug. I think it's the same with the other use flags, so libmemcached everytime compiles with all options enabled without letting a user to know about it. >make php-fpm unreadable
make php-fpm.log
Created attachment 389794 [details, diff]
libmemcached-1.0.18-fix_debug_flag.patch
This patch will make configure obey the debug flag. Since I don't feel like navigating upstream's repo (why don't they use github??), someone else can push my patch upstream.
fixed in 1.0.18-r1 and reported upstream |