Bug#424168: Fixing the "twice build" failure

[Roberto C. Sánchez]

It appears that our packages have been hit by the "twice build" failure.
These are the relevant portions of the build log (they are identical for
both source packages):

.....
dpkg-source: cannot represent change to saslauthd/config/config.guess:
dpkg-source:  new version is symlink
dpkg-source:  old version is something else
dpkg-source: cannot represent change to saslauthd/config/config.sub:
dpkg-source:  new version is symlink
dpkg-source:  old version is something else
dpkg-source: cannot represent change to saslauthd/config/ltmain.sh:
dpkg-source:  new version is symlink
dpkg-source:  old version is something else
.....

.....
dpkg-source: warning: ignoring deletion of file config/libtool.m4
dpkg-source: warning: ignoring deletion of file include/md5global.h
dpkg-source: warning: ignoring deletion of file plugins/anonymous_init.c
dpkg-source: warning: ignoring deletion of file plugins/crammd5_init.c
dpkg-source: warning: ignoring deletion of file plugins/digestmd5_init.c
dpkg-source: warning: ignoring deletion of file plugins/gssapiv2_init.c
dpkg-source: warning: ignoring deletion of file plugins/kerberos4_init.c
dpkg-source: warning: ignoring deletion of file plugins/ldapdb_init.c
dpkg-source: warning: ignoring deletion of file plugins/login_init.c
dpkg-source: warning: ignoring deletion of file plugins/ntlm_init.c
dpkg-source: warning: ignoring deletion of file plugins/otp_init.c
dpkg-source: warning: ignoring deletion of file plugins/passdss_init.c
dpkg-source: warning: ignoring deletion of file plugins/plain_init.c
dpkg-source: warning: ignoring deletion of file plugins/sasldb_init.c
dpkg-source: warning: ignoring deletion of file plugins/sql_init.c
dpkg-source: warning: ignoring deletion of file plugins/srp_init.c
dpkg-source: building cyrus-sasl2 in cyrus-sasl2_2.1.22.dfsg1-10.dsc
dpkg-source: unrepresentable changes to source
.....

What this indicates (to me, at least) is that in some cases the clean
target is not properly removing everything (the ltmain.sh and config.*
files are autogenerated by ./configure) and improperly removing things
in other cases (it appears many files from the plugins/ directory).

I think that one thing that can be done is to build in a subdirectory of
the source root.  Basically, you make a directory (say, for example,
build/) and then cd into it.  Then you run your configure as
../configure instead of ./configure.  I think that everything else is
the same.  Then, in the clean target of debian/rules, we can just blow
away the whole build/ subdirectory.

I'd like to get some opinions on this.

Regards,

-Roberto
-- 
Roberto C. Sánchez
http://people.connexer.com/~roberto
http://www.connexer.com
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 189 bytes
Desc: Digital signature
Url : http://lists.alioth.debian.org/pipermail/pkg-cyrus-sasl2-debian-devel/attachments/20070526/c1cf781f/attachment-0003.pgp