On Fri, 13 Aug 2004, Hans Horn wrote:
> Group,
>
> I have a rather lengthy awk script (that internally includes a bunch of awk
> library functions; therefore I'm using igawk).
>
> When I invoke it, e.g. like
>
> echo | igawk -f script.awk
> eval: gawk: argument list too long
>
> The script and the awk library functions together make up approx. 34kByte.
>
> Does anybody have a clue whether I'm running here into a hard shell limit,
> or some internal limit of gawk?
This looks like an upstream igawk portability bug -- the lines
processed_program=`gawk -- "$expand_prog" /dev/stdin <<EOF
$program
EOF
look like the culprit. They should be using xargs instead...
This is a Win32 limit, and it has to do with the fact that gawk is invoked
using Win32 calls by default. There are a few solutions, one of the
easiest being to "mount -X" your /bin and /usr/bin directories. Or, you
can fix igawk to use xargs and submit your patch upstream... ;-)
Igor
--
http://cs.nyu.edu/~pechtcha/
|\ _,,,---,,_ [EMAIL PROTECTED]
ZZZzz /,`.-'`' -. ;-;;,_ [EMAIL PROTECTED]
|,4- ) )-,_. ,\ ( `'-' Igor Pechtchanski, Ph.D.
'---''(_/--' `-'\_) fL a.k.a JaguaR-R-R-r-r-r-.-.-. Meow!
"Happiness lies in being privileged to work hard for long hours in doing
whatever you think is worth doing." -- Dr. Jubal Harshaw
--
Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple
Problem reports: http://cygwin.com/problems.html
Documentation: http://cygwin.com/docs.html
FAQ: http://cygwin.com/faq/
