http://bugzilla.novell.com/show_bug.cgi?id=578655 http://bugzilla.novell.com/show_bug.cgi?id=578655#c0 Summary: Race condition on AutoFS build (lookup_ldap.so not linked against krb5) Classification: openSUSE Product: openSUSE 11.3 Version: Factory Platform: All OS/Version: openSUSE 11.3 Status: ASSIGNED Severity: Normal Priority: P5 - None Component: Other AssignedTo: lchiquitto@novell.com ReportedBy: lchiquitto@novell.com QAContact: qa@suse.de CC: mszeredi@novell.com Found By: --- Blocker: --- There's an interesting problem when building the autofs package. Sometimes it will create a binary that fails to start, reporting the following error: Jan 19 16:14:49 eagnmnmbd000 automount[8731]: open_lookup:95: cannot open lookup module ldap (/usr/lib64/autofs/lookup_ldap.so: undefined symbol: krb5_cc_get_principal) We can see that lookup_ldap.so is not being linked against krb5, even with the patch we currently have in our package to enforce it (autofs-5.0.4-link_kerberos.patch). I reported the problem to the Autobuild Team and here's the explanation: """ Basically this is a race condition. The "-f" for autoconf does in _no way_ guarantee configure to be overwritten (it has a completely different meaning). Since the timestamps for configure.in and configure are sufficiently close it can happen that "autoconf -f" will _not_ update configure. I've tried it several times in a row with these sources and the chance is about once in three attempts when building on reiserfs (not sure about other filesystems, but the window is there as well) that the configure script will not be updated. Since it is just a patch to configure.in that adds "-lkrb5", if configure is not being updated, the old script runs and you'll get a binary not linked against kerberos. The only way to make sure this succeeds is adding "rm -f configure" before the autoconf call. """ -- Configure bugmail: http://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.