From mboxrd@z Thu Jan 1 00:00:00 1970 From: Michael Tremer To: development@lists.ipfire.org Subject: Re: make is an addon in IPFire?? Date: Thu, 12 May 2022 10:05:21 +0100 Message-ID: <112E4673-6E03-4097-9004-8CF59CDF9A08@ipfire.org> In-Reply-To: MIME-Version: 1.0 Content-Type: multipart/mixed; boundary="===============9081234667551023651==" List-Id: --===============9081234667551023651== Content-Type: text/plain; charset="utf-8" Content-Transfer-Encoding: quoted-printable Hello, Jon is right. There is only one reason to make as a package for IPFire: So yo= u 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=E2=80=99t 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=E2=80=99s it. -Michael > On 11 May 2022, at 23:26, Adolf Belka wrote: >=20 >=20 >=20 > On 12/05/2022 00:14, Jon Murphy wrote: >> I found this reference=E2=80=A6 >> > > 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 ha= ve make on the IPFire machine. >=20 > None of the commits for the various updates for make in the git repository = refer to why it was added as an addon. >=20 > Regards, > Adolf. >> But it doesn=E2=80=99t answer the question=E2=80=A6 >>> On May 11, 2022, at 4:47 PM, Adolf Belka > wrote: >>>=20 >>> Hi All, >>>=20 >>> I just realised that make is defined in IPFire as an addon. Why would any= one need to run make on a firewall. >>>=20 >>>=20 >>> I can understand it being in the build so that packages can be compiled e= tc but why on the firewall itself? >>>=20 >>>=20 >>> Regards, >>>=20 >>> Adolf. >>>=20 --===============9081234667551023651==--