From: Gene Fodor <efodor@zworld.com>
To: sourcenav@sourceware.cygnus.com
Subject: Re: Upgrading windows SN broke grep!
Date: Fri, 14 Sep 2001 17:00:00 -0000 [thread overview]
Message-ID: <4.1.20010914164746.00c49700@zmail> (raw)
In-Reply-To: <3BA29055.9763E56@redhat.com>
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.
next prev parent reply other threads:[~2001-09-14 17:00 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-09-14 15:54 Gene Fodor
2001-09-14 16:06 ` Ian Roxborough
2001-09-14 17:00 ` Gene Fodor [this message]
2001-09-14 17:09 ` Ian Roxborough
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=4.1.20010914164746.00c49700@zmail \
--to=efodor@zworld.com \
--cc=sourcenav@sourceware.cygnus.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).