On 8/10/19 8:16 AM, anonymous wrote:
> Follow-up Comment #3, bug #56732 (project make):
>
> OK, this is a special case I didn't remembered. The wording in the manual
> doesn't touch implicit rules, so one can assume it should work for them too.
>
> I don't know how much application of rules diffe
pendency is a coding error in the Makefile's by
the build-engineer, and I don't want it to slide by...
Thanks,
jzb
On 5/11/24 06:11, Dmitry Goncharov wrote:
On Wed, May 8, 2024 at 2:04 PM JZB wrote:
... perhaps a command line option or a ".CIRCULARERROR:" rule
or some way to allow this to be turned on by those who need it?
There is currently no mechanism (option or otherwise) to fail on
On 5/13/24 21:05, Dmitry Goncharov wrote:
On Wed, May 8, 2024 at 2:04 PM JZB wrote:
I have a GNU make-based build system wherein I would like for any/all
GNU make-detected circular dependencies to be treated as a hard error,
i.e., fail [immediately], rather than a "dropped and we
On 5/19/24 18:25, Paul D. Smith wrote:
Follow-up Comment #6, bug #60736 (group make):
I think that using a warn option is better than forcing this to always warn.
But I still think that the warning makes global usage useless, and since
there's no way to control warnings on a per-target basis (to
