gracebat runs in X, but not as a system call from a perl script

[Andrew DeFaria]

moka@hol.gr wrote:
> Forgot to say that the error message is :the system cannot
> execute the specified program
> (failure code 256)
>
>> I do startxwin to open X and then do
>> gracebat <parameters>
>> this does what I want, namely produce a jpeg file
>>
>> Now if I try this for a perl script(run from X)
>> system(gracebat <parameters>)
>>
>> i.e. the exact same line that produced the right result
>> I get an error.
>>
>> I guess the reason is that I am using the activestate perl instead of the
>> cygwin
>> perl; anyway there were reasons for that, not sure if valid or not[the
>> reason
>> was getting DBD::Oracle to work, which was a huge pain].
>> So I guess "system" to perl is whatever system Activestate was installed
>> for,
>> i.e. Windows.
>> The question is:
>> Is it possible to get around this?
>> Can I tweak the system command so that it executes gracebat(but
>> otherwise use Activestate, e.g. for Oracle DBI queries?
If you use Activestate then I believe it invokes cmd.exe for your system 
call. Take the parameter you passed to system in your Activestate perl 
and plug it into a cmd.exe shell (copy and paste). Massage until it 
works under cmd and copy and paste that new command back into your perl 
and it should work.

My guesses would be that you are using "C:/path/to/gracebat <parms>" and 
Activestate invoking cmd can't find that or perhaps you are literally 
using "gracebat <parms>" and gracebat is in Cygwin's PATH but not cmd's 
PATH.
-- 
Andrew DeFaria <http://defaria.com>
If work is so terrific, why do they have to pay you to do it?


--
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/