Failure of `make.test'

2008-07-01 Thread Ludovic Courtès
Hi,

This is with Automake 1.10.1 on GNU/Linux (NixOS), with Autoconf 2.62:

/tmp/nix-build-asfyknxas01zm7gr00sw7z2h9jqszv8b-automake-1.10.1.drv-0/automake-1.10.1/tests:/nix/store/4p6cj78b188n649fjf1fz1gi3hl2dw40-perl-5.10.0/bin:/nix/store/cxc8hfhxayw773csnrsidsdr1dq9h55p-autoconf-2.62/bin:/nix/store/ylbjk3gsrbnbbcapx2rqhbjs40sw57c0-gcc-4.2.4/bin:/nix/store/68afga4khv0ws37n00qy06m11srx1lhj-coreutils-6.12/bin:/nix/store/r9k93bv42mam9krqfp6mqkfg0yh5iy1d-findutils-4.2.33/bin:/nix/store/rdy412gsf858lada2d0nd15kxszfj0ks-diffutils-2.8.1/bin:/nix/store/5x9yj9ypb0s9mc2b5za1mbydp8ax62jz-gnused-4.1.5/bin:/nix/store/mjzv772s5y2v89mgv1d4vifrbwvh9x1f-gnugrep-2.5.3/bin:/nix/store/x3r3p1hyf5zlzwzpddvj4l95znprl3la-gawk-3.1.6/bin:/nix/store/md2hjc11ks0nc093b7ar12xzslv1wrqp-gnutar-1.20/bin:/nix/store/kcgpcilybvi0svy1404qdybnbv9jcnn7-gzip-1.3.12/bin:/nix/store/40ir4rhcxc4f87n2fbzfkwvx9w2n194x-bzip2-1.0.5/bin:/nix/store/n1ivd8bha9bcrkrg62hq9p6gr019d5g4-gnumake-3.81/bin:/nix/store/vdzbaimmqgnzbv41jlz04h0pfwxi9vc6-bash-3.2-p39/bin:/nix/store/lz9vfxg7c4fjys1bx5kcn34rvlg02d6b-gnupatch-2.5.4/bin:/nix/store/mpkpfgpr34rwmls9qcrlpvgrjsr3fp6c-replace-2.24/bin:/nix/store/a6kwvyyy65bcg0zhq0y7r93w2fc3vys7-patchelf-0.4/bin:/nix/store/18cjrw11vwmpx0jkk6mdwfc4caj99714-gcc-4.2.4/bin:/nix/store/7a32kkwjdqmy09hwpl4f7pa0rii91ksl-binutils-2.18/bin:/nix/store/b2gmgy8y6nidjj7n34jx4sanrjdaxrw3-glibc-2.7/bin
make: running make --version -v | grep GNU
GNU Make 3.81
=== Running test ./make.test
++ pwd
/tmp/nix-build-asfyknxas01zm7gr00sw7z2h9jqszv8b-automake-1.10.1.drv-0/automake-1.10.1/tests/testSubDir
+ cat
+ :
+ set -e
+ aclocal-1.10 -Werror
+ autoconf
+ automake-1.10 --foreign -Werror -Wall
+ export ACLOCAL
+ export AUTOCONF
+ export AUTOMAKE
+ save=make
+ for flag in ''\'''\''' -w
+ MAKE='make '
+ ./configure
checking for a BSD-compatible install... 
/nix/store/68afga4khv0ws37n00qy06m11srx1lhj-coreutils-6.12/bin/install -c
checking whether build environment is sane... yes
checking for a thread-safe mkdir -p... 
/nix/store/68afga4khv0ws37n00qy06m11srx1lhj-coreutils-6.12/bin/mkdir -p
checking for gawk... gawk
checking whether make  sets $(MAKE)... yes
checking for style of include used by make ... GNU
configure: creating ./config.status
config.status: creating Makefile
+ /nix/store/mjzv772s5y2v89mgv1d4vifrbwvh9x1f-gnugrep-2.5.3/bin/grep -F 
'am__include = include' Makefile
am__include = include
+ touch configure.in
+ make
cd .  aclocal-1.10 -Werror 
 cd .  automake-1.10 --foreign -Werror -Wall --foreign 
cd .  autoconf
/bin/sh ./config.status --recheck
running CONFIG_SHELL=/bin/sh /bin/sh ./configure --no-create --no-recursion
checking for a BSD-compatible install... 
/nix/store/68afga4khv0ws37n00qy06m11srx1lhj-coreutils-6.12/bin/install -c
checking whether build environment is sane... yes
checking for a thread-safe mkdir -p... 
/nix/store/68afga4khv0ws37n00qy06m11srx1lhj-coreutils-6.12/bin/mkdir -p
checking for gawk... gawk
checking whether make sets $(MAKE)... yes
checking for style of include used by make... GNU
configure: creating ./config.status
 /bin/sh ./config.status
config.status: creating Makefile
make: Nothing to be done for `all'.
+ /nix/store/mjzv772s5y2v89mgv1d4vifrbwvh9x1f-gnugrep-2.5.3/bin/grep -F 
'am__include = include' Makefile
am__include = include
+ rm -f config.cache
+ for flag in ''\'''\''' -w
+ MAKE='make -w'
+ ./configure
checking for a BSD-compatible install... 
/nix/store/68afga4khv0ws37n00qy06m11srx1lhj-coreutils-6.12/bin/install -c
checking whether build environment is sane... yes
checking for a thread-safe mkdir -p... 
/nix/store/68afga4khv0ws37n00qy06m11srx1lhj-coreutils-6.12/bin/mkdir -p
checking for gawk... gawk
checking whether make -w sets $(MAKE)... yes
checking for style of include used by make -w... none
configure: creating ./config.status
config.status: creating Makefile
+ /nix/store/mjzv772s5y2v89mgv1d4vifrbwvh9x1f-gnugrep-2.5.3/bin/grep -F 
'am__include = include' Makefile


That last command returns 1.  Indeed, grep am__include Makefile
returns 1, too.

Any idea?

Thanks,
Ludovic.





Re: Failure of `make.test'

2008-07-01 Thread Stepan Kasal
Hello,
  to reproduce what the test does, try the following:

mkdir test.dir
cd test.dir
cat  configure.ac \EOF
AC_INIT(foo,0,np)
AM_INIT_AUTOMAKE(foreign)
AM_MAKE_INCLUDE
AC_OUTPUT(Makefile)
EOF
touch Makefile.am
autoreconf -i
MAKE='make -w' ./configure

In my case, the configure output contains (near the end):
checking for style of include used by make -w... GNU

But in your case, it will probably be:

 checking for style of include used by make -w... none

Attached below please find a test similar to that pefofrmed by configure.
Could you please try it?  What is the output?

Have a nice day,
Stepan

#!/bin/sh
am_make='make -w'
cat  confinc  'END'
am__doit:; @echo done
.PHONY: am__doit
END
# If we don't find an include directive, just comment out the code.
echo -n checking for style of include used by $am_make... 
am__include=#
am__quote=
_am_result=none
# First try GNU make style include.
echo include confinc  confmf
# We grep out `Entering directory' and `Leaving directory'
# messages which can occur if `w' ends up in MAKEFLAGS.
# In particular we don't look at `^make:' because GNU make might
# be invoked under some other name (usually gmake), in which
# case it prints its new name instead of `make'.
if test `$am_make -s -f confmf 2 /dev/null | grep -v 'ing directory'` = 
done; then
   am__include=include
   am__quote=
   _am_result=GNU
fi
# Now try BSD make style include.
if test $am__include = #; then
   echo '.include confinc'  confmf
   if test `$am_make -s -f confmf 2 /dev/null` = done; then
  am__include=.include
  am__quote=\
  _am_result=BSD
   fi
fi
echo $_am_result
rm -f confinc confmf





Re: Failure of `make.test'

2008-07-01 Thread Ludovic Courtès
Hi,

Stepan Kasal [EMAIL PROTECTED] writes:

   to reproduce what the test does, try the following:

Unfortunately, I can't run it with the in-tree Automake, because
`autoreconf' won't find $prefix/share/aclocal-1.10, for instance.  How
can I make it use the in-tree files?

 Attached below please find a test similar to that pefofrmed by configure.
 Could you please try it?  What is the output?

It displays none.

Thanks,
Ludovic.





Re: Failure of `make.test'

2008-07-01 Thread Stepan Kasal
Hello,

On Tue, Jul 01, 2008 at 05:39:27PM +0200, Ludovic Courtès wrote:
to reproduce what the test does, try the following:
 
 Unfortunately, I can't run it with the in-tree Automake, because
 `autoreconf' won't find $prefix/share/aclocal-1.10, for instance.  How
 can I make it use the in-tree files?

the build tree creates wrappers in the tests/ subdir and then defs
adds that to the beginning of PATH.

But it does not matter here, since:

  Attached below please find a test similar to that pefofrmed by configure.
  Could you please try it?  What is the output?
 
 It displays none.

It means that make -w behaves strange on your platform.  (Try
replacing make -w with make at the top of the script; then the
answer will be GNU, right?)

You should report it to the vendor of your platform (NixOS).

OTOH, AFAIK, make -w is not used much, so it is quite probable that
this problem does not affect you in practical life at all.

Have a nice day,
Stepan




Re: Failure of `make.test'

2008-07-01 Thread Ludovic Courtès
Hi,

Stepan Kasal [EMAIL PROTECTED] writes:

 It means that make -w behaves strange on your platform.  (Try
 replacing make -w with make at the top of the script; then the
 answer will be GNU, right?)

 You should report it to the vendor of your platform (NixOS).

Yes, actually I had forgotten that NixOS' GNU Make package is modified
to produce additional output suitable for the `nix-log2xml' tool.  This
is what the test is catching.

Thanks, and sorry for the noise,
Ludovic.





Re: Failure of `make.test'

2008-07-01 Thread Ludovic Courtès
Hi,

Ralf Wildenhues [EMAIL PROTECTED] writes:

 You could also write a patch letting automake/m4/make.m4 drop that extra
 output.  Or at least show us what it is.

The extra output [*] is (1) one line per goal sent to stderr, and (2) an
additional \e[p sequence to stdout when `-w' is used:

  $ a=`make -w -s -f confmf | grep -v 'ing directory'`
  building am__doit
  $ echo \`$a'
  `done
  '
(1) doesn't hurt here, but (2) causes the test to fail.

I'm not sure whether we want the test to work around this.

Thanks,
Ludovic.

[*] Patch available at:

https://svn.nixos.org/viewvc/nix/nixpkgs/trunk/pkgs/development/tools/build-managers/gnumake/log.patch?revision=10849view=markup