On 2016-07-28 20:28 +0200, Sven Joachim wrote:
> On 2016-07-28 17:45 +0100, Wookey wrote:
> 
> > On 2016-07-28 15:19 +0200, Sven Joachim wrote:
> >> 
> >> They should not be used at all, but Mr. Davis has these special broken
> >> tests for them. :-(  And while I appreciate that you applied my patch to
> >> autoconf/aclocal.m4, the problem is not fixed as long as 'configure' is
> >> not regenerated.
> >
> > Hmm. But configure is regenerated (on a second build dpkg-source
> > complains that 'configure' has changed). And I checked that the
> > updated configure has the debian terminfo directory, added from the
> > aclocal patch.
> >
> > Run dpkg-buildpackage and check the configure file:
> > grep terminfo configure 
> > { $as_echo "$as_me:${as_lineno-$LINENO}: checking for terminfo" >&5
> > $as_echo_n "checking for terminfo... " >&6; }
> >    MISC_TERMINFO_DIRS=`$nc5config --terminfo`
> >                   /usr/lib/terminfo \
> >                   /usr/share/terminfo \
> >                   /usr/share/lib/terminfo \
> >               /usr/local/lib/terminfo \
> >               /lib/terminfo"
> >
> > What test are you doing to determine that this problem is not fixed?
> 
> I ran pbdebuild, where /usr/share/terminfo has been rmdir'ed from the
> build chroot beforehand.  Attached is a build log.

I use sbuild, but this shouldn't matter.
 
> > It is possible I guess that the configure flie is being updated too
> > late so the dir is not checked in time, but I just checked
> > that removing the /usr/share/terminfo did not break the build.
> 
> Did you also ensure that libtinfo-dev is not installed on the build
> system?  Because if it is, linking with -ltermcap succeeds, and the
> jed package gains a spurious dependency on libtinfo5.

My build chroot is clean so that package is not in it. Still builds OK for me. 
Same with a local build in jessie.

OK. I've managed to reproduce it now. 

> Well, in a normal build system configure _is_ updated, but only after
> building jed and before building xjed.  Which is a bit too late.

OK. I've done a better job of ensuring configure is generated before
first usage, and backed-up/restored so a second build works as
well. Basically a manual dh_autoreconf.
3rd time lucky... uploaded.

Wookey
-- 
Principal hats:  Linaro, Debian, Wookware, ARM
http://wookware.org/

Attachment: signature.asc
Description: Digital signature

Reply via email to