Re: make signal text descriptions

[Earnie Boyd]

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 error */
#define SIGSEGV 11  /* Segmentation violation */
#define SIGTERM 15  /* Termination request */
#define SIGBREAK21  /* Control-break */
#define SIGABRT 22  /* Abnormal termination (abort) */
#define NSIG 23 /* maximum signal number + 1 */

Earnie


I noticed on this list list they talk about it being a failed exec:

http://www.cygwin.com/ml/cygwin/2003-06/msg00674.html

If it is a failed exec, could this be added to the list.. if it is 
convention on win32.

Only if you can find MSDN documentation that supports it.

My win32 build of make is compiled with BATCH_MODE_ONLY_SHELL, and it 
uses my sh.exe when in --jobs mode.  It only has this signal error every 
few days.  Unsure what is causing it. the command runs fine if I run it 
from a .bat file, or in terminal etc.

Can't tell you either and I only have one CPU.

Earnie
--
http://www.mingw.org
Powered by SourceForge 


___
Bug-make mailing list
[EMAIL PROTECTED]
http://mail.gnu.org/mailman/listinfo/bug-make

multiple wildcards in a static pattern rule

[Ram Bhamidipaty]

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 there a way to write all of these static pattern rules with one rule?



When I did a google search on this I saw that there was a patch submitted
for that back in 1997, but there is no documentation in the make manuals
that suggests that this feature has been incorporated into gnu make.

Thanks for any info?
-Ram


___
Bug-make mailing list
[EMAIL PROTECTED]
http://mail.gnu.org/mailman/listinfo/bug-make

Re: multiple wildcards in a static pattern rule

[Noel Yap]

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 should at least be close to what I think you want.

HTH,
Noel
Ram Bhamidipaty wrote:
> 
> 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 there a way to write all of these static pattern rules with one rule?
> 
> When I did a google search on this I saw that there was a patch submitted
> for that back in 1997, but there is no documentation in the make manuals
> that suggests that this feature has been incorporated into gnu make.
> 
> Thanks for any info?
> -Ram
> 
> ___
> Bug-make mailing list
> [EMAIL PROTECTED]
> http://mail.gnu.org/mailman/listinfo/bug-make

-- 
NOTICE: If received in error, please destroy and notify sender.  Sender does not waive 
confidentiality or privilege, and use is prohibited.


___
Bug-make mailing list
[EMAIL PROTECTED]
http://mail.gnu.org/mailman/listinfo/bug-make

Re: MAKECMDGOALS

[Noel Yap]

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 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 MAKECMDGOALS working? How come it always turns out to be empty.
> > >
> > >
> > -
> > > ___
> > > Help-make mailing list
> > > [EMAIL PROTECTED]
> > > http://mail.gnu.org/mailman/listinfo/help-make
> >
> >--
> >NOTICE: If received in error, please destroy and notify sender.  Sender
> >does not waive confidentiality or privilege, and use is prohibited.

-- 
NOTICE: If received in error, please destroy and notify sender.  Sender does not waive 
confidentiality or privilege, and use is prohibited.


___
Bug-make mailing list
[EMAIL PROTECTED]
http://mail.gnu.org/mailman/listinfo/bug-make

Re: MAKECMDGOALS

[Noel Yap]

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 MAKECMDGOALS working? How come it always turns out to be empty.
> 
>  
> -
> ___
> Help-make mailing list
> [EMAIL PROTECTED]
> http://mail.gnu.org/mailman/listinfo/help-make

-- 
NOTICE: If received in error, please destroy and notify sender.  Sender does not waive 
confidentiality or privilege, and use is prohibited.


___
Bug-make mailing list
[EMAIL PROTECTED]
http://mail.gnu.org/mailman/listinfo/bug-make