odd PATH

odd PATH

[Konstantin Gorskov]

Hi! I'm building ffmpeg using cygwin+mingw32ce. I have build configure file successfully, but can not execute 'make' command properly. I get ffmpeg.d:1 ***multiple target patters.Stop.

Now, here is echo $PATH command output:
/cygdrive/c/mingw/bin:/usr/local/bin:/usr/bin:/bin:/usr/X11R6/bin:/cygdrive/c/Program Files/Common Files/SYmbian/Tools:/cygdrive/c/Program Files/ParaSOft/Insure++/bin.win32 and e.t.c (many other stupid program here)

I understand, that I get this error because of blank spaces if file paths, but
where does those Program Files comes from? How are they related to my build?
There are no tracks of them in profile either:
PATH=/cygdrive/c/mingw/bin:/usr/local/bin:/usr/bin:/bin:/usr/X11R6/bin:$PATH
export PATH

I do not see any references to Program Files, this is odd...

if it helps, 'which make' outputs /usr/bin/make ...

I'll appreciate any hints on this matter.
Regards,
Konstantin.


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

Re: odd PATH

[Brian Dessent]

Konstantin Gorskov wrote:

> Hi! I'm building ffmpeg using cygwin+mingw32ce. I have build configure file successfully, but can not execute 'make' command properly. I get ffmpeg.d:1 ***multiple target patters.Stop.

This probably means your Makefile contains Win32 (drive-letter) style
paths, which Cygwin make does not support.

> I understand, that I get this error because of blank spaces if file paths, but
> where does those Program Files comes from? How are they related to my build?
> There are no tracks of them in profile either:
> PATH=/cygdrive/c/mingw/bin:/usr/local/bin:/usr/bin:/bin:/usr/X11R6/bin:$PATH
> export PATH

This statement *prepends* a set of values to the existing value of
$PATH, which starts out with a value from the operating system
configuration.  Those other directories are already in your path from
Windows, as you can see if you look at PATH in a standard command prompt
(or from the GUI: System Properties -> Advanced tab -> Environment
Variables button.)  This likely has nothing to do with your error
because it's totally normal for the PATH to contain those sort of
things.  Having paths with spaces is not an issue and works fine.

Brian

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