From mboxrd@z Thu Jan 1 00:00:00 1970 From: Gene Fodor To: sourcenav@sourceware.cygnus.com Subject: Re: Upgrading windows SN broke grep! Date: Fri, 14 Sep 2001 17:00:00 -0000 Message-id: <4.1.20010914164746.00c49700@zmail> References: <4.1.20010914154031.00c45bc0@zmail> <3BA29055.9763E56@redhat.com> X-SW-Source: 2001-q3/msg00156.html Ian, Well, I tried messing with my path a bit, but SN still could not find grep. I also noticed that hyper.exe seemed to be eating all my CPU time when I wasn't really trying to do anything. I have decided to downgrade to 4.52 as I don't seem to have these problems with that version. Other things that I noticed are: The version of grep that I use in cygwin and SN seem to be the same (using --version both reported 2.2), although I did not do a binary diff. The message would alternatively say "bad file number" or some such. Regards, Gene At 04:18 PM 9/14/01 -0700, you wrote: >Gene Fodor wrote: >> >> It seems as though SN 5.0 is having trouble finding grep. Here is the not >> so helpful error message I get: >> >> -code error -errorinfo couldn't execute "grep": invalid argument >> while executing >> "open "| ${cmd} " ?nonprintable char?" -errorcode POSIX EINVAL {invalid >> argument} couldn't execute "grep": invalid argument > >Can you run grep from the command line? > >What do you find if you search for grep.exe in Window explorer find files >thingy? > >> I have a feeling that it is using the wrong grep and have tried a couple of >> things to try to get it to see it, but without success. Any ideas? I was >> using the Enterprise version (pre-RedHat) of Source Navigator before >upgrading. > >Looks like your going to have to find the right grep and put it on your path >in front of which ever grep Sourcen-Navigator is or isn't finding. > >Ian.