NetBSD Problem Report #50193

From dholland@netbsd.org  Thu Sep  3 07:34:06 2015
Return-Path: <dholland@netbsd.org>
Received: from mail.netbsd.org (mail.netbsd.org [149.20.53.66])
	(using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits))
	(Client CN "mail.netbsd.org", Issuer "Postmaster NetBSD.org" (verified OK))
	by mollari.NetBSD.org (Postfix) with ESMTPS id 54D70A57FD
	for <gnats-bugs@gnats.NetBSD.org>; Thu,  3 Sep 2015 07:34:06 +0000 (UTC)
Message-Id: <20150903073405.E011E14A1ED@mail.netbsd.org>
Date: Thu,  3 Sep 2015 07:34:05 +0000 (UTC)
From: dholland@netbsd.org
Reply-To: dholland@netbsd.org
To: gnats-bugs@gnats.NetBSD.org
Subject: convergent circular rules in make
X-Send-Pr-Version: 3.95

>Number:         50193
>Category:       bin
>Synopsis:       convergent circular rules in make
>Confidential:   no
>Severity:       non-critical
>Priority:       low
>Responsible:    bin-bug-people
>State:          open
>Class:          change-request
>Submitter-Id:   net
>Arrival-Date:   Thu Sep 03 07:35:00 +0000 2015
>Originator:     David A. Holland
>Release:        n/a
>Organization:
>Environment:
n/a
>Description:

It would be useful for some process automation tasks (and even some
build tasks) if make supported circular rules that were expected to
converge after some (fixed) number of times around.

e.g. something like

   foo: foo.c foo.h foo.gmon
           $(CC) -pg -O2 -fuse-profile-data=foo.gmon foo.c -o foo.new
	   if diff foo foo.new > /dev/null 2>&1; then mv -f foo.new foo; fi
   foo.gmon: foo
           ./foo
	   mv -f gmon.out foo.gmon
   .CONVERGE(20): foo

where you'd pick 20 or whatever based on your expectation.

This needs further refinement, and I am thinking out loud, but I
wanted to file this somewhere so it doesn't get forgotten.

>How-To-Repeat:
n/a
>Fix:
n/a

Home	PR Database Search