[sr #107444] constructs generated by autoconf do not work in the ash shell

Update of sr #107444 (project autoconf): Status: Need Info => Works For Me Open/Closed:Open => Closed ___ Follow-up Comment #4: We never heard bac

[sr #107444] constructs generated by autoconf do not work in the ash shell

Follow-up Comment #3, sr #107444 (project autoconf): Mark, I really need information on which version of ash this affects, before I can do anything about this bug report. Can you please answer? ___ Reply to this item at:

Re: [sr #107444] constructs generated by autoconf do not work in the ash shell

On 08/03/10 01:30, Mark Hobley wrote: > Some versions of the ash shell will not allow redirection to a stream number > held in a variable: > > # This construct does not work in some versions of the ash shell > echo $1 >&$2 What do these shells do? For example, if /bin/ash is where your ash

[sr #107444] constructs generated by autoconf do not work in the ash shell

Update of sr #107444 (project autoconf): Status:None => Need Info ___ Follow-up Comment #2: Please report this to the dash maintainer, as Posix requires parameter expansion to occur for

[sr #107444] constructs generated by autoconf do not work in the ash shell

Follow-up Comment #1, sr #107444 (project autoconf): Can you check if this works: set abc 2 eval "echo $1 >&$2" ___ Reply to this item at: ___

[sr #107444] constructs generated by autoconf do not work in the ash shell

URL: Summary: constructs generated by autoconf do not work in the ash shell Project: Autoconf Submitted by: markhobley Submitted on: Tue 03 Aug 2010 08:30:57 AM GMT Category: None