From mboxrd@z Thu Jan 1 00:00:00 1970 From: Adolf Belka To: development@lists.ipfire.org Subject: Re: Problem with ipfire build system Date: Mon, 09 Dec 2024 13:43:14 +0100 Message-ID: In-Reply-To: <39CF8BB8-B6D7-47BF-9502-979184DEF43A@ipfire.org> MIME-Version: 1.0 Content-Type: multipart/mixed; boundary="===============6692031404043602590==" List-Id: --===============6692031404043602590== Content-Type: text/plain; charset="utf-8" Content-Transfer-Encoding: quoted-printable Hi Michael, On 09/12/2024 12:48, Michael Tremer wrote: > Hello Adolf, >=20 >> On 8 Dec 2024, at 12:04, Adolf Belka wrote: >> >> Hi Michael, >> >> I have experienced a problem yesterday and today with the IPFire build sys= tem. Not a major problem but it only seems to have started recently. >> >> Today when I tried to run the build command with the standard IPFire-2.x g= it clone I got the following error message. >> >> ./make.sh build >> >> ERROR: Not enough temporary space available, need at least 8192MiB, but on= ly have 491 [ FAIL ] >> Check /home/ahb/sandbox/ipfire-2.x/log_x86_64/_build.preparation.log = for errors if applicable [ FAIL ] >=20 > So, there is a check that will ensure that there is 8 GiB available for the= build directory so that (ideally) the build does not abort because of low di= sk space. >=20 > This is however a little bit of a gamble because we don=E2=80=99t always kn= ow exactly how much (temporary) space the build environment might need and it= is a little bit difficult if a build is being restarted (because we might ha= ve consumed a chunk of the 8 GiB already). >=20 > Could you send me the output of =E2=80=9Cdf -h=E2=80=9D and =E2=80=9Cdu -cs= h build_x86_64=E2=80=9D when this problem happens? I managed to get the same problem to occur. Then running df -h told me where = my problem was and it is self made. My home directory, where the git repo's are in is nearly full. With one repo = with a full build directory I only had 4.9G left (99% full) not enough space = for the 8G. When I cleaned the other build directory then my home directory had 14G avail= able (97% full) and so enough space for the 8G. So I don't currently have enough space for both of the git repos to be gettin= g built. I will need to search out what is using up the space as normally most things = are on my file server, which includes most of my vm definitions. I will need = to figure out what has filled up the space over time and either get rid of it= or move it elsewhere. Sorry for the noise. Regards, Adolf. >=20 >> I was able to overcome it by running the ./make.sh clean command on the op= envpn-2.6-meetup-rebased branch git repo that I also have on my system. >> >> After running the clean command the normal ipfire-2.x git repo build comma= nd is working fine and no longer gives the above message. >=20 > It sounds like the calculation works well when there is no build directory.= That is the easy case. >=20 >> 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 ab= ove 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 t= he build. Just doing a reboot on my desktop machine that has the git repo's o= n it made no difference. >=20 > Hmm, is it possible that the build environment has gone so large that 8 GiB= is exceeded and my calculation goes into negative numbers? That might break = things hard. >=20 >> I have not had this problem in the past. Although not a major problem, I h= ave definitely run a build on one repo when the other still had its build res= ults in place so something has changed. Maybe something in Arch Linux with on= e of the recent updates I ran. >=20 > It shouldn=E2=80=99t. This code was changed when we introduced the containe= rised build system earlier this year. So I am quite confident that I broke th= is myself. >=20 > Best, > -Michael >=20 >> Regards, >> >> Adolf. >> >> >=20 --===============6692031404043602590==--