From b1d778b2303c3dcb3f70e4b29a0a9bcba72c11d6 Mon Sep 17 00:00:00 2001
From: Boris Kolpackov <boris@codesynthesis.com>
Date: Sun, 29 Nov 2015 14:31:00 +0200
Subject: Allow for target group members to remain unresolved

This, for example, can happen when we have a fallback rule for dist(update)
or configure(update).
---
 build/algorithm.cxx | 3 +--
 1 file changed, 1 insertion(+), 2 deletions(-)

(limited to 'build/algorithm.cxx')

diff --git a/build/algorithm.cxx b/build/algorithm.cxx
index fb6c72a..6c3374e 100644
--- a/build/algorithm.cxx
+++ b/build/algorithm.cxx
@@ -272,8 +272,7 @@ namespace build
     execute_direct (a, g);
 
     r = g.group_members (a);
-    assert (r.members != nullptr); // What "next step" did the group expect?
-    return r;
+    return r; // Might still be unresolved.
   }
 
   void
-- 
cgit v1.1