Follow-up Comment #2, bug #63638 (project make):
Thank you very much for your quick response, Paul. Good to know that you can
reproduce this behavior.
I'll switch back to 4.3 for now. Thanks again for your time,
Best regards
___
Reply
Follow-up Comment #7, bug #63638 (project make):
Where did you download the Make binaries?
Do you have a MinGW development environment installed (GCC, Binutils, header
files) that allow you to compile C programs?
___
Reply to this item
Follow-up Comment #9, bug #63638 (project make):
OK, then it should be easy for you to build Make by yourself.
First, download the Make sources from here:
https://ftp.gnu.org/gnu/make/make-4.4.tar.gz
Unpack it (you will need tar.exe or bsdtar.exe). This will create a directory
make-4.4
Follow-up Comment #8, bug #63638 (project make):
I downloaded the Make binaries through MSYS2 with:
pacman -S mingw-w64-x86_64-make
Yes, I have a MinGW development environment installed and I can compile C
programs.
___
Reply to this
Follow-up Comment #4, bug #63638 (project make):
Ah, I see. I spent about 30m last night trying to find this but since I don't
really do Windows development I was reduced to printf debugging and couldn't
come up with it before I had to go to dinner :).
That was my fault breaking this. That
Follow-up Comment #6, bug #63638 (project make):
Eli, Paul, thanks a lot for finding the cause of the problem so quickly!
I am just an end user of make, though, and to be quite honest I don't know how
to apply your patch, rebuild make, and test my real-life Makefile.
(I'm really sorry about
Follow-up Comment #5, bug #63638 (project make):
(AFAIK, printf debugging is the only way in this case, since GDB on MS-Windows
cannot follow-exec, and we are re-exec-ing ourselves. My only advantage was
that I knew up from where to put the printf...)
I didn't know about the CSTRLEN macro. I
Follow-up Comment #3, bug #63638 (project make):
It is a subtle feature of the native Windows port of GNU Make that it attempts
to support PATH variables delimited by colons and semi-colons alike. It does
that by converting colon delimiters to semi-colons. Which is a bit tricky,
given the drive
Follow-up Comment #11, bug #63638 (project make):
You definitely should but you'll have to do more debugging, ideally giving a
repro case as you did for the PATH issue. It may be challenging: our
regression tests for output-sync are not failing so I don't think the problem
is obvious.
We did
Follow-up Comment #10, bug #63638 (project make):
Indeed, I followed your instructions and I can confirm that the PATH bug is
now gone. Thank you kindly.
However, as you suspected, my real application still does not build
successfully...
It seems to be an unrelated problem, though. My parallel
10 matches
Mail list logo
