You have been selected to receive this exclusive invitation. We promise that this
email will be well worth your time to read.
We are creating the world's largest organized group of Credit Card Members by offering
a Free Credit Card with unprecedented benefits and we are paying out Millions of
Just to be completely clear, you're talking about the VMS code, right?
In my current version of variable.c, these lines are different.
Thx.
--
---
Paul D. Smith <[EMAIL PROTECTED]> Find some GNU make tips at:
I found another problem in variable.c for GNU Make 3.79.1.
Line 222-234 replace $ signs in variable values with double $$. The problem
is, the result is not null-terminated before being passed to define_variable
on line 236. This can be fixed by inserting the line:
*nptr = '\0';
immediately p
%% jacques klein <[EMAIL PROTECTED]> writes:
jk> Is there a reason why make returns always with an exitcode of 0, even
jk> when an error occured ?.
It doesn't. See the GNU make manual for a description of the exit code
values, or try it:
$ echo 'all: ; false' | make -f-
false
make: *
Is there a reason why make returns always with an exitcode of 0, even
when an error occured ?.
In a shell script, or make calling make, what is the `good' way to check
for errors ?.
Thank's for any reply.
___
Bug-make mailing list
[EMAIL PROTECTED]
h
Please can you tell me who is the current maintainer of the make utility
(3.79.1) ?
I would like to send him some questions about all the changes since
3.77.
Well, why not asking here
I hacked the make version 3.77 in order to be able to extend the builtin
functions with new functions, main
Not only do you get to build your own business,
you get the chance to try all natural products at
Wholesale prices. True Potential, the Power of Women!
I was stuck working outside the home, away from my children and
husband. Now I work at home, earn the same income, get to see
my children grow
