From owner-freebsd-hackers Thu Nov 12 14:35:49 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id OAA02424 for freebsd-hackers-outgoing; Thu, 12 Nov 1998 14:35:49 -0800 (PST) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from detlev.UUCP (132.camalott.com [208.203.140.132]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id OAA02415 for ; Thu, 12 Nov 1998 14:35:43 -0800 (PST) (envelope-from joelh@gnu.org) Received: (from joelh@localhost) by detlev.UUCP (8.9.1/8.9.1) id QAA21363; Thu, 12 Nov 1998 16:35:15 -0600 (CST) (envelope-from joelh) To: David Holland Cc: kline@tao.thought.org, hackers@FreeBSD.ORG Subject: Re: bsd make to gnu make conversion, anyone?? References: <98Nov12.141220edt.37768-2936@qew.cs.toronto.edu> From: Joel Ray Holveck Date: 12 Nov 1998 16:35:14 -0600 In-Reply-To: David Holland's message of "Thu, 12 Nov 1998 14:12:14 -0500" Message-ID: <863e7or13x.fsf@detlev.UUCP> Lines: 38 X-Mailer: Gnus v5.5/Emacs 20.3 Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > eww. > I didn't know this would work. As Gary later pointed out, it doesn't. As I said, it was just a guess. The hangup is that pattern substitutions cannot introduce multiple targets. I suspect that breaking the Makefile into targets is done before variable substitution, but I don't know. >> What's wrong with using sh like God intended? > Two reasons; one that issuing complex shell commands makes make -n > output less useful (for an extreme case of this, try make -n install > in gnu binutils), I am aware of that, but in this simple case, it's perfectly fine. > and the other that when you do loops in the shell they don't always > terminate on error like you (usually) want. I guess a little extra sh code could fix that at the expense of prettiness. > For install this may not be that significant, but when you're doing > recursion into subdirectories it sucketh. Hard. Quite. Requirements for cross-compatibility across Linux, BSD, and Win32 have brought several of my compile procedures to tears. (In case you're wondering, most Win32 compilers parse #include "..." differently. It's an ambiguity about what is considered the "current directory".) Happy hacking, joelh -- Joel Ray Holveck - joelh@gnu.org Fourth law of programming: Anything that can go wrong wi sendmail: segmentation violation - core dumped To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message