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 [thread overview]
Message-ID: <1a307f97-c214-8546-0f91-a7639cea1b62@ipfire.org> (raw)
In-Reply-To: <42d07aa0-7536-2c41-fc49-07e147156cc4@ipfire.org>
[-- 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
next prev parent reply other threads:[~2021-07-11 11:56 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 [this message]
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=1a307f97-c214-8546-0f91-a7639cea1b62@ipfire.org \
--to=matthias.fischer@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