From mboxrd@z Thu Jan  1 00:00:00 1970
From: Michael Tremer <michael.tremer@ipfire.org>
To: development@lists.ipfire.org
Subject: Re: Problem with ipfire build system
Date: Mon, 09 Dec 2024 11:48:26 +0000
Message-ID: <39CF8BB8-B6D7-47BF-9502-979184DEF43A@ipfire.org>
In-Reply-To: <cc83dc26-a3d5-470b-9327-a00ca28ff232@ipfire.org>
MIME-Version: 1.0
Content-Type: multipart/mixed; boundary="===============6194834816269582950=="
List-Id: <development.lists.ipfire.org>

--===============6194834816269582950==
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: quoted-printable

Hello Adolf,

> On 8 Dec 2024, at 12:04, Adolf Belka <adolf.belka(a)ipfire.org> wrote:
>=20
> Hi Michael,
>=20
> I have experienced a problem yesterday and today with the IPFire build syst=
em. Not a major problem but it only seems to have started recently.
>=20
> Today when I tried to run the build command with the standard IPFire-2.x gi=
t clone I got the following error message.
>=20
> ./make.sh build
>=20
> ERROR: Not enough temporary space available, need at least 8192MiB, but onl=
y have 491 [ FAIL ]
>     Check /home/ahb/sandbox/ipfire-2.x/log_x86_64/_build.preparation.log fo=
r errors if applicable [ FAIL ]

So, there is a check that will ensure that there is 8 GiB available for the b=
uild directory so that (ideally) the build does not abort because of low disk=
 space.

This is however a little bit of a gamble because we don=E2=80=99t always know=
 exactly how much (temporary) space the build environment might need and it i=
s a little bit difficult if a build is being restarted (because we might have=
 consumed a chunk of the 8 GiB already).

Could you send me the output of =E2=80=9Cdf -h=E2=80=9D and =E2=80=9Cdu -csh =
build_x86_64=E2=80=9D when this problem happens?

> I was able to overcome it by running the ./make.sh clean command on the ope=
nvpn-2.6-meetup-rebased branch git repo that I also have on my system.
>=20
> After running the clean command the normal ipfire-2.x git repo build comman=
d is working fine and no longer gives the above message.

It sounds like the calculation works well when there is no build directory. T=
hat is the easy case.

> Yesterday it was the other way around. I tried to run the build command on =
the openvpn-2.6-meetup-rebased branch and got the same sort of message as abo=
ve just the amount available was a bit different. Something like 670 instead =
of 491 today. Yesterday, when I ran the clean command on my normal ipfire-2.x=
 git repo then the openvpn-2.6-meetup-rebased git repo had no problem with th=
e build. Just doing a reboot on my desktop machine that has the git repo's on=
 it made no difference.

Hmm, is it possible that the build environment has gone so large that 8 GiB i=
s exceeded and my calculation goes into negative numbers? That might break th=
ings hard.

> I have not had this problem in the past. Although not a major problem, I ha=
ve definitely run a build on one repo when the other still had its build resu=
lts in place so something has changed. Maybe something in Arch Linux with one=
 of the recent updates I ran.

It shouldn=E2=80=99t. This code was changed when we introduced the containeri=
sed build system earlier this year. So I am quite confident that I broke this=
 myself.

Best,
-Michael

> Regards,
>=20
> Adolf.
>=20
>=20


--===============6194834816269582950==--