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 [thread overview]
Message-ID: <7680969A-7647-4400-BD49-3C066076357C@ipfire.org> (raw)
In-Reply-To: <42d07aa0-7536-2c41-fc49-07e147156cc4@ipfire.org>
[-- 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
next prev parent reply other threads:[~2021-07-11 11:40 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 [this message]
2021-07-11 11:56 ` Matthias Fischer
2021-07-11 12:02 ` Matthias Fischer
2021-07-11 12:18 ` Adolf Belka
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=7680969A-7647-4400-BD49-3C066076357C@ipfire.org \
--to=michael.tremer@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