On Monday 20 February 2006 04:25, [EMAIL PROTECTED] wrote:
> Hi all;
>
> Please find the first release candidate for GNU make 3.81, 3.81rc1,
> available now for download from ftp://alpha.gnu.org/gnu/make:
>
> c907a044ebe7dff19f56f8dbb829cd3f
> ftp://alpha.gnu.org/gnu/make/make-3.81rc1.tar.bz2
>
On Tuesday 20 December 2005 22:39, Paul D. Smith wrote:
> %% Dan Jacobson <[EMAIL PROTECTED]> writes:
>
> dj> You guys have a new backslash-newline deal that is breaking 1000
> dj> of my scripts.
>
> dj> make
> dj> perl -pwle '\
> dj> BEGIN{print "#jidanni ~root/config auto
1? Perhaps I'd get more mileage with double-quotes? Or perhaps I
should use 'define'?
Cheers,
Steve.
On Sunday 21 August 2005 23:28, Paul D. Smith wrote:
> %% Steve James <[EMAIL PROTECTED]> writes:
>
> sj> AFAICT the behavior of line continuation escapes has cha
Hello John,
I concur: that Makefile segfaults with make 3.80. However, you may like to
know that it doesn't upset 3.81beta3 (linux and MinGW builds). I expected
this might be the case because I've been through the same experience: one
day, I added another innocuous line to my make script, and i
AFAICT the behavior of line continuation escapes has changed within
single-quoted strings. What's really confusing me is that this seems to be
deliberate.
Here's the simple example make script
all:
@echo 'line1\
line2'
Version 3.80 prints this (as I would expect):
line1line2
But Vers
> The second problem happens on all Windows 2000 systems, regardless of
> As you can see, I'm running with the MKS toolkit (v 6.2a) installed,
We had this problem too but it went away when we upgraded to 7.0. I believe
you don't want to run MKS on Win2k at less than 7.0.
Steve
