Hi, thank you for reporting the issue. I'm currently on holidays and unable to fix the issue before mid of June. If one of you can meanwhile create a patch I would be very happy. Thank you very much! Best regards, Peter Am 30.05.2014 14:33, schrieb Anthony G. Basile:
Hi Peter et al.
Can I ask you to look at Gentoo bug #511578. The url is
https://bugs.gentoo.org/show_bug.cgi?id=511578
While its easy enough to produce a patch here, it does depend on what upstream wants.
The issue in a nutshell can be seen by the following configure line (tested on 0.97.2).
# ./configure --disable-bundled-getopt | grep -C 3 forced checking for working memcmp... yes checking for strspn... yes checking for strstr... yes *** use of bundled getopt library forced checking openssl/md5.h usability... yes checking openssl/md5.h presence... yes checking for openssl/md5.h... yes
We ask to disable bundled-getopt and yet we get it. getopt is provided by glibc in this case and AC_CHECK_FUNC(getopt_long ...) does not fail. Rather, the logic wrt to how AC_ARG_ENABLE is used is incorrect. See
https://www.gnu.org/software/autoconf/manual/autoconf-2.67/html_node/Generic...
with particular attention to the [action-if-found]. The problem is repeated in several places.
In my opinion, and if I were to produce a patch, it would work as follows:
./configure --enable-bundled-getopt <- Don't bother checking if getopt_long is provided, just used the bundled version.
./configure --disable-bundled-getopt <- Check if getopt_long is provided via AC_CHECK_FUNC. If it is, use it. If it is not, fail with an error message. Under no circumstances should you used the bundled getopt.