Hi Lorenzo,
I've changed C: to /c/ everywhere except the PATH.
[ but it didn't fix the sed problem. ]
The sed you should use is the one inside msys which is in c:\msys
\1.0\bin.
Mixing msys and non-msys tools is the main source of problems.
msys is a posix env and it means the c:\bin\harbour.exe is read like
c:binharbour.exe.
If you want the right path you need to enter c:\\bin\\harbour.exe or
better /bin/harbour.exe
This is what I use, at least almost, since I don't know
of any place where I should specify the location of harbour.exe,
the dir specs I'm using are fully /c/bin/... formatted (can't
use /bin, not wanting to trash in the root).
I have tried to reverse my PATH to first include msys, and
mingw afterwards. This blew the whole build process, creating
an infinite loop, an unstoppable chain of sh.exe crashes
and launches, and an unusable system, with no way to pull up
Task Manager. I managed to kill make/sh by issuing a pskill
for both at the same time (killing about 1500 instances of them).
(so don't anybody try this at home.)
Finally I simply copied over sed.exe from msys to mingw dir,
and this way it worked without the error. Thanks for the tip.
[ I wonder however how these tools are meant to be used properly,
if even a 'sed' cannot work consistently along different builds,
not to mention the rest of the mess. I also wonder if there is
any clean method achieve the above effect. ]
Brgds,
Viktor
_______________________________________________
Harbour mailing list
Harbour@harbour-project.org
http://lists.harbour-project.org/mailman/listinfo/harbour
