From mboxrd@z Thu Jan 1 00:00:00 1970 From: Adolf Belka To: development@lists.ipfire.org Subject: Re: Unable to build current "next" branch Date: Sun, 11 Jul 2021 14:18:56 +0200 Message-ID: In-Reply-To: <1ac09054-f40e-a023-6254-026e537e4ed8@ipfire.org> MIME-Version: 1.0 Content-Type: multipart/mixed; boundary="===============2861050796277170312==" List-Id: --===============2861050796277170312== Content-Type: text/plain; charset="utf-8" Content-Transfer-Encoding: quoted-printable Hi Peter, Sorry but that makes three not having a problem. I successfully downloaded th= e new toolchain a day or so ago and then did a build for the last set of patc= hes I submitted. Just did a clean build start on next now and it is now at building glibc with= no problems. Regards, Adolf. On 11/07/2021 14:02, Matthias Fischer wrote: > On 11.07.2021 13:38, Peter M=C3=BCller wrote: >> Hello development folks, >> >> is anybody else unable to build current "next" branch as well? >> >> On my workstation, ./make.sh build requires a toolchain to be present (unl= ess memories fail >> me, I thought it was possible to compile IPFire 2.x without a toolchain). = After having executed >> ./make.sh gettoolchain, tar complains about the downloaded toolchain not l= ooking like a tar >> archive - presumably because the toolchain archive uses zstd now, and tar = does 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: >> >>> Jul 11 11:33:07: Building stage2 chroot: failed to run command 'env': No = such file or directory >> Cleaning cache directories and the entire ipfire-2.x Git repository accomp= lishes nothing. >> >> I guess this will be a lazy Sunday then... :-) >> >> Thanks, and best regards, >> Peter M=C3=BCller >> --===============2861050796277170312==--