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@ipfire.org
Hi Jon,
On 14/02/2023 22:43, jon wrote:
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.
A new toolchain was released. You need to run ./make gettoolchain
As standard when I do a new build I run ./make gettoolchain ./make downloadsrc ./make clean ./make build
The gettoolchain most of the time comes back with " latest toolchain already downloaded" but occasionally, like a couple of days ago, it downloaded and checked the b2 sum of a new toolchain.
I think for a new clone you definitely need to do the whole set of commands.
Regards,
Adolf.
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 LFSThe toolchain files I have are
ipfire-2.27-toolchain-20220808-x86_64.b2 ipfire-2.27-toolchain-20220808-x86_64.tar.zstDoes this make sense? Jon
Jon Murphy jon.murphy@ipfire.org
sorry I should have been more specific. I did all of those steps.
I started over again and I’ll see if the same happens.
Jon
On Feb 15, 2023, at 2:36 AM, Adolf Belka adolf.belka@ipfire.org wrote:
Hi Jon,
On 14/02/2023 22:43, jon wrote:
All,
I started with a new `git clone git://git.ipfire.org/ipfire-2.x.git` git://git.ipfire.org/ipfire-2.x.git%60. 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.
A new toolchain was released. You need to run ./make gettoolchain
As standard when I do a new build I run ./make gettoolchain ./make downloadsrc ./make clean ./make build
The gettoolchain most of the time comes back with " latest toolchain already downloaded" but occasionally, like a couple of days ago, it downloaded and checked the b2 sum of a new toolchain.
I think for a new clone you definitely need to do the whole set of commands.
Regards,
Adolf.
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 LFSThe toolchain files I have are
ipfire-2.27-toolchain-20220808-x86_64.b2 ipfire-2.27-toolchain-20220808-x86_64.tar.zstDoes this make sense? Jon
Jon Murphy jon.murphy@ipfire.org
-- Sent from my laptop
I just did:
git clone git://git.ipfire.org/ipfire-2.x.git sudo ./make.sh downloadsrc sudo ./make.sh gettoolchain sudo ./make.sh build
I did this build just to make sure things worked (and all was OK).
But, after the first build I still have the old toolchains.
jon@deb11HPZ:~/develoment/ipfire-2.x$ ll cache/toolchains total 97872 drwxr-xr-x 2 root root 4096 2023-02-14 15:24 . drwxr-xr-x 3 root root 32768 2023-02-15 15:00 .. -rw-r--r-- 1 root root 193 2022-08-11 04:14 ipfire-2.27-toolchain-20220808-x86_64.b2 -rw-r--r-- 1 root root 100174269 2022-08-11 04:14 ipfire-2.27-toolchain-20220808-x86_64.tar.zst
Then I did a second `sudo ./make.sh gettoolchain` and now I see:
jon@deb11HPZ:~/develoment/ipfire-2.x$ ll cache/toolchains total 192648 drwxr-xr-x 2 root root 4096 2023-02-15 15:05 . drwxr-xr-x 3 root root 32768 2023-02-15 15:00 .. -rw-r--r-- 1 root root 193 2022-08-11 04:14 ipfire-2.27-toolchain-20220808-x86_64.b2 -rw-r--r-- 1 root root 100174269 2022-08-11 04:14 ipfire-2.27-toolchain-20220808-x86_64.tar.zst -rw-r--r-- 1 root root 193 2023-02-10 09:07 ipfire-2.27-toolchain-20230210-x86_64.b2 -rw-r--r-- 1 root root 97043243 2023-02-10 09:07 ipfire-2.27-toolchain-20230210-x86_64.tar.zst
It doesn’t quite make sense to me!
I’m going to make my changes and try a second build.
On Feb 15, 2023, at 11:04 AM, jon jon.murphy@ipfire.org wrote:
sorry I should have been more specific. I did all of those steps.
I started over again and I’ll see if the same happens.
Jon
On Feb 15, 2023, at 2:36 AM, Adolf Belka <adolf.belka@ipfire.org mailto:adolf.belka@ipfire.org> wrote:
Hi Jon,
On 14/02/2023 22:43, jon wrote:
All,
I started with a new `git clone git://git.ipfire.org/ipfire-2.x.git` git://git.ipfire.org/ipfire-2.x.git%60. 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.
A new toolchain was released. You need to run ./make gettoolchain
As standard when I do a new build I run ./make gettoolchain ./make downloadsrc ./make clean ./make build
The gettoolchain most of the time comes back with " latest toolchain already downloaded" but occasionally, like a couple of days ago, it downloaded and checked the b2 sum of a new toolchain.
I think for a new clone you definitely need to do the whole set of commands.
Regards,
Adolf.
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 LFSThe toolchain files I have are
ipfire-2.27-toolchain-20220808-x86_64.b2 ipfire-2.27-toolchain-20220808-x86_64.tar.zstDoes this make sense? Jon
Jon Murphy jon.murphy@ipfire.org mailto:jon.murphy@ipfire.org
-- Sent from my laptop
Hello Jon,
Currently master is using a different toolchain than next.
Is that the missing piece in the puzzle?
-Michael
On 15 Feb 2023, at 22:10, jon jon.murphy@ipfire.org wrote:
I just did:
git clone git://git.ipfire.org/ipfire-2.x.git sudo ./make.sh downloadsrc sudo ./make.sh gettoolchain sudo ./make.sh build
I did this build just to make sure things worked (and all was OK).
But, after the first build I still have the old toolchains.
jon@deb11HPZ:~/develoment/ipfire-2.x$ ll cache/toolchains total 97872 drwxr-xr-x 2 root root 4096 2023-02-14 15:24 . drwxr-xr-x 3 root root 32768 2023-02-15 15:00 .. -rw-r--r-- 1 root root 193 2022-08-11 04:14 ipfire-2.27-toolchain-20220808-x86_64.b2 -rw-r--r-- 1 root root 100174269 2022-08-11 04:14 ipfire-2.27-toolchain-20220808-x86_64.tar.zst
Then I did a second `sudo ./make.sh gettoolchain` and now I see:
jon@deb11HPZ:~/develoment/ipfire-2.x$ ll cache/toolchains total 192648 drwxr-xr-x 2 root root 4096 2023-02-15 15:05 . drwxr-xr-x 3 root root 32768 2023-02-15 15:00 .. -rw-r--r-- 1 root root 193 2022-08-11 04:14 ipfire-2.27-toolchain-20220808-x86_64.b2 -rw-r--r-- 1 root root 100174269 2022-08-11 04:14 ipfire-2.27-toolchain-20220808-x86_64.tar.zst -rw-r--r-- 1 root root 193 2023-02-10 09:07 ipfire-2.27-toolchain-20230210-x86_64.b2 -rw-r--r-- 1 root root 97043243 2023-02-10 09:07 ipfire-2.27-toolchain-20230210-x86_64.tar.zst
It doesn’t quite make sense to me!
I’m going to make my changes and try a second build.
On Feb 15, 2023, at 11:04 AM, jon jon.murphy@ipfire.org wrote:
sorry I should have been more specific. I did all of those steps.
I started over again and I’ll see if the same happens.
Jon
On Feb 15, 2023, at 2:36 AM, Adolf Belka adolf.belka@ipfire.org wrote:
Hi Jon,
On 14/02/2023 22:43, jon wrote:
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.
A new toolchain was released. You need to run ./make gettoolchain
As standard when I do a new build I run ./make gettoolchain ./make downloadsrc ./make clean ./make build
The gettoolchain most of the time comes back with " latest toolchain already downloaded" but occasionally, like a couple of days ago, it downloaded and checked the b2 sum of a new toolchain.
I think for a new clone you definitely need to do the whole set of commands.
Regards,
Adolf.
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 LFSThe toolchain files I have are
ipfire-2.27-toolchain-20220808-x86_64.b2 ipfire-2.27-toolchain-20220808-x86_64.tar.zstDoes this make sense? Jon
Jon Murphy jon.murphy@ipfire.org
-- Sent from my laptop
On Feb 16, 2023, at 3:13 AM, Michael Tremer michael.tremer@ipfire.org wrote:
Hello Jon,
Currently master is using a different toolchain than next.
Is that the missing piece in the puzzle?
Yes!
-Michael
On 15 Feb 2023, at 22:10, jon jon.murphy@ipfire.org wrote:
I just did:
git clone git://git.ipfire.org/ipfire-2.x.git sudo ./make.sh downloadsrc sudo ./make.sh gettoolchain sudo ./make.sh build
I did this build just to make sure things worked (and all was OK).
But, after the first build I still have the old toolchains.
jon@deb11HPZ:~/develoment/ipfire-2.x$ ll cache/toolchains total 97872 drwxr-xr-x 2 root root 4096 2023-02-14 15:24 . drwxr-xr-x 3 root root 32768 2023-02-15 15:00 .. -rw-r--r-- 1 root root 193 2022-08-11 04:14 ipfire-2.27-toolchain-20220808-x86_64.b2 -rw-r--r-- 1 root root 100174269 2022-08-11 04:14 ipfire-2.27-toolchain-20220808-x86_64.tar.zst
Then I did a second `sudo ./make.sh gettoolchain` and now I see:
jon@deb11HPZ:~/develoment/ipfire-2.x$ ll cache/toolchains total 192648 drwxr-xr-x 2 root root 4096 2023-02-15 15:05 . drwxr-xr-x 3 root root 32768 2023-02-15 15:00 .. -rw-r--r-- 1 root root 193 2022-08-11 04:14 ipfire-2.27-toolchain-20220808-x86_64.b2 -rw-r--r-- 1 root root 100174269 2022-08-11 04:14 ipfire-2.27-toolchain-20220808-x86_64.tar.zst -rw-r--r-- 1 root root 193 2023-02-10 09:07 ipfire-2.27-toolchain-20230210-x86_64.b2 -rw-r--r-- 1 root root 97043243 2023-02-10 09:07 ipfire-2.27-toolchain-20230210-x86_64.tar.zst
It doesn’t quite make sense to me!
I’m going to make my changes and try a second build.
On Feb 15, 2023, at 11:04 AM, jon jon.murphy@ipfire.org wrote:
sorry I should have been more specific. I did all of those steps.
I started over again and I’ll see if the same happens.
Jon
On Feb 15, 2023, at 2:36 AM, Adolf Belka adolf.belka@ipfire.org wrote:
Hi Jon,
On 14/02/2023 22:43, jon wrote:
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.
A new toolchain was released. You need to run ./make gettoolchain
As standard when I do a new build I run ./make gettoolchain ./make downloadsrc ./make clean ./make build
The gettoolchain most of the time comes back with " latest toolchain already downloaded" but occasionally, like a couple of days ago, it downloaded and checked the b2 sum of a new toolchain.
I think for a new clone you definitely need to do the whole set of commands.
Regards,
Adolf.
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 LFSThe toolchain files I have are
ipfire-2.27-toolchain-20220808-x86_64.b2 ipfire-2.27-toolchain-20220808-x86_64.tar.zstDoes this make sense? Jon
Jon Murphy jon.murphy@ipfire.org
-- Sent from my laptop
-
Adolf Belka -
jon -
Michael Tremer