NetBSD Problem Report #57791

From  Thu Dec 21 01:50:37 2023
Return-Path: <>
Received: from ( [])
	(using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits))
	(Client CN "", Issuer " CA" (not verified))
	by (Postfix) with ESMTPS id 46B921A9238
	for <>; Thu, 21 Dec 2023 01:50:37 +0000 (UTC)
Message-Id: <>
Date: Thu, 21 Dec 2023 01:50:36 +0000 (UTC)
Subject: make: .ORDER vs. non-parallel makes
X-Send-Pr-Version: 3.95

>Number:         57791
>Category:       toolchain
>Synopsis:       make: .ORDER vs. non-parallel makes
>Confidential:   no
>Severity:       non-critical
>Priority:       medium
>Responsible:    toolchain-manager
>State:          open
>Class:          sw-bug
>Submitter-Id:   net
>Arrival-Date:   Thu Dec 21 01:55:01 +0000 2023
>Originator:     David A. Holland
>Release:        NetBSD 10.99.10 (20231220)
System: NetBSD valkyrie 9.99.97 NetBSD 9.99.97 (VALKYRIE) #9: Thu Jun  2 20:39:54 EDT 2022  dholland@valkyrie:/usr/src/sys/arch/amd64/compile/VALKYRIE amd64
Architecture: x86_64
Machine: amd64

Non-parallel makes ignore the .ORDER directive. This is, on the one
hand, reasonable. On the other, it means that in some cases "make" and
"make -j1" behave materially differently, and that seems undesirable.

I'm not sure what the resolution should be. I lean towards having
"make" and "make -j1" always do the same thing. Though maybe it's also
reasonable for this case to produce an error.

In any event the current behavior is not documented, and that's
definitely undesirable.


   all: foo bar
   .ORDER: bar foo
   	@echo bar
   	@echo foo

 % make
 % make -j1


Dunno, sorry, been too much change in make since I last looked at it.

NetBSD Home
NetBSD PR Database Search

(Contact us) $NetBSD: query-full-pr,v 1.47 2022/09/11 19:34:41 kim Exp $
$NetBSD:,v 1.9 2014/08/02 14:16:04 spz Exp $
Copyright © 1994-2023 The NetBSD Foundation, Inc. ALL RIGHTS RESERVED.