This is the mail archive of the
mailing list for the Cygwin project.
Re: igawk problem
- From: Igor Pechtchanski <pechtcha at cs dot nyu dot edu>
- To: Hans Horn <hannes at 2horns dot com>
- Cc: cygwin at cygwin dot com
- Date: Fri, 13 Aug 2004 23:30:49 -0400 (EDT)
- Subject: Re: igawk problem
- References: <email@example.com>
- Reply-to: cygwin at cygwin dot com
On Fri, 13 Aug 2004, Hans Horn wrote:
> 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
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... ;-)
|\ _,,,---,,_ firstname.lastname@example.org
ZZZzz /,`.-'`' -. ;-;;,_ email@example.com
|,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