public inbox for development@lists.ipfire.org
 help / color / mirror / Atom feed
From: Adolf Belka <adolf.belka@ipfire.org>
To: development@lists.ipfire.org
Subject: Re: make is an addon in IPFire??
Date: Thu, 12 May 2022 00:26:44 +0200	[thread overview]
Message-ID: <dff1258e-b902-b3d7-a689-1ba7771f3749@ipfire.org> (raw)
In-Reply-To: <C661DA5F-C14F-41E8-9593-B61BAF9C2B38@gmail.com>

[-- Attachment #1: Type: text/plain, Size: 994 bytes --]



On 12/05/2022 00:14, Jon Murphy wrote:
> I found this reference…
> 
> <https://wiki.ipfire.org/devel/ipfire-2-x/build-initial#ipfire <https://wiki.ipfire.org/devel/ipfire-2-x/build-initial#ipfire>>
That is related to what you need on your build machine to be able to build the various packages that use autotools. That does not refer to needing to have make on the IPFire machine.

None of the commits for the various updates for make in the git repository refer to why it was added as an addon.

Regards,
Adolf.
> 
> But it doesn’t answer the question…
> 
> 
>> On May 11, 2022, at 4:47 PM, Adolf Belka <adolf.belka(a)ipfire.org <mailto:adolf.belka(a)ipfire.org>> wrote:
>>
>> Hi All,
>>
>> I just realised that make is defined in IPFire as an addon. Why would anyone need to run make on a firewall.
>>
>>
>> I can understand it being in the build so that packages can be compiled etc but why on the firewall itself?
>>
>>
>> Regards,
>>
>> Adolf.
>>
> 

       reply	other threads:[~2022-05-11 22:26 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <C661DA5F-C14F-41E8-9593-B61BAF9C2B38@gmail.com>
2022-05-11 22:26 ` Adolf Belka [this message]
2022-05-12  9:05   ` Michael Tremer
2022-05-11 21:47 Adolf Belka

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=dff1258e-b902-b3d7-a689-1ba7771f3749@ipfire.org \
    --to=adolf.belka@ipfire.org \
    --cc=development@lists.ipfire.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox