Hello
I am trying (for 3 days and still failing ) to identify why
pam_msyql (
https://bugzilla.redhat.com/show_bug.cgi?id=374611 ) will
not build succesfully on EL-4/x86_64. Everything else (Centos 4/i386,
Centos 5 i386+x86_64 and Fedora >=7) works OK.
I have uploaded at
http://wdl.lug.ro/linux/rpms/pam_msyql the build
logs left after attempting mock builds with Centos4 as targets
(successful build for i386, failed build for x86_64) . The error seems
to point to a problem in cyrus-sasl-devel, resp md5.h but I kind of
think that the real problem is somewhere earlier in the chain. I am not
sure if this is the reason of the failure, but looking at the logs I
have noticed that - on this architecture only - after the %configure
stage I get (quote from config.h)
/* Define to 1 if OpenSSL library is installed */
/* #undef HAVE_OPENSSL */
while the other builds lead to:
/* Define to 1 if OpenSSL library is installed */
/* #undef HAVE_OPENSSL */
This happens independent of the presence of openssl-devel in the mock chroot
To add spice to the problem
- both the functional and non functional builds exhibit the same warning
about md5.h, i.e.
checking md5.h presence... yes
configure: WARNING: md5.h: present but cannot be compiled
configure: WARNING: md5.h: check for missing prerequisite headers?
configure: WARNING: md5.h: see the Autoconf documentation
configure: WARNING: md5.h: section "Present But Cannot Be Compiled"
configure: WARNING: md5.h: proceeding with the preprocessor's result
configure: WARNING: md5.h: in the future, the compiler will take precedence
- someone did a successful build on a x86_64 machine (not in mock but in
a rather "fat chroot"). I have tried to identify if one of the packages
he has but mock does not pull would provide something "useful" but I did
not spot anything obvious. I have uploaded the output of "rpm -qa" on
his machine to
http://wdl.lug.ro/linux/rpms/pam_msyql as well.
Any help would be appreciated, I am going nuts ...
Manuel