Date: Fri, 31 May 2002 01:38:17 -0700 From: Terry Lambert <tlambert2@mindspring.com> To: jos@catnook.com Cc: freebsd-hackers@freebsd.org Subject: Re: Improving GNU make compatibility in BSD make (+ patch) Message-ID: <3CF73679.A5AB7886@mindspring.com> References: <20020531024250.GA90997@lizzy.catnook.com>
next in thread | previous in thread | raw e-mail | index | archive | help
Jos Backus wrote: > So BSD make interpreting either `$^' or `$+' as its own `$>' would improve > compatibility with GNU make Makefiles. I am just not sure which of the two GNU > make variables maps better to our `$>'. This patch implements the former: The biggest problem with GNU make that I've seen is re-expansion of variable variables. The suggested fix doesn't address that, so it won't fix the most common "compatability problem". If we are going to evolve make into gmake (not a good idea, IMO), then probably the place to start is "any port that requires gmake" to get it working under "make". I'm not sure, but I believe the other BSD's, and "OpenPorts" have modified "make" syntax somewhat. It's probably a good idea to keep compatability with options in the "OpenPorts" camp, more than any other, if it ever evolves to fulfill its potential properly. I really hate that many autoconf/automake scripts generate code that can ony be run by gmake, and sometimes also requires that /bin/sh actually be "bash" instead of "sh". It also occurs to me (from experience with "perl"), that in any language where it's posible to do something in more than one way, it is then impossible to differentiate "the right way" from "the wrong way". 8-(. -- Terry To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?3CF73679.A5AB7886>