On Tue, Apr 25, 2006 at 09:46:41AM +0200, Guido Guenther wrote: > Hi Kurt, > On Mon, Apr 24, 2006 at 09:33:19PM +0200, Kurt Roeckx wrote: > > Package: libpam-ccreds > > Version: 3-1 > > Severity: serious > > > > Hi, > > > > Your package is failing to build with the following error: > > checking openssl/opensslconf.h usability... no > > checking openssl/opensslconf.h presence... no > > checking for openssl/opensslconf.h... no > > configure: error: could not locate <openssl/opensslconf.h> > > make: *** [config.status] Error 1 > It built on all arches except for amd64 because debian/rules didn't > execute the autoreconf. I don't understand this since the Makefile part > is quiet simple: > > configure: patch-stamp > autoreconf
One that works shows: dpatch cat-all >>patch-stampT mv -f patch-stampT patch-stamp autoreconf [...] dh_testdir One that doesn't work shows: dpatch cat-all >>patch-stampT mv -f patch-stampT patch-stamp dh_testdir So, it all depends on the time between when configure was created, and when the patch-stamp was created. If you can extract the sources, and get to apply the patches within the same second, you have a problem. apt-get source libpam-ccreds; cd libpam-ccreds-1; dpkg-buildpackage -B -rfakeroot [...] ls -l --full-time configure patch-stamp -rwxr-xr-x 1 kurt kurt 182470 2006-04-25 18:44:49.000000000 +0200 configure -rw-r--r-- 1 kurt kurt 734 2006-04-25 18:44:49.000000000 +0200 patch-stamp make just doesn't know that configure is older than patch-stamp. I suggest you either don't patch configure at all, or have all patches applied to it. Note that there used to be a time when 2.6 kernels used to keep timestamps of files while they were in memory more accurate, but that seems to have been changed in newer kernels. Kurt -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
