make-w32
[Top][All Lists]
Advanced

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: GNU make 3.81beta4 released


From: Eli Zaretskii
Subject: Re: GNU make 3.81beta4 released
Date: Sat, 17 Dec 2005 15:36:15 +0200

> Date: Tue, 13 Dec 2005 10:27:13 -0500
> From: address@hidden
> 
> Please find GNU make 3.18beta4, available now for download from
> ftp://alpha.gnu.org/gnu/make:
> 
> 0db7ce037088bb32548de7153225c95c  
> ftp://alpha.gnu.org/gnu/make/make-3.81beta4.tar.gz
> 8bd2a61eef5e98feaf36fa5f95b7aa8a  
> ftp://alpha.gnu.org/gnu/make/make-3.81beta4.tar.bz2

I successfully built the MinGW port of this pretest.  Suggested minor
changes are below, most of them to shut up compiler warnings.  Also
fixed several minor problems in the manual.

2005-12-17  Eli Zaretskii  <address@hidden>

        * main.c (handle_runtime_exceptions): Cast exrec->ExceptionAddress
        to DWORD, to avoid compiler warnings.

        * job.c (exec_command): Cast hWaitPID and hPID to DWORD, and
        use %ld in format, to avoid compiler warnings.

        * doc/make.texi (Special Targets): Fix a typo.
        (Appending): Fix cross-reference to Setting.
        (Special Variables, Secondary Expansion, File Name Functions)
        (Flavor Function, Pattern Match, Quick Reference): Ensure two
        periods after a sentence.
        (Execution): Add @: after "e.g.".
        (Environment): Fix punctuation.
        (Target-specific, Call Function, Quick Reference): Add @: after "etc."
        (Shell Function, Target-specific): Add @: after "vs."


--- main.c~0    2005-10-24 17:01:39.000000000 +0200
+++ main.c      2005-12-17 14:31:39.375000000 +0200
@@ -668,7 +668,7 @@ handle_runtime_exceptions( struct _EXCEP
     {
       sprintf(errmsg,
               _("%s: Interrupt/Exception caught (code = 0x%lx, addr = 
0x%lx)\n"),
-              prg, exrec->ExceptionCode, exrec->ExceptionAddress);
+              prg, exrec->ExceptionCode, (DWORD)exrec->ExceptionAddress);
       fprintf(stderr, errmsg);
       exit(255);
     }
@@ -676,7 +676,7 @@ handle_runtime_exceptions( struct _EXCEP
   sprintf(errmsg,
           _("\nUnhandled exception filter called from program 
%s\nExceptionCode = %lx\nExceptionFlags = %lx\nExceptionAddress = %lx\n"),
           prg, exrec->ExceptionCode, exrec->ExceptionFlags,
-          exrec->ExceptionAddress);
+          (DWORD)exrec->ExceptionAddress);
 
   if (exrec->ExceptionCode == EXCEPTION_ACCESS_VIOLATION
       && exrec->NumberParameters >= 2)

--- job.c~0     2005-09-26 11:16:31.000000000 +0300
+++ job.c       2005-12-17 14:34:20.796875000 +0200
@@ -2027,8 +2027,8 @@ exec_command (char **argv, char **envp)
           break;
       else
           fprintf(stderr,
-                  _("make reaped child pid %d, still waiting for pid %d\n"),
-                  hWaitPID, hPID);
+                  _("make reaped child pid %ld, still waiting for pid %ld\n"),
+                  (DWORD)hWaitPID, (DWORD)hPID);
     }
 
   /* return child's exit code as our exit code */

--- doc/make.texi~0     2005-11-17 11:27:28.000000000 +0200
+++ doc/make.texi       2005-12-17 15:27:50.234375000 +0200
@@ -1290,7 +1290,7 @@
 command line (@pxref{Goals, , Arguments to Specify the Goals}).  The
 @code{.DEFAULT_GOAL} variable allows you to discover the current
 default goal, restart the default goal selection algorithm by clearing
-its value, or to explicitly set the default goal. The following
+its value, or to explicitly set the default goal.  The following
 example illustrates these cases:
 
 @example
@@ -1738,7 +1738,7 @@
 rule for this target.  @code{$$^} and @code{$$+} evaluate to the list
 of all prerequisites of rules @emph{that have already appeared} for
 the same target (@code{$$+} with repetitions and @code{$$^}
-without). The following example will help illustrate these behaviors:
+without).  The following example will help illustrate these behaviors:
 
 @example
 .SECONDEXPANSION:
@@ -1751,9 +1751,9 @@
 @end example
 
 For the first line, all three variables (@code{$$<}, @code{$$^}, and
address@hidden) expand to the empty string. For the second line, they will
address@hidden) expand to the empty string.  For the second line, they will
 have values @code{foo.1}, @code{foo.1 bar.1}, and @code{foo.1 bar.1}
-respectively. For the third they will have values @code{foo.1},
+respectively.  For the third they will have values @code{foo.1},
 @code{foo.1 bar.1 foo.2 bar.2}, and @code{foo.1 bar.1 foo.2 bar.2}
 respectively.
 
@@ -2907,7 +2907,7 @@
 @findex .SECONDEXPANSION
 @item .SECONDEXPANSION
 
-If @code{.SECONDEXPANSION} is mentioned as a target anwyeren in the
+If @code{.SECONDEXPANSION} is mentioned as a target anywhere in the
 makefile, then all prerequisite lists defined @emph{after} it appears
 will be expanded a second time after all makefiles have been read in.
 @xref{Secondary Expansion, ,Secondary Expansion}.
@@ -3587,7 +3587,7 @@
 @cindex @code{cd} (shell command)
 @strong{Please note:} this implies that shell commands such as @code{cd}
 that set variables local to each process will not affect the following
-command lines. @footnote{On MS-DOS, the value of current working
+command address@hidden MS-DOS, the value of current working
 directory is @strong{global}, so changing it @emph{will} affect the
 following command lines on those systems.}  If you want to use @code{cd}
 to affect the next command, put the two on a single line with a
@@ -3719,7 +3719,7 @@
 
 The effect of the above DOS-specific processing is that a Makefile that
 says @samp{SHELL = /bin/sh} (as many Unix makefiles do), will work
-on MS-DOS unaltered if you have e.g. @file{sh.exe} installed in some
+on MS-DOS unaltered if you have e.g.@: @file{sh.exe} installed in some
 directory along your @code{PATH}.
 
 @cindex environment, @code{SHELL} in
@@ -5287,7 +5287,7 @@
 making it a simply-expanded variable, @samp{+=} adds to that
 simply-expanded definition, and expands the new text before appending it
 to the old value just as @samp{:=} does
-(@pxref{Setting, ,Setting Variables} for a full explanation of @samp{:=}).
+(see @ref{Setting, ,Setting Variables}, for a full explanation of @samp{:=}).
 In fact,
 
 @example
@@ -5528,7 +5528,7 @@
 
 When @code{make} runs a command script, variables defined in the
 makefile are placed into the environment of that command.  This allows
-you to pass values to address@hidden invocations. (@pxref{Recursion,
+you to pass values to address@hidden invocations (@pxref{Recursion,
 ,Recursive Use of @code{make}}).  By default, only variables that came
 from the environment or the command line are passed to recursive
 invocations.  You can use the @code{export} directive to pass other
@@ -5605,7 +5605,7 @@
 target: thus, any previously-defined target-specific variable values
 will be in effect.  Note that this variable is actually distinct from
 any ``global'' value: the two variables do not have to have the same
-flavor (recursive vs. static).
+flavor (recursive vs.@: static).
 
 Target-specific variables have the same priority as any other makefile
 variable.  Variables provided on the command-line (and in the
@@ -5616,7 +5616,7 @@
 There is one more special feature of target-specific variables: when
 you define a target-specific variable that variable value is also in
 effect for all prerequisites of this target, and all their
-prerequisites, etc. (unless those prerequisites override that variable
+prerequisites, etc.@: (unless those prerequisites override that variable
 with their own target-specific variable value).  So, for example, a
 statement like this:
 
@@ -6596,8 +6596,8 @@
 @cindex file name, realpath of
 For each file name in @var{names} return the canonical absolute name.
 A canonical name does not contain any @code{.} or @code{..} components,
-nor any repeated path separators (@code{/}) or symlinks. In case of a
-failure the empty string is returned. Consult the @code{realpath(3)}
+nor any repeated path separators (@code{/}) or symlinks.  In case of a
+failure the empty string is returned.  Consult the @code{realpath(3)}
 documentation for a list of possible failure causes.
 
 @item $(abspath @address@hidden)
@@ -6606,9 +6606,9 @@
 @cindex file name, abspath of
 For each file name in @var{names} return an absolute name that does
 not contain any @code{.} or @code{..} components, nor any repeated path
-separators (@code{/}). Note that in contrast to @code{realpath}
+separators (@code{/}).  Note that, in contrast to @code{realpath}
 function, @code{abspath} does not resolve symlinks and does not require
-the file names to refer to an existing file or directory. Use the
+the file names to refer to an existing file or directory.  Use the
 @code{wildcard} function to test for existence.
 @end table
 
@@ -6804,7 +6804,7 @@
 Now the variable LS contains @code{/bin/ls} or similar.
 
 The @code{call} function can be nested.  Each recursive invocation gets
-its own local values for @code{$(1)}, etc. that mask the values of
+its own local values for @code{$(1)}, etc.@: that mask the values of
 higher-level @code{call}.  For example, here is an implementation of a
 @dfn{map} function:
 
@@ -7058,7 +7058,7 @@
 
 The @code{flavor} function is unlike most other functions (and like
 @code{origin} function) in that it does not operate on the values of
-variables; it tells you something @emph{about} a variable. Specifically,
+variables; it tells you something @emph{about} a variable.  Specifically,
 it tells you the flavor of a variable
 (@pxref{Flavors, ,The Two Flavors of Variables}).
 
@@ -7117,7 +7117,7 @@
 @code{make} Reads a Makefile}).  Because this function involves
 spawning a new shell, you should carefully consider the performance
 implications of using the @code{shell} function within recursively
-expanded variables vs. simply expanded variables (@pxref{Flavors, ,The
+expanded variables vs.@: simply expanded variables (@pxref{Flavors, ,The
 Two Flavors of Variables}).
 
 Here are some examples of the use of the @code{shell} function:
@@ -9119,7 +9119,7 @@
 comparison of the file name to the target pattern, the directory
 names, along with the slash that ends them, are added on to the
 prerequisite file names generated from the pattern rule's prerequisite
-patterns and the file name. The directories are ignored only for the
+patterns and the file name.  The directories are ignored only for the
 purpose of finding an implicit rule to use, not in the application of
 that rule.  Thus, @samp{e%t} matches the file name @file{src/eat},
 with @samp{src/a} as the stem.  When prerequisites are turned into file
@@ -10276,7 +10276,7 @@
 @item $(call @var{var},@var{param},@dots{})
 
 Evaluate the variable @var{var} replacing any references to @code{$(1)},
address@hidden(2)} with the first, second, etc. @var{param} address@hidden
address@hidden(2)} with the first, second, etc.@: @var{param} address@hidden
 @xref{Call Function, ,The @code{call} Function}.
 
 @item $(eval @var{text})
@@ -10376,7 +10376,7 @@
 @item MAKESHELL
 
 On MS-DOS only, the name of the command interpreter that is to be used
-by @code{make}. This value takes precedence over the value of
+by @code{make}.  This value takes precedence over the value of
 @code{SHELL}.  @xref{Execution, ,MAKESHELL variable}.
 
 @item MAKE


2005-12-17  Eli Zaretskii  <address@hidden>

        * glob.c (my_realloc) [WINDOWS32]: Provide a different declaration
        of arguments, to avoid compiler warnings.


--- glob/glob.c~0       2005-06-26 05:00:17.000000000 +0300
+++ glob/glob.c 2005-12-17 14:38:50.859375000 +0200
@@ -188,12 +188,13 @@ __inline
 # ifndef __SASC
 #  ifdef WINDOWS32
 static void *
+my_realloc (void *p, unsigned int n)
 #  else
 static char *
-# endif
 my_realloc (p, n)
      char *p;
      unsigned int n;
+# endif
 {
   /* These casts are the for sake of the broken Ultrix compiler,
      which warns of illegal pointer combinations otherwise.  */




reply via email to

[Prev in Thread] Current Thread [Next in Thread]