public inbox for development@lists.ipfire.org
 help / color / mirror / Atom feed
From: jon <jon.murphy@ipfire.org>
To: development@lists.ipfire.org
Subject: Toolchain errors during make build
Date: Tue, 14 Feb 2023 15:43:15 -0600	[thread overview]
Message-ID: <71B94B85-D8A2-4220-885C-E1484554FFAD@ipfire.org> (raw)

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

All,

I started with a new `git clone git://git.ipfire.org/ipfire-2.x.git`.  And I keep getting toolchain errors during the make build.  

I seem to remember a recent change to the toolchain.  And the errors are related to a newer date toolchain build that I do not have.

This is what I see:
```
Packaged toolchain compilation                                                                                                                                                        
b2sum: /home/Jon/development/ipfire-2.x/cache/toolchains/ipfire-2.27-toolchain-20230210-x86_64.tar.zst: No such file or directory
cat: /home/jon/development/ipfire-2.x/cache/toolchains/ipfire-2.27-toolchain-20230210-x86_64.b2: No such file or directory
./make.sh: line 1827: /home/jon/development/ipfire-2.x/cache/toolchains/ipfire-2.27-toolchain-20230210-x86_64.tar.zst: No such file or directory
tar: This does not look like a tar archive
tar: Exiting with failure status due to previous errors
Checking for necessary space on disk                                                    [ DONE ]
chroot: failed to run command 'env': No such file or directory
Building LFS
```                                                                                                                                                                          

The toolchain files I have are
```
ipfire-2.27-toolchain-20220808-x86_64.b2
ipfire-2.27-toolchain-20220808-x86_64.tar.zst
```

Does this make sense?
Jon



Jon Murphy
jon.murphy(a)ipfire.org




             reply	other threads:[~2023-02-14 21:43 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-02-14 21:43 jon [this message]
2023-02-15  8:36 ` Adolf Belka
     [not found] <493D748F-99D0-42C8-B92A-488E1EAA1562@ipfire.org>
2023-02-16  9:13 ` 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=71B94B85-D8A2-4220-885C-E1484554FFAD@ipfire.org \
    --to=jon.murphy@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