Re: CVS automake testsuite failures under Tru64 unix v5.1A

[Nicolas Joly]

On Thu, Dec 05, 2002 at 04:54:52PM +0100, Alexandre Duret-Lutz wrote:
> >>> "Nicolas" == Nicolas Joly <address@hidden> writes:
> 
>  Nicolas> FAIL: texinfo3.test
>  Nicolas> FAIL: texinfo13.test
>  Nicolas> FAIL: texinfo16.test
>  Nicolas> FAIL: texinfo18.test
>  Nicolas> FAIL: version7.test
> 
> Ouch!  I was hopping we could release 1.7.2 today :(

Sorry.

>  Nicolas> All seems to be related to `make distcheck' problems with vendor
>  Nicolas> make, as using GNU make solves all problems.
> 
> They all seem to follow the same pattern: the info file get
> rebuilt during distcheck.  This should not happen since info
> files are distributed.
> 
> [...]
>  Nicolas> === Running test ./texinfo13.test
> [...]
>  Nicolas> + cd build 
>  Nicolas> + ../configure 
>  Nicolas> configure: loading site script /usr/local/share/config.site
>  Nicolas> checking for a BSD-compatible install... ../install-sh -c
>  Nicolas> checking whether build environment is sane... yes
>  Nicolas> checking for gawk... no
>  Nicolas> checking for mawk... no
>  Nicolas> checking for nawk... nawk
>  Nicolas> checking whether make sets $(MAKE)... yes
>  Nicolas> configure: creating ./config.status
>  Nicolas> config.status: creating Makefile
>  Nicolas> + make distcheck 
>  Nicolas> test -f subdir/.dirstamp || make subdir/.dirstamp
>  Nicolas> mkdir -p -- subdir
>  Nicolas> Updating subdir/version.texi
>  Nicolas> { test ! -d texinfo13-1.0  || { find texinfo13-1.0 -type d ! -perm 
> -200 -exec chmod u+w {} ';'  && rm -fr texinfo13-1.0; }; }
>  Nicolas> mkdir texinfo13-1.0
>  Nicolas> /bin/ksh ../mkinstalldirs texinfo13-1.0/subdir
>  Nicolas> mkdir -p -- texinfo13-1.0/subdir
>  Nicolas> make   top_distdir="." distdir="texinfo13-1.0"  dist-info
>  Nicolas> /bin/ksh /home/njoly/temp/automake/tests/testSubDir/missing --run 
> makeinfo   -I subdir -I ../subdir  -o subdir/main.info `test -f 
> '../subdir/main.texi' || echo '../'`../subdir/main.texi
> 
> subdir/main.info is first built here, this is ok.
> 
>  Nicolas> list='subdir/main.info';  for base in $list; do  if test -f $base; 
> then d=.; else d=..; fi;  for file in $d/$base*; do  relfile=`expr "$file" : 
> "$d/\(.*\)"`;  test -f texinfo13-1.0/$relfile ||  cp -p $file 
> texinfo13-1.0/$relfile;  done;  done
> 
> subdir/main.info should be copied to $(distdir) here.  Looking
> at the output we don't know whether that happened or not.  If it
> somehow failed to be copied to $(distdir) this can explain the
> distcheck failure.

address@hidden [tests/testSubDir]> find . -name 'main.info'    
./build/subdir/main.info
./build/texinfo13-1.0/subdir/main.info
./build/texinfo13-1.0/=build/subdir/main.info

> [...]
> 
>  Nicolas> checking for a BSD-compatible install... ../install-sh -c
>  Nicolas> checking whether build environment is sane... yes
>  Nicolas> checking for gawk... no
>  Nicolas> checking for mawk... no
>  Nicolas> checking for nawk... nawk
>  Nicolas> checking whether make sets $(MAKE)... yes
>  Nicolas> configure: creating ./config.status
>  Nicolas> config.status: creating Makefile
>  Nicolas> test -f subdir/.dirstamp || make subdir/.dirstamp
>  Nicolas> mkdir -p -- subdir
>  Nicolas> Updating subdir/version.texi
>  Nicolas> /bin/ksh 
> /home/njoly/temp/automake/tests/testSubDir/build/texinfo13-1.0/missing --run 
> makeinfo   -I subdir -I ../subdir  -o subdir/main.info `test -f 
> '../subdir/main.texi' || echo '../'`../subdir/main.texi
> 
> main.info gets rebuilt here.  This make no sense if main.info was distributed.
> 
> Could you try the following?
> 
> cd tests
> ./texinfo13.test
> cd testSubDir
> tar zxvf texinfo13-1.0.tar.gz

Ok, but there is no archive created in `testSubDir'.

address@hidden [tests/testSubDir]> find . -name '*.gz'
./build/texinfo13-1.0.tar.gz

> cd texinfo13-1.0
> ls subdir
> ./configure
> make
>
> According to the trace you sent, this `make' should cause
> `main.info' to be rebuilt (unexpectedly).
> 
> Does Tru64 make supports a debug options like `-d'?  
> Maybe this could help :)

No, the only thing i can do to help is the `-p' flag :

  -p  Displays all the macro definitions target and prerequisite descriptions
      including modification times.  This information is displayed both
      before and after description file processing has occurred.

-- 
Nicolas Joly

Biological Software and Databanks.
Pasteur Institute, Paris.