Re: Unable to build current "next" branch

[Michael Tremer <michael.tremer@ipfire.org>]

[-- Attachment #1: Type: text/plain, Size: 1840 bytes --]

Hey,

I installed SuSE Leap. That distribution seems to be the last surviving dinosaur shipping tar 1.30 from 2017 which does not recognise Zstandard.

This patch helps: https://lists.ipfire.org/pipermail/development/2021-July/010774.html

-Michael

> On 11 Jul 2021, at 13:18, Adolf Belka <adolf.belka(a)ipfire.org> wrote:
> 
> Hi Peter,
> 
> Sorry but that makes three not having a problem. I successfully downloaded the new toolchain a day or so ago and then did a build for the last set of patches 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üller 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 (unless 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 looking 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 accomplishes nothing.
>>> 
>>> I guess this will be a lazy Sunday then... :-)
>>> 
>>> Thanks, and best regards,
>>> Peter Müller
>>>