[Pkg-samba-maint] Problems with autoconf.patch and 3.2.0pre1

[Christian Perrier]

Quoting Steve Langasek (vorlon at debian.org):

> > Thanks for the hint.
> 
> Er -- you should *not* have autoconf2.13 installed, that package is obsolete
> and doesn't work the same as recent versions of autoconf.  I meant that
> having autoconf2.13 installed could be a *cause* of the problem, not a fix
> for it.

Yep, I discovered that yesterday. Indeed, your previous message was
ambiguous..:-). I was suprised to see autoconf2.13 install a diversion
of autoconf (logical, after all).....but just thought "Okay, Steve
says so, so just don't think".

The result was funny, autoconf ran without errors, produced a small
patch as expected (while autoconf 2.50 produces a giant one)...but the
package didn't build either.

Did I already say "black magic"?

> Anyway, I've just had a chance to test myself and it's not an autoconf
> installation problem - I get the same error here, on a system that I know
> has a good autoconf install (tested against samba 3.0.26, even).
> 
> I'm still not sure what causes the error, but it turns out that using the
> autoconf command from autogen.sh works just fine:
> 
>    autoconf -I m4 -I lib/replace


OK, will go that way.


-------------- 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-samba-maint/attachments/20071002/216eb8fe/attachment.pgp