From mboxrd@z Thu Jan 1 00:00:00 1970 From: Matthias Fischer To: development@lists.ipfire.org Subject: Re: Unable to build current "next" branch Date: Sun, 11 Jul 2021 14:02:45 +0200 Message-ID: <1ac09054-f40e-a023-6254-026e537e4ed8@ipfire.org> In-Reply-To: <42d07aa0-7536-2c41-fc49-07e147156cc4@ipfire.org> MIME-Version: 1.0 Content-Type: multipart/mixed; boundary="===============2890780938933296380==" List-Id: --===============2890780938933296380== Content-Type: text/plain; charset="utf-8" Content-Transfer-Encoding: quoted-printable On 11.07.2021 13:38, Peter M=C3=BCller wrote: > Hello development folks, >=20 > is anybody else unable to build current "next" branch as well? >=20 > On my workstation, ./make.sh build requires a toolchain to be present (unle= ss memories fail > me, I thought it was possible to compile IPFire 2.x without a toolchain). A= fter having executed > ./make.sh gettoolchain, tar complains about the downloaded toolchain not lo= oking like a tar > archive - presumably because the toolchain archive uses zstd now, and tar d= oes not recognise > this format. FYI: Downloaded toolchain (5.Jul 13:51) is: 883b1a6d0825c046fd8f8a2aa6e42ffa cache/toolchains/ipfire-2.25-toolchain-20210701-i586.tar.zst > In addition, some issues around chroot and env arise here as well: >=20 >> Jul 11 11:33:07: Building stage2 chroot: failed to run command 'env': No s= uch file or directory >=20 > Cleaning cache directories and the entire ipfire-2.x Git repository accompl= ishes nothing. >=20 > I guess this will be a lazy Sunday then... :-) >=20 > Thanks, and best regards, > Peter M=C3=BCller >=20 --===============2890780938933296380==--