Re: [GNU Autoconf 2.59d] testsuite: 202 failed

2006-05-18 Thread Ralf Menzel 
Hi Ralf,

I applied your proposed patch (with the break 2 modification) and it
fixes the testsuite error. (For whatever that is worth.)

Bye,
Ralf

[GNU Autoconf 2.59d] testsuite: 202 failed

2006-05-17 Thread Ralf Menzel 
Hi,

the latest patches related to mkdir seem to cause problems with
/usr/bin/mkdir of Solaris 9.

I attach the log of the testsuite. Tell me how I can help.

Bye,
Ralf Menzel



testsuite.log
Description: tests/testsuite.log

Re: [GNU Autoconf 2.59d] testsuite: 202 failed

2006-05-17 Thread Ralf Wildenhues 
Argh, for this description to be correct...

* Ralf Wildenhues wrote on Wed, May 17, 2006 at 02:40:09PM CEST:
 
 Note I don't bother to search all of PATH for a suitable mkdir --
 I don't think people go to lenghts to install GNU coreutils mkdir and
 then put it late in the PATH.

...it needs to be `break 2'...

 +[_AS_PATH_WALK([],
 +[for ac_exec_ext in '' $ac_executable_extensions; do
 +  if AS_EXECUTABLE_P([$as_dir/mkdir$ac_exec_ext]); then
 +if $as_dir/mkdir$ac_exec_ext -p --version . /dev/null 21 \
 + test ! -d ./--version; then
 +  ac_cv_prog_mkdir_p=$as_dir/mkdir$ac_exec_ext -p
 +else
 +  for ac_d in ./-p ./--version
 +  do
 + test -d $ac_d  rmdir $ac_d
 +  done
 +  ac_cv_prog_mkdir_p=$ac_install_sh -d
 +fi
 +break

...here, which is what I intended.

 +  fi
 +done])
 +])

Re: [GNU Autoconf 2.59d] testsuite: 202 failed

2006-05-17 Thread Paul Eggert 
Ralf Wildenhues [EMAIL PROTECTED] writes:

 The config.status special magic from this patch:
 http://lists.gnu.org/archive/html/autoconf-patches/2006-05/msg00041.html
 doesn't work if we don't also use a program with an absolute name.

What's the bug with it?  Sorry, I don't follow.

 OK to apply this patch to fix both?

I'd rather not use an absolute name in the normal case.  It makes
'make' output look really ugly.  In the normal case, $(MKDIR_P) should
expand to mkdir -p, not to /usr/local/bin/mkdir -p or whatever.

Re: [GNU Autoconf 2.59d] testsuite: 202 failed

2006-05-17 Thread Ralf Wildenhues 
* Paul Eggert wrote on Wed, May 17, 2006 at 07:37:18PM CEST:
 Ralf Wildenhues [EMAIL PROTECTED] writes:
 
  The config.status special magic from this patch:
  http://lists.gnu.org/archive/html/autoconf-patches/2006-05/msg00041.html
  doesn't work if we don't also use a program with an absolute name.
 
 What's the bug with it?  Sorry, I don't follow.

Oh, I forgot to explain.  Sorry about that.

cat configure.ac EOF
AC_INIT
AC_PROG_MKDIR_P
AC_CONFIG_FILES(sub/foo)
AC_OUTPUT
EOF
echo @MKDIR_P@  sub/foo.in
autoconf
./configure

On GNU/Linux, sub/foo will contain:
../mkdir -p

  OK to apply this patch to fix both?
 
 I'd rather not use an absolute name in the normal case.  It makes
 'make' output look really ugly.  In the normal case, $(MKDIR_P) should
 expand to mkdir -p, not to /usr/local/bin/mkdir -p or whatever.

Well, then you need a different method in the config.status code to
detect whether you need to munge with $MKDIR_P for subdirectories, i.e.,
a different way to detect that MKDIR_P contains a path that is relative
to the build tree.

Cheers,
Ralf