From: Pavel Fedin p.fe...@samsung.com
Date: Mon, 05 Aug 2013 09:19:18 +0400
IMHO it's a little bit inconvenient that you have to use config.cache trick
in order to build a fully working Make for Cygwin, and this is not
documented anywhere. First time, when i didn't know about this, i've
[Reply-to set to bug-make]
On Mon, Aug 05, 2013 at 09:19:18AM +0400, Pavel Fedin wrote:
Hello!
Right. Because I knew I could just turn if off for the Cygwin release.
There is no reason to nuke the feature for people who want to roll
their own version of make with DOS paths turned on.
Then
On Mon, 2013-08-05 at 10:56 -0400, Christopher Faylor wrote:
Then maybe really add something like --enable-dos-paths which
defaults to
no on Cygwin and Yes on MinGW ?
ac_cv_dos_paths=no configure
works just fine and does not require a command-line switch.
If this is a common/necessary
Hello! I have found and fixed the problem. It appeared to be PATH issue.
fork()-based code temporary sets 'environ' variable to child's environment,
which appears to contain current directory. EMX code didn't do that.
The problem gets triggered only if you try to call something which is not
Hello, Eli.
Monday, August 5, 2013, 18:44:17 you wrote:
I don't yet understand why you have a problem in the first place. It
sounds like the single issue is with the 'abspath' function, is that
correct?
Yes, correct.
2 Christopher Faylor:
ac_cv_dos_paths=no configure
works just fine
Date: Mon, 5 Aug 2013 21:34:31 +0400
From: Pavel Fedin pavel_fe...@mail.ru
fork()-based code temporary sets 'environ' variable to child's environment,
which appears to contain current directory. EMX code didn't do that.
The problem gets triggered only if you try to call something which
Date: Mon, 5 Aug 2013 22:04:44 +0400
From: Pavel Fedin pavel_fe...@mail.ru
CC: m...@cgf.cx, bug-make@gnu.org
I don't yet understand why you have a problem in the first place. It
sounds like the single issue is with the 'abspath' function, is that
correct?
Yes, correct.
In that
