From: Adolf Belka <adolf.belka@ipfire.org>
To: development@lists.ipfire.org
Subject: Problem with ipfire build system
Date: Sun, 08 Dec 2024 13:04:10 +0100 [thread overview]
Message-ID: <cc83dc26-a3d5-470b-9327-a00ca28ff232@ipfire.org> (raw)
[-- Attachment #1: Type: text/plain, Size: 1570 bytes --]
Hi Michael,
I have experienced a problem yesterday and today with the IPFire build system. 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 git clone I got the following error message.
./make.sh build
ERROR: Not enough temporary space available, need at least 8192MiB, but only have 491 [ FAIL ]
Check /home/ahb/sandbox/ipfire-2.x/log_x86_64/_build.preparation.log for errors if applicable [ FAIL ]
I was able to overcome it by running the ./make.sh clean command on the openvpn-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 command is working fine and no longer gives the above message.
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 above 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 the build. Just doing a reboot on my desktop machine that has the git repo's on it made no difference.
I have not had this problem in the past. Although not a major problem, I have definitely run a build on one repo when the other still had its build results in place so something has changed. Maybe something in Arch Linux with one of the recent updates I ran.
Regards,
Adolf.
next reply other threads:[~2024-12-08 12:04 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-12-08 12:04 Adolf Belka [this message]
2024-12-09 11:48 ` Michael Tremer
2024-12-09 12:43 ` Adolf Belka
2024-12-09 13:39 ` 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=cc83dc26-a3d5-470b-9327-a00ca28ff232@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