This is the mail archive of the
cygwin
mailing list for the Cygwin project.
Re: ImageMagick "display" and "convert" fail with a Visual C++ runtime error
- From: Igor Peshansky <pechtcha at cs dot nyu dot edu>
- To: dmitry at math dot uakron dot edu
- Cc: cygwin at cygwin dot com
- Date: Wed, 25 Apr 2007 12:31:10 -0400 (EDT)
- Subject: Re: ImageMagick "display" and "convert" fail with a Visual C++ runtime error
- References: <984298f00704192225n97bd4f0uc76ef0ce396c7cff@mail.gmail.com>
- Reply-to: cygwin at cygwin dot com
On Fri, 20 Apr 2007, Dmitry Golovaty wrote:
> Thanks - the culprit is the MATLAB entry
>
> /cygdrive/c/Program Files/MATLAB/R2007a/bin/win32
>
> in the path; removing it fixes the problem ... is there way to pluck
> it out automatically (e.g. in .bashrc) when the path is imported from
> Windows at Cygwin start-up? Thanks again and sorry for starting
> another thread - I did not subscribe in time to get the original
> message.
PATH is usually processed left-to-right. As an alternative to what Brian
suggested, simply prepending C:\cygwin\bin to the PATH should work.
FWIW, the above is already done in the standard shell startup scripts, so
unless you're using custom .*rc scripts, you probably attempted to invoke
ImageMagick from a Windows command prompt. One word of warning for
working in that mode: some of the programs in /bin are symbolic links or
scripts that Windows does not understand. You're better off invoking
Cygwin programs from a Cygwin shell, unless you're sure they are .exe
files.
Igor
--
http://cs.nyu.edu/~pechtcha/
|\ _,,,---,,_ pechtcha@cs.nyu.edu | igor@watson.ibm.com
ZZZzz /,`.-'`' -. ;-;;,_ Igor Peshansky, Ph.D. (name changed!)
|,4- ) )-,_. ,\ ( `'-' old name: Igor Pechtchanski
'---''(_/--' `-'\_) fL a.k.a JaguaR-R-R-r-r-r-.-.-. Meow!
Freedom is just another word for "nothing left to lose"... -- Janis Joplin
--
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/