> From: Paul Smith
> Cc: make-...@gnu.org, bug-make@gnu.org
> Date: Mon, 16 Jan 2012 18:01:02 -0500
>
> > NMakefile is for building the MS-Windows port with nmake, the
> > Microsoft's make program. Given that build_w32.bat exists, we could
> > remove it (and the same goes for the make_msvc_* fil
Follow-up Comment #2, bug #35063 (project make):
According to RFC 1738 (http://www.ietf.org/rfc/rfc1738.txt):
... octets may be encoded by a character triplet consisting of the character
"%" followed by the two hexadecimal digits (from "0123456789ABCDEF") which
forming the hexadecimal value of th
Follow-up Comment #7, bug #34530 (project make):
After some discussion recently by the GNU maintainers, the coding standards
have been modified:
http://www.gnu.org/prep/standards/html_node/Quote-Characters.html
In the C locale, the output of GNU programs should stick to plain ASCII for
quotatio
On Mon, 2012-01-16 at 06:59 -0500, Eli Zaretskii wrote:
> > From: Paul Smith
> > 1. Standard configure/Makefile.am
> > 2. build.sh
> > 3. Makefile.DOS
> > 4. NMakefile
> > 5. SMakefile
> > 6. build_w32.bat
> > 7. Makefile.ami
> > 8. makefile.vms
> > 9.
Update of bug #34818 (project make):
Status:None => Fixed
Assigned to:None => psmith
Open/Closed:Open => Closed
Component Version:
Update of bug #35063 (project make):
Triage Status:None => Medium Effort
___
Follow-up Comment #1:
A useful idea. FMI:
http://en.wikipedia.org/wiki/Percent-encoding
Note we already have a $% vari
2012/1/16 Paul Smith :
> 2. Unclear what to do about newlines. The code doesn't add any but
> getting a newline into a make variable is tricky.
Is it possible https://savannah.gnu.org/bugs/?35063 would help here? I
think it's a simple, robust, helpful extension (but I would).
> '>>' :
On Mon, 2012-01-16 at 13:26 +, Tim Murphy wrote:
> There might be some question about how the variable "$(FILE)" would
> look if you tried to iterate over its contents. e.g. would one see an
> iteration for each word and with "\n"s marking lines or is each line
> an "atom" for want of a better
I think that looks ok.
There might be some question about how the variable "$(FILE)" would
look if you tried to iterate over its contents. e.g. would one see an
iteration for each word and with "\n"s marking lines or is each line
an "atom" for want of a better word.
Regards,
Tim
2012/1/16 Paul
On Thu, 2011-12-15 at 15:13 -0800, Lawrence Ibarria wrote:
> This is a rather simple path that implements a very simplified version
> of what Tim suggested in his message of Sept 25th
> (https://lists.gnu.org/archive/html/bug-make/2011-09/msg00044.html ).
>
> Paul, what do you think? I’d rather no
> From: Paul Smith
> Date: Sun, 15 Jan 2012 17:53:25 -0500
> Reply-To: psm...@gnu.org
>
> Going through the content of GNU make sources recently it occurs to me
> we have a LOT of ways to build GNU make. Maybe at one time or another
> all these different ways were necessary but I wonder if they
11 matches
Mail list logo
