[Top][All Lists]
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: Problem with sh "shift" command in config.status on HP-UX
From: |
Ralf Wildenhues |
Subject: |
Re: Problem with sh "shift" command in config.status on HP-UX |
Date: |
Thu, 26 Mar 2009 07:06:57 +0100 |
User-agent: |
Mutt/1.5.18 (2008-05-17) |
Hello Daniel,
thanks for the report.
* Daniel Richard G. wrote on Thu, Mar 26, 2009 at 05:06:45AM CET:
> I upgraded my copy of Automake from 1.10.1 to 1.10.2, and suddenly,
> builds are failing on two separate HP-UX systems (B.11.00 on 32-bit
> PA-RISC, and B.11.23 on IA64).
Weird. I haven't noticed such a failure.
> config.status: executing depfiles commands
> ./config.status[1763]: shift: The specified number is not valid for this
> command.
> ----(cut here)----
> # are listed without --file. Let's play safe and only enable the eval
> # if we detect the quoting.
> case $CONFIG_FILES in
> *\'*) eval set x "$CONFIG_FILES" ;;
> *) set x $CONFIG_FILES ;;
> esac
> shift <== line 1763
> for mf
> do
> # Strip MF so we end up with the name of the file.
> mf=`echo "$mf" | sed -e 's/:.*$//'`
> # Check whether this is an Automake generated Makefile or not.
> ----(snip snip snip)----
>
> I suspect the real problem is that "shift" is being called when there are no
> positional parameters ($1, $2, ...) to shift. (Sure enough, just before the
> shift, $# is 0.)
But how can this be. Just before the shift, one of the two "set"
commands is executed and sets $1 to "x". Which is exactly what the
shift aims to undo!
Are you sure this is the position the error is happening?
Thanks,
Ralf