public inbox for development@lists.ipfire.org
 help / color / mirror / Atom feed
From: Adolf Belka <adolf.belka@ipfire.org>
To: development@lists.ipfire.org
Subject: Re: Unable to build current "next" branch
Date: Sun, 11 Jul 2021 14:18:56 +0200	[thread overview]
Message-ID: <e2a521d9-d30a-e740-50f7-ef4c512df501@ipfire.org> (raw)
In-Reply-To: <1ac09054-f40e-a023-6254-026e537e4ed8@ipfire.org>

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

  reply	other threads:[~2021-07-11 12:18 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-07-11 11:38 Peter Müller
2021-07-11 11:40 ` Michael Tremer
2021-07-11 11:56 ` Matthias Fischer
2021-07-11 12:02 ` Matthias Fischer
2021-07-11 12:18   ` Adolf Belka [this message]
2021-07-11 13:15     ` Michael Tremer

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=e2a521d9-d30a-e740-50f7-ef4c512df501@ipfire.org \
    --to=adolf.belka@ipfire.org \
    --cc=development@lists.ipfire.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox