On 25/07/2012 16:56, Earnie Boyd wrote:
On Wed, Jul 25, 2012 at 9:50 AM, Aaron Schneider wrote:
Oh no I meant I removed the cygwin's make, the nokia's make is still
present, never removed it in the end. The makefile is in perfect condition,
even I tried it on a empty dir and the result is the s
On Wed, Jul 25, 2012 at 9:50 AM, Aaron Schneider wrote:
>
> Oh no I meant I removed the cygwin's make, the nokia's make is still
> present, never removed it in the end. The makefile is in perfect condition,
> even I tried it on a empty dir and the result is the same.
If you're not using the Cygwin
On 25/07/2012 15:34, Thrall, Bryan wrote:
guide for more details about POSIX paths:
http://cygwin.com/cygwin-ug-net/using.html#using-pathnames
Can't find C:\Program on PATH.
Could this be a problem with the Makefile? It looks like you're using
Cygwin make now, but the Makefile might b
Aaron Schneider wrote on 2012-07-24:
> So anyway, the problem is caused when calling a binary present on
> windows path that can match a cygwin one, for example running a
> ./configure script.
> After removing make the issue is happening again:
> $ make
> cygwin warning:
>MS-DOS style path d
On 07/24/2012 07:24 PM, Aaron Schneider wrote:
On 25/07/2012 3:59, Andrew DeFaria wrote:
Maybe when in Cygwin, /bin and /usr/bin should be put in your PATH ahead
of the Windows stuff. I know I've run with C:\Cygwin\bin in the front of
my Windows System Environment PATH variable for years withou
On 25/07/2012 3:59, Andrew DeFaria wrote:
Maybe when in Cygwin, /bin and /usr/bin should be put in your PATH ahead
of the Windows stuff. I know I've run with C:\Cygwin\bin in the front of
my Windows System Environment PATH variable for years without issue
(though I think some around here might s
On 7/24/2012 6:09 PM, Aaron Schneider wrote:
On 25/07/2012 2:47, Andrew DeFaria wrote:
There'd be a /bin/make if you installed it...
$ which make
/bin/make
IMHO it's always better to go with a Cygwin way of doing things instead
of installing some Unix/Linux thing through some Windows
On 25/07/2012 2:47, Andrew DeFaria wrote:
There'd be a /bin/make if you installed it...
$ which make
/bin/make
IMHO it's always better to go with a Cygwin way of doing things instead
of installing some Unix/Linux thing through some Windows port like this
Symbian\tools thing...
>
That
On 7/24/2012 1:35 PM, Aaron Schneider wrote:
On 24/07/2012 18:08, Christopher Faylor wrote:
>
You must be running a non-cygwin make.
That said, however, make does not deal well with spaces in file
specifications. If something is actually parsing a PATH environment
variable then it could cause
On 24/07/2012 18:08, Christopher Faylor wrote:
>
You must be running a non-cygwin make.
That said, however, make does not deal well with spaces in file
specifications. If something is actually parsing a PATH environment
variable then it could cause problems.
You're right, I know what caused
On Tue, Jul 24, 2012 at 05:57:40PM +0200, Aaron Schneider wrote:
>On 24/07/2012 17:50, Christopher Faylor wrote:
>>
>> The Cygwin version of make would not display "c:" anything. That's not
>> a Cygwin path specification and it shouldn't even be possible for a
>> Cygwin program to see the Windows
On 24/07/2012 17:50, Christopher Faylor wrote:
The Cygwin version of make would not display "c:" anything. That's not
a Cygwin path specification and it shouldn't even be possible for a
Cygwin program to see the Windows PATH environment variable. You must
be running a non-cygwin make. Spaces
On Tue, Jul 24, 2012 at 05:31:54PM +0200, Aaron Schneider wrote:
>Fresh install of cygwin on c:\cygwin\ is including spaces in PATH,
>causing that cannot execute common tasks,
>
>$ echo $PATH
>/usr/local/bin:/usr/bin:/cygdrive/c/Program Files (x86)/PC Connectivity
>Solution:/cygdrive/c/Program Fi
13 matches
Mail list logo
