Re: Migrating to autoconf 2.52g

[Tim Van Holder]

On Tue, 2002-02-05 at 10:37, John Poltorak wrote:
> On Tue, Feb 05, 2002 at 09:06:33AM +0100, Akim Demaille wrote:
> 
> File::Glob::csh_glob(c:/usr/lib/perl/lib/5.6.0/os2/File/Glob.pm:164):
> 164:                delete $entries{$cxix};
>   DB<2>
> File::Glob::csh_glob(c:/usr/lib/perl/lib/5.6.0/os2/File/Glob.pm:165):
> 165:                return undef;
>   DB<2>
> Autom4te::General::CODE(0x26e548)(c:/usr/local/share/autoconf/Autom4te/General.pm:110):
> 110:          rmdir $tmp
> 111:            or carp ("$me: cannot remove $tmp: $!\n"), _exit (1);
>   DB<2>
> Autom4te::General::CODE(0x26e548)(c:/usr/local/share/autoconf/Autom4te/General.pm:116):
> 116:      close STDOUT
> 117:        or (carp "$me: closing standard output: $!\n"), _exit (1);
>   DB<2>
> Autom4te::General::CODE(0x26e548)(c:/usr/local/share/autoconf/Autom4te/General.pm:119):
> 119:      _exit ($exit_status);
>   DB<2>
> autoupdate.: cannot close autom4te --language=autoconf 
> --include=c:/usr/local/share/autoconf
>  --trace AU_DEFUN:'AU:$f:$1' --trace define:'AC:$f:$1' --melt /dev/null |:
>  at c:/usr/local/bin/autoupdate. line 185

I'm no expert either on autoconf traces, but if that $f resolves to a
file name (as its name sorta suggests), the use of a colon as separator
may conflict with the drivespec in the filename (assuming it's present
anyway).

> I'm no Perl expert, and have no idea what is going on here so can anyone 
> explain why it's failing?

Well I assume the actual error message means that automate is run, but
does not complete properly.  This _may_ be a problem with the OS/2 perl
port (or even a libc issue).  I do still see /dev/null used (which gave
errors before IIRC); you might want to start by changing the use of
/dev/null to NUL (assuming NUL is the null device on OS/2).