%% "J. Grant" <[EMAIL PROTECTED]> writes:
>> All of these are not going to be easy to fix. The code is actually
>> created that way for a reason, IIRC.
jg> It will be a little difficult to work out what the code is that is
jg> compiled, as there seems to be (traditionally) excessive use
%% Claudio Fontana <[EMAIL PROTECTED]> writes:
cf> I have written a Makefile (.am, but this is a Make
cf> issue), containing:
cf> --
cf> description:
cf> description-long:
cf> .SILENT: description description-long
cf> --
cf> on th
Hello,
I have written a Makefile (.am, but this is a Make
issue), containing:
--
description:
@echo "a short description here containing
@PACKAGE_VERSION@ and other stuff available only at
maketime (like $(DESTDIR))"
description-long:
@echo "a multiline"
Hi Paul,
[...]
jg> If I submit fixes for these would they be reviewed for inclusion ?
I'm happy to look at them, but they will not be easy to fix.
I'm happy to assist if needed. I hope the 3.81 release can have as few
warnings as possible.
jg> main.c:420: warning: missing initializer
Could (void)batch_filename_ptr; be added in this job.c to stop this
compile warning please? (or a different solution to stop the warning)
batch_filename_ptr
job.c: In function `construct_command_argv_internal':
job.c:2155: warning: unused parameter `batch_filename_ptr'
I just rebuilt with late
%% "J. Grant" <[EMAIL PROTECTED]> writes:
jg> If I submit fixes for these would they be reviewed for inclusion ?
I'm happy to look at them, but they will not be easy to fix.
jg> main.c:420: warning: missing initializer
jg> main.c:420: warning: (near initialization for `switches[30].type')