From owner-freebsd-hackers Sun Jun 2 19:33:21 2002 Delivered-To: freebsd-hackers@freebsd.org Received: from orthanc.ab.ca (orthanc.ab.ca [216.123.203.186]) by hub.freebsd.org (Postfix) with ESMTP id 9140937B408 for ; Sun, 2 Jun 2002 19:33:16 -0700 (PDT) Received: from orthanc.ab.ca (localhost.orthanc.ab.ca [127.0.0.1]) by orthanc.ab.ca (8.12.3/8.12.3) with ESMTP id g532X8m1012565; Sun, 2 Jun 2002 20:33:08 -0600 (MDT) (envelope-from lyndon@orthanc.ab.ca) Message-Id: <200206030233.g532X8m1012565@orthanc.ab.ca> From: Lyndon Nerenberg Organization: The Frobozz Magic Homing Pigeon Company To: jos@catnook.com Cc: Sergey Babkin , Terry Lambert , freebsd-hackers@FreeBSD.ORG Subject: Re: Improving GNU make compatibility in BSD make (+ patch) In-reply-to: Your message of "Sun, 02 Jun 2002 19:14:55 -0701." <20020603021517.GA11452@lizzy.catnook.com> X-Mailer: mh-e 5.0.92; MH 6.8.4; Emacs 21.2 Date: Sun, 02 Jun 2002 20:33:08 -0600 Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG >>>>> "Jos" == Jos Backus writes: Jos> I just checked the Open Group make definition and I can't find Jos> either $^ or $>. So if we want to be truly standards-compliant Jos> perhaps we should remove support for $> :-) We are POSIX compliant right now (I think -- I haven't done a strict comparison between (our) BSD make and POSIX). BSD does have things that aren't in POSIX, as does GNUmake. Removing the historical BSD syntax would just break things, so I wouldn't advocate that. We can depricate the BSD extensions if that seems useful. That's not the same as adding new incompatible extensions to make (ours, GNUs, or anyone elses). Writing portable makefiles is already enough of a pain in the ass. --lyndon (death to feeping creaturism!) (And yes, I would really miss the BSD/GNU if/then/else makefile constructs if we went POSIX-anal on this.) To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message