Unable to build current "next" branch

Unable to build current "next" branch

[Peter Müller]

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

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.

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

Re: Unable to build current "next" branch

[Michael Tremer]

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

Hello,

> On 11 Jul 2021, at 12:38, Peter Müller <peter.mueller(a)ipfire.org> 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.

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:
> 
>> Jul 11 11:33:07: Building stage2 chroot: failed to run command 'env': No such file or directory

This just says that you didn’t extract the toolchain successfully.

> Cleaning cache directories and the entire ipfire-2.x Git repository accomplishes nothing.

Does the downloaded toolchain look like a tarball?

Best,
-Michael

> 
> I guess this will be a lazy Sunday then... :-)
> 
> Thanks, and best regards,
> Peter Müller

Re: Unable to build current "next" branch

[Matthias Fischer]

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

On 11.07.2021 13:38, Peter Müller 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 (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.

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

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

> Thanks, and best regards,
> Peter Müller
> 

You're welcome, :-)
Matthias

Re: Unable to build current "next" branch

[Matthias Fischer]

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

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
> 

Re: Unable to build current "next" branch

[Adolf Belka]

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

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

Re: Unable to build current "next" branch

[Michael Tremer]

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