J. Grant wrote:
Hi Earnie,
ok, I wonder if win32 has extra signals, this code 127, could these
be supported for win32 ports?
#define SIGINT 2 /* Interactive attention */
#define SIGILL 4 /* Illegal instruction */
#define SIGFPE 8 /* Floating point err
I have a series of rules like this in my Makefile:
$(ROOT)etc/dir1/%: $(ROOT)etc/dir1/%: %
cp $< $@
chmod 644 $@
$(ROOT)etc/dir2/%: $(ROOT)etc/dir2/%: %
cp $< $@
chmod 644 $@
...
$(ROOT)etc/dirN/%: $(ROOT)etc/dirN/%: %
cp $< $@
chmod 644 $@
Is th
I'm not sure about your syntax. I think you might mean:
$(ROOT)etc/dir1/%: %
cp $< $@
chmod 644 $@
and so on.
Anyway the way I'd go about this would be:
$(foreach d,etc/dir1 etc/dir2 etc/dirN,$(eval $(ROOT)$(d)/%: % ; cp $< $@ && chmod
644 $@))
I haven't tested it, but it s
According to the NEWS file that comes with the source, MAKECMDGOALS was added in 3.76.
HTH,
Noel
Andy Xiao wrote:
>
> I am executing gmake (verion 3.74) with a target: "gmake xxx", I am
> expecting the MAKECMDGOALS containing xxx.
>
> At 05:20 PM 10/30/2003 -0500, Noel Yap wrote:
> >Are you ex
Are you executing gmake with a target (eg "gmake all") or relying on the "first rule
hit" behaviour (eg "gmake")? If the former, what does "gmake -npqr all 2>&1 | grep
MAKECMDGOALS" give? If the latter, I think MAKECMDGOALS is supposed to be empty.
HTH,
Noel
Andy Xiao wrote:
>
> Is MAKECMDGO
