Re: Toolchain errors during make build

[Adolf Belka <adolf.belka@ipfire.org>]

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

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

-- 
Sent from my laptop