"Markus Mauhart" wrote ...
>
> during some long ago experiments with make381beta1 sources I've
> gathered some questionable code snippets, some maybe bugs, but
> didnt find the time to discuss them, now I thought better now
> than even later.
> If necessary I can file something to savannah.
> A few
> Thanks Markus.
I hope 50% of my list is worth some troubles during 381-release.
> You don't have a copy of GNU diff lying around on your Windows system do
> you?
yes, but better dont ask ... my sources last year suddenly got so much
changes that you would need 1 week to filter out the few rele
%% "Markus Mauhart" <[EMAIL PROTECTED]> writes:
mm> during some long ago experiments with make381beta1 sources I've
mm> gathered some questionable code snippets, some maybe bugs, but
mm> didnt find the time to discuss them, now I thought better now
mm> than even later.
Thanks Markus.
You
Hi,
during some long ago experiments with make381beta1 sources I've
gathered some questionable code snippets, some maybe bugs, but
didnt find the time to discuss them, now I thought better now
than even later.
If necessary I can file something to savannah.
A few others are still to be extracted f
%% "John Jenniskens" <[EMAIL PROTECTED]> writes:
jj> This occurs on platforms where malloc(0) returns 0. I've found the
jj> error on AIX and on TRU64 (dec-osf) platforms.
Just a note: the 1989 ANSI C standard (adopted as the ISO C standard in
1990) required that malloc(0) return a valid point
Hello,
Given the following very small makefile:
all:
@echo TEST Succesfull!!
make-3.80 with --no-builtin-rules fails:
/home/huminf/johnj> make --no-builtin-rules -f test.mak
make: *** virtual memory exhausted. Stop.
This occurs on platforms where malloc(0) returns 0. I've found
