> From: Gururaj Bhat
> Date: Fri, 10 Jun 2011 10:18:02 +0530
>
> I am getting the below error from *gmake*.
>
> *"_main: memory allocation error during startup*"
>
> when I try to run it in my Windows 7 build environment with cygwin.
>
>
> Version of the gmake is 3.79
This is very old. I su
Hi,
I am getting the below error from *gmake*.
*"_main: memory allocation error during startup*"
when I try to run it in my Windows 7 build environment with cygwin.
Version of the gmake is 3.79
Below is the detailed version Info.
>gmake -ver
*
GNU Make version 3.79-1 (Sudhi's SpeedPatch), by
Hi,
Thanks for looking into this Eddy!
The behavior depends on the VPATH directory order
e.g.
VPATH = a b, mv a => b does not work
VPATH = a b, mv b => a works correct
VPATH = b a, mv b => a works
VPATH = b a, mv a => b does not work
To illustrate this better the script attached in the bug-repo
I got lost in your perl script, so may have missed something; but it
*looks* as if what's happening is that your .d.cmd file records the
prior path of what was $< on your previous run; so the .o file depends
on that (as well as the newly renamed file that's $<) and this is the
problem, not the fact
Hi, I came across this issue some time, had no choice but lurk into make sources and hack the
implicit rules code. I submitted a patch:
https://savannah.gnu.org/patch/?func=detailitem&item_id=7213
It can break backward compatibility on Windows/Dos/OS2 systems as Paul suggested in his comment du
Just noticed my colleague has posted the same topic over the
web-interface (subject: [bug #33499] VPATH does not work with 'Advanced
Auto-DependencyGeneration' when source file is moved into another
location).
Sorry for this spam.
-Original Message-
From: bug-make-bounces+joachim.baue
