bug#32868: Acknowledgement (Check if make supports nested variables is done twice when using silent rules)

2018-09-28 Thread GNU bug Tracking System
Thank you for filing a new bug report with debbugs.gnu.org.

This is an automatically generated reply to let you know your message
has been received.

Your message is being forwarded to the package maintainers and other
interested parties for their attention; they will reply in due course.

Your message has been sent to the package maintainer(s):
 bug-automake@gnu.org

If you wish to submit further information on this problem, please
send it to 32...@debbugs.gnu.org.

Please do not send mail to help-debb...@gnu.org unless you wish
to report a problem with the Bug-tracking system.

-- 
32868: http://debbugs.gnu.org/cgi/bugreport.cgi?bug=32868
GNU Bug Tracking System
Contact help-debb...@gnu.org with problems



bug#48188: Acknowledgement (Manual: Multiple outputs)

2021-05-03 Thread GNU bug Tracking System
Thank you for filing a new bug report with debbugs.gnu.org.

This is an automatically generated reply to let you know your message
has been received.

Your message is being forwarded to the package maintainers and other
interested parties for their attention; they will reply in due course.

Your message has been sent to the package maintainer(s):
 bug-automake@gnu.org

If you wish to submit further information on this problem, please
send it to 48...@debbugs.gnu.org.

Please do not send mail to help-debb...@gnu.org unless you wish
to report a problem with the Bug-tracking system.

-- 
48188: http://debbugs.gnu.org/cgi/bugreport.cgi?bug=48188
GNU Bug Tracking System
Contact help-debb...@gnu.org with problems



bug#48188: closed (Re: bug#48188: Manual: Multiple outputs)

2021-11-04 Thread GNU bug Tracking System
Your bug report

#48188: Manual: Multiple outputs

which was filed against the automake package, has been closed.

The explanation is attached below, along with your original report.
If you require more details, please reply to 48...@debbugs.gnu.org.

-- 
48188: http://debbugs.gnu.org/cgi/bugreport.cgi?bug=48188
GNU Bug Tracking System
Contact help-debb...@gnu.org with problems
--- Begin Message ---
Getting back to this automake doc report from May ...

> > 
https://www.gnu.org/software/automake/manual/html_node/Multiple-Outputs.html ) 
...
fh> > More importantly (at least to me), the final paragraph of the page
fh> > should really be first. 

I agree. Moved.

ps> This example is wrong.  You need the data.h target to have a recipe

Thanks. Deleted incorrect example.

Closing bug. --thanks, karl.

P.S. I wish there was a clean (non-gmake-only) solution for multiple
outputs that did actually meet all the desiderata. So far as I can
tell from reading that page, there isn't.

--- End Message ---
--- Begin Message ---
I had accidentally posted to bug-m...@gnu.org first, but this
belongs to bug-automake@gnu.org.

Paul Smith wrote:

> On Mon, 2021-05-03 at 12:55 +0200, Frank Heckenbach wrote:
> > The manual (
> > https://www.gnu.org/software/automake/manual/html_node/Multiple-Outputs.html
> >  ) 
> > describes various ways to handle commands with multiple outputs.
> 
> Just to remind, this is the mailing list for GNU make... the above
> manual is for automake which is a different project; we have no input
> into or control over their manual.  You should be emailing their list.

Oops! I see that now. I had googled for "gnu make multiple outputs"
and got that page, and since it described make features without any
reference to automake, I didn't notice where I was. (And the last
paragraph links to the GNU make manual which is formatted exactly
the same, to add to the confusion.)

> > One intermediate solution that's said to work except with phony
> > dependencies doesn't actually seem to work:
> > 
> > % cat Makefile
> > all: data.c data.h
> > data.c data.h: data.foo
> > touch data.c data.h
> > data.h: data.c
> > 
> > % rm -f data.[ch]; touch data.foo; make -j
> > touch data.c data.h
> > touch data.c data.h
> > 
> > It says "[...] therefore a parallel make will have to serialize the
> > builds of data.c and data.h, and will detect that the second is no
> > longer needed once the first is over." This doesn't seem to be so.
> > 
> > Am I missing something?
> 
> This example is wrong.  You need the data.h target to have a recipe
> associated with it; it could be rewritten as:
> 
>   data.h: data.c ;
> 
> (note the extra semicolon).  Now it will work.

This gives me this error:

Makefile:4: warning: overriding recipe for target 'data.h'
Makefile:3: warning: ignoring old recipe for target 'data.h'

It goes away if I take out data.h in the first rule (not sure what
other consequences this might have).

This suggestion still stands (to the automake manual maintainers):

> > More importantly (at least to me), the final paragraph of the page
> > should really be first. After reading about increasingly more
> > complex solutions to handle various corner cases, I found it *much*
> > easier to just turn my rule into a pseudo-pattern rule a la:
> > 
> > %ata.c %ata.h: %ata.foo
>
> Of course, this can't work if there's no common stem between the
> targets.

Yes. I'd prefer if "%" could match the empty string ...

(Anyway, I'd rather rename my files to create a common stem than go
through the contortions in the final example. ;)

> It also requires GNU make, which is a restriction that not
> all automake projects may be willing to accept.

Indeed, the manual page says so.

> In newer versions of GNU make there's a "grouped targets" feature which
> allows explicit rules to behave like implicit rules WRT multiple
> targets.

With emphasis on newer! 4.2.1 (my current default) accepts "&:",
but still runs the recipe twice. Only 4.3 seems to work correctly.

> But again, this is only helpful for automake projects which
> are willing to require a new-enough version of GNU make.

Or non-automake projects which require GNU make, such as mine.


--- End Message ---


bug#32868: closed (Re: bug#32868: [PATCH v2] m4: rework silent-rules macros to avoid double expansion)

2022-02-28 Thread GNU bug Tracking System
Your bug report

#32868: Check if make supports nested variables is done twice when using silent 
rules

which was filed against the automake package, has been closed.

The explanation is attached below, along with your original report.
If you require more details, please reply to 32...@debbugs.gnu.org.

-- 
32868: http://debbugs.gnu.org/cgi/bugreport.cgi?bug=32868
GNU Bug Tracking System
Contact help-debb...@gnu.org with problems
--- Begin Message ---
On 28 Feb 2022 15:58, Karl Berry wrote:
> Fixes automake bug https://bugs.gnu.org/32868.
> 
> Looks fine to me.
> 
> +./configure -C
> +grep '^AM_DEFAULT_VERBOSITY = 1' Makefile
> 
> Good :).
> 
> I remain steadfastly opposed to (ever) changing the default to be silent
> rules, as we've already discussed ad nauseam :).

we shall see :p
-mike


signature.asc
Description: PGP signature
--- End Message ---
--- Begin Message ---

On 9/28/18 1:47 PM, Jacob Kroon wrote:

Hi,

If I use AM_SILENT_RULES([yes]) in my configure.ac, when I run the
configure scripts I see this:
...
checking whether make supports nested variables... yes
checking whether make supports nested variables... (cached) yes
...

If I remove AM_SILENT_RULES, the test is only done once.

Is this intended behaviour ?


I don't know. But AM_SILENT_RULES is supplied by automake, not autoconf, 
so it's better to ask your question on the correct list.  I've gone 
ahead and updated the CC's accordingly.




I'm on an updated Debian Stretch system using (Debian version syntax):
autoconf 2.69-10
automake 1:1.15-6

Regards Jacob




--
Eric Blake, Principal Software Engineer
Red Hat, Inc.   +1-919-301-3266
Virtualization:  qemu.org | libvirt.org


--- End Message ---