executable won't run on another machine

sik0fewl xxdigitalhellxx at hotmail.com
Tue Apr 8 19:26:37 CEST 2003


Ben Hutchings wrote:
> In article <v90mh6ppf9bc09 at corp.supernews.com>, Lance wrote:
> 
>>Hi All,
>>
>>I created an executable using McMillan's Installer. It runs great on the
>>development machine. I copied it to another machine and it doesn't run. I
>>type the executable name from a command prompt, hit return, and get another
>>command prompt.
> 
> <snip>
> 
> Did you put './' in front of the executable name?  Most Unix systems are
> configured not to include the current directory in the search path.  If
> you forgot to do that then you could be running some other program that is
> in the search path.

This is especially true if you call your executable 'test' (which I've 
done more than once) because the Unix command 'test' prints nothing to 
stdout or stderr, so you just get another command prompt.

-- 
Hope this helps,
Ryan





More information about the Python-list mailing list