From mboxrd@z Thu Jan  1 00:00:00 1970
From: Michael Tremer <michael.tremer@ipfire.org>
To: development@lists.ipfire.org
Subject: Re: Unable to build current "next" branch
Date: Sun, 11 Jul 2021 12:40:16 +0100
Message-ID: <7680969A-7647-4400-BD49-3C066076357C@ipfire.org>
In-Reply-To: <42d07aa0-7536-2c41-fc49-07e147156cc4@ipfire.org>
MIME-Version: 1.0
Content-Type: multipart/mixed; boundary="===============7835999538852701370=="
List-Id: <development.lists.ipfire.org>

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

Hello,

> On 11 Jul 2021, at 12:38, Peter M=C3=BCller <peter.mueller(a)ipfire.org> wr=
ote:
>=20
> 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.

Could you post more about this error?

Yes, the toolchain is now compressed using zstd. Tar should know that on any =
recent distribution.

> 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

This just says that you didn=E2=80=99t extract the toolchain successfully.

> Cleaning cache directories and the entire ipfire-2.x Git repository accompl=
ishes nothing.

Does the downloaded toolchain look like a tarball?

Best,
-Michael

>=20
> I guess this will be a lazy Sunday then... :-)
>=20
> Thanks, and best regards,
> Peter M=C3=BCller


--===============7835999538852701370==--