#38378 closed enhancement (invalid)
Using port's -d flag should pass --disable-silent-rules to configure.args when applicable
| Reported by: | cooljeanius (Eric Gallager) | Owned by: | macports-tickets@… |
|---|---|---|---|
| Priority: | Normal | Milestone: | |
| Component: | base | Version: | 2.1.3 |
| Keywords: | Cc: | ryandesign (Ryan Carsten Schmidt) | |
| Port: |
Description
The -d flag implies that the user wants additional information, and passing --disable-silent-rules to most configure scripts usually makes the make process print additional information. Of course we'd probably want to test this first so we don't end up with something like the situation with how qmake doesn't recognize the --disable-dependency-tracking flag.
Change History (5)
comment:1 follow-up: 2 Changed 12 years ago by ryandesign (Ryan Carsten Schmidt)
| Cc: | ryandesign@… added |
|---|---|
| Resolution: | → invalid |
| Status: | new → closed |
comment:2 Changed 12 years ago by larryv (Lawrence Velázquez)
Furthermore, this behavior would cause a Heisenberg-esque scenario in which main.log changes depending on whether it was observed during its creation.
comment:3 follow-ups: 4 5 Changed 12 years ago by cooljeanius (Eric Gallager)
File bugs for individual ports. We've already done this in many ports.
Are there tickets I could look at that have been filed in the past for individual ports that you've already done this for?
comment:4 Changed 12 years ago by larryv (Lawrence Velázquez)
Replying to egall@…:
Are there tickets I could look at that have been filed in the past for individual ports that you've already done this for?
I don’t think anyone’s ever filed a ticket about it, but there are currently 88 portfiles containing --disable-silent-rules.
port file all | sort -u | xargs grep -le --disable-silent-rules
comment:5 Changed 12 years ago by ryandesign (Ryan Carsten Schmidt)
Replying to egall@…:
File bugs for individual ports. We've already done this in many ports.
Are there tickets I could look at that have been filed in the past for individual ports that you've already done this for?
I meant: we've already added configure.args --disable-silent-rules or equivalent (like build.args V=1) to many ports to solve this problem. 44 portfiles matching V=1:
port file all | sort -u | xargs grep -Ele '[[:space:]]V=1'
The cmake portgroup does this automatically also.
One ticket that's still open is #38234.
Nah. MacPorts can't know what ports would support that option and what ports would complain. All ports that support --disable-silent-rules should use it unconditionally. File bugs for individual ports. We've already done this in many ports.