[bug #61042] Enhance implicit rule search logging

Follow-up Comment #2, bug #61042 (project make): sv_61042_reuse_rule_name_for_dash_p.diff reuses rule->name for printing the db under -p. ___ Reply to this item at:

[bug #61042] Enhance implicit rule search logging

Additional Item Attachment, bug #61042 (project make): File name: sv_61042_reuse_rule_name_for_dash_p.diff Size:0 KB ___ Reply to this item

[bug #61042] Enhance implicit rule search logging

Follow-up Comment #1, bug #61042 (project make): sv_61042_implicit_rule_search_logging.diff has the following Changes in the implicit rule search logging: 1. The messages which refer to a rule print the first line (the targets and prerequisites) of the rule. 2. A new message tells when a

[bug #61042] Enhance implicit rule search logging

Additional Item Attachment, bug #61042 (project make): File name: sv_61042_implicit_rule_search_logging.diff Size:13 KB ___ Reply to this

[bug #61042] Enhance implicit rule search logging

URL: Summary: Enhance implicit rule search logging Project: make Submitted by: dgoncharov Submitted on: Sun 15 Aug 2021 04:11:25 AM UTC Severity: 3 - Normal Item Group:

Re: Parallel job instance identifiers?

Hi, I'm afraid there's a lot to consider. > That would require starting up a server first, and somehow getting it to report its port# to us. > But the server configs must know port#s in advance because they need to talk to each other. Bootstrapping from leaf servers up the dependency tree should

Re: Parallel job instance identifiers?

Christian Hujer wrote: > Hi, > > Have you considered using port 0 instead to tap into the ephemeral port range > and communicate that port somehow? That would require starting up a server first, and somehow getting it to report its port# to us. But the server configs must know port#s in