From mboxrd@z Thu Jan  1 00:00:00 1970
From: Matthias Fischer <matthias.fischer@ipfire.org>
To: development@lists.ipfire.org
Subject: Re: Unable to build current "next" branch
Date: Sun, 11 Jul 2021 13:56:31 +0200
Message-ID: <1a307f97-c214-8546-0f91-a7639cea1b62@ipfire.org>
In-Reply-To: <42d07aa0-7536-2c41-fc49-07e147156cc4@ipfire.org>
MIME-Version: 1.0
Content-Type: multipart/mixed; boundary="===============3728529320100905080=="
List-Id: <development.lists.ipfire.org>

--===============3728529320100905080==
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,

Hi Peter,

> is anybody else unable to build current "next" branch as well?

No.

> 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.

Just tested on my Devels (i586): no seen problems downloading the
toolchain, no problems running './make.sh build' on 'next'. Right now,
its compiling 'glibc (2.33)'.

> 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... :-)

Sounds good...everyone should be allowed to take some time off! ;-)

> Thanks, and best regards,
> Peter M=C3=BCller
>=20

You're welcome, :-)
Matthias

--===============3728529320100905080==--