Hello,

Jon is right. There is only one reason to make as a package for IPFire: So you can compile IPFire on itself.

Our build system only has very few requirements to run: Bash, wget & make.

If you want to build the toolchain, it requires some more things, but 99% of people won’t do that.

Otherwise make is normally not too useful without a compiler, but we use make for downloading the sources linked in the LFS files.

That’s it.

-Michael

On 11 May 2022, at 23:26, Adolf Belka adolf.belka@ipfire.org wrote:

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@ipfire.org mailto:adolf.belka@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.