[bug #65600] `--silent` option should also silence `$(info ...)`

2024-04-20 Thread Gökçe
Follow-up Comment #8, bug #65600 (group make): [comment #7 comment #7:] > You can check the build system of the Linux man-pages, which I wrote in the last few years, if you're interested. It's quite complex, though, so it may be scary. :) > >

[bug #65600] `--silent` option should also silence `$(info ...)`

2024-04-20 Thread Gökçe
Follow-up Comment #6, bug #65600 (group make): I could not find a button to close this enhancement request. I assume I don't have any privileges. Feel free to close this item. ___ Reply to this item at:

[bug #65600] `--silent` option should also silence `$(info ...)`

2024-04-20 Thread Gökçe
Follow-up Comment #5, bug #65600 (group make): [comment #4 comment #4:] > Hmmm, I still disagree, because $(info) is a replacement for echo(1). In fact, I use .SILENCE to not show any commands, and then $(info) shows pretty versions of them (e.g., CC file.o, instead of cc -Wall -Wextra ... -c -

[bug #65600] `--silent` option should also silence `$(info ...)`

2024-04-19 Thread Gökçe
Follow-up Comment #3, bug #65600 (group make): [comment #2 comment #2:] > No. --silent (and .SILENT) don't silence the output of any command. Where did you get that from? > No. `@` is to not print the command before executing it. For silencing the command, you'd need to >/dev/null I made a m

[bug #65600] `--silent` option should also silence `$(info ...)`

2024-04-16 Thread Gökçe
Follow-up Comment #1, bug #65600 (group make): [comment #0 original submission:] > I propose that `--silence`... I actually meant `--silent`. ___ Reply to this item at: _

[bug #65600] `--silent` option should also silence `$(info ...)`

2024-04-16 Thread Gökçe
Triage Status: None ___ Follow-up Comments: --- Date: Tue 16 Apr 2024 10:14:04 AM UTC By: Gökçe Currently `--silent` option only silences the output of the executed commands. Some users o

Enhancement request on documentation for 'Multiple Targets in a Rule'

2015-12-25 Thread Gökçe Aydos
a is to clearly differentiate pattern rules and change the title of 4.10 to 'Multiple Targets in a _Normal_ Rule'. What do you think? Kind Regards, Gökçe ___ Bug-make mailing list Bug-make@gnu.org https://lists.gnu.org/mailman/listinfo/bug-make

[bug #38442] Field 'name' not cached

2013-05-22 Thread Gökçe
Follow-up Comment #4, bug #38442 (project make): Unfortunately still the same error: $ touch foo.vhd $ make-3.99.90/make cd module_timestamps && touch foo && ar rv lib foo && rm foo ar: creating lib a - foo $ make-3.99.90/make make: Nothing to be done for 'default'. make: module_timestamps/lib(fo

[bug #38442] Field 'name' not cached

2013-02-28 Thread Gökçe
Follow-up Comment #1, bug #38442 (project make): I want to add that the Make 3.81 doesn't have this warning. ___ Reply to this item at: ___ Message sent

[bug #38442] Field 'name' not cached

2013-02-28 Thread Gökçe
URL: Summary: Field 'name' not cached Project: make Submitted by: karaheart Submitted on: Thu 28 Feb 2013 01:46:55 PM GMT Severity: 3 - Normal Item Group: Bug