From nobody Thu Apr 25 18:52:40 2024 X-Original-To: freebsd-questions@mlmmj.nyi.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mlmmj.nyi.freebsd.org (Postfix) with ESMTP id 4VQQ3L0kddz5JKFL for ; Thu, 25 Apr 2024 18:53:02 +0000 (UTC) (envelope-from gray@nxg.name) Received: from mx1.mythic-beasts.com (mx1.mythic-beasts.com [IPv6:2a00:1098:0:86:1000:0:2:1]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange ECDHE (P-256) server-signature RSA-PSS (4096 bits) server-digest SHA256) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id 4VQQ3K5jB2z4c1v for ; Thu, 25 Apr 2024 18:53:01 +0000 (UTC) (envelope-from gray@nxg.name) Authentication-Results: mx1.freebsd.org; none Received: by mailhub-cam-d.mythic-beasts.com with esmtpsa (TLS1.2) tls TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384 (Exim 4.94.2) (envelope-from ) id 1s04DL-004uqP-BN; Thu, 25 Apr 2024 19:52:59 +0100 From: Norman Gray To: Tomek CEDRO Cc: FreeBSD Questions Mailing List Subject: Re: bsd sed / make vs bsd sed / make Date: Thu, 25 Apr 2024 19:52:40 +0100 X-Mailer: MailMate (1.14r5964) Message-ID: <3DBC8F99-C32B-4AEE-9EB4-99F4CA54DD27@nxg.name> In-Reply-To: References: List-Id: User questions List-Archive: https://lists.freebsd.org/archives/freebsd-questions List-Help: List-Post: List-Subscribe: List-Unsubscribe: X-BeenThere: freebsd-questions@freebsd.org Sender: owner-freebsd-questions@FreeBSD.org MIME-Version: 1.0 Content-Type: text/plain Content-Transfer-Encoding: quoted-printable X-BlackCat-Spam-Score: 24 X-Spam-Status: No, score=2.4 X-Spamd-Bar: ---- X-Rspamd-Pre-Result: action=no action; module=replies; Message is reply to one we originated X-Spamd-Result: default: False [-4.00 / 15.00]; REPLY(-4.00)[]; ASN(0.00)[asn:44684, ipnet:2a00:1098::/32, country:GB] X-Rspamd-Queue-Id: 4VQQ3K5jB2z4c1v Tomek, hello. On 25 Apr 2024, at 18:36, Tomek CEDRO wrote: > Is there an elegant way to > use BSD make here with no dramatic code modification? As Souji says, this is not easy in general. Resorting to galling gmake f= rom make wouldn't be pretty, but might be necessary. The core of GNU Make and pmake/bmake (ie, the FreeBSD version) are the sa= me, and it's not too hard to write a basic Makefile which will work with = both implementations. But as soon as you step beyond that core -- ie, as= soon as you need a non-basic Makefile -- the two go in different directi= ons, and are almost immediately thoroughly incompatible with each other. Best wishes, Norman -- = Norman Gray : https://nxg.me.uk