Date: Mon, 27 Jan 2014 05:17:47 -0700 (MST) From: Warren Block <wblock@wonkity.com> To: Alexey Dokuchaev <danfe@FreeBSD.org> Cc: doc@freebsd.org, Pietro Cerutti <gahr@FreeBSD.org> Subject: Re: [patch] PH tells crap about GMAKE (Was: Re: svn commit: r340018 - head/textproc/scew) Message-ID: <alpine.BSF.2.00.1401270514480.36906@wonkity.com> In-Reply-To: <20140127085527.GA84465@FreeBSD.org> References: <201401170910.s0H9Aw9O087448@svn.freebsd.org> <20140117093546.GA16656@FreeBSD.org> <20140117095020.GD4006@gahrfit.gahr.ch> <20140117141440.GA94157@FreeBSD.org> <alpine.BSF.2.00.1401240922210.87046@wonkity.com> <alpine.BSF.2.00.1401251735370.2111@wonkity.com> <20140127085527.GA84465@FreeBSD.org>
next in thread | previous in thread | raw e-mail | index | archive | help
On Mon, 27 Jan 2014, Alexey Dokuchaev wrote:
> On Sat, Jan 25, 2014 at 05:38:11PM -0700, Warren Block wrote:
>> I would like to be more specific in this part:
>>
>> Quite often, a specific implementation is required, like GNU make, or
>> legacy FreeBSD make.
>>
>> I think that should say:
>>
>> Quite often, a specific implementation is required, like GNU make
>> (gmake), or legacy FreeBSD make (fmake).
>>
>> Is that correct?
>
> For FreeBSD, technically yes, it is correct; however, in GNU/Linux distros
> GNU make is installed just as "make" (no `g' prefix). That said, if you
> want to be even more accurate, you could say:
>
> Quite often, a specific implementation is required, like GNU make
> (known in &os; as <command>gmake</command>), or legacy &os; make
> (<command>fmake</command>).
Okay, final version of that paragraph:
<para>Several differing <literal>make</literal>
implementations exist. Ported software often requires a
particular implementation, like <acronym>GNU</acronym>
<command>make</command>, known in &os; as
<command>gmake</command>, or <command>fmake</command>, the
legacy &os; <command>make</command>.</para>
One last question, and I'll commit this. The last sentence in this
paragraph:
<para><varname>MAKE_CMD</varname> can be used to reference the
specific command configured by the <literal>USES</literal>
setting in the port's <filename>Makefile</filename>. In
rare cases where several different <literal>make</literal>
implementations are listed in <literal>USES</literal>, the
variables <varname>GMAKE</varname> (for the
<acronym>GNU</acronym> version) or <varname>FMAKE</varname>
(for the legacy &os; version) are available. Most ports
should only use <varname>MAKE_CMD</varname> within their
own <filename>Makefile</filename>s to call the
<command>make</command> implementation expected by the
ported software.</para>
It's not really clear what the last sentence is trying to say. Is it
saying that I might need to modify application Makefiles with MAKE_CMD?
Is it a warning that using MAKE_CMD in the port Makefile is probably a
mistake?
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?alpine.BSF.2.00.1401270514480.36906>