From mboxrd@z Thu Jan 1 00:00:00 1970 From: Adolf Belka To: development@lists.ipfire.org Subject: Re: Failure to build clamav due to rust reversion Date: Thu, 29 Aug 2024 20:06:46 +0200 Message-ID: <7d25fe95-d7fc-4ef8-9159-3daa8fc6371a@ipfire.org> In-Reply-To: <7C213CC0-31F6-476B-A148-E7D35169130A@ipfire.org> MIME-Version: 1.0 Content-Type: multipart/mixed; boundary="===============7875106898351610197==" List-Id: --===============7875106898351610197== Content-Type: text/plain; charset="utf-8" Content-Transfer-Encoding: quoted-printable Hi Michael, I just found this section on the rust site that suggests a build from source = can be done, if my interpretation is correct. https://forge.rust-lang.org/infra/other-installation-methods.html#source-code If this is really being able to build the rust toolchain from scratch via a s= ource build then I could give that a try. What are the changes that you mentioned needed to be made to make rust build = ruby for non x86_64 architectures? Regards, Adolf. On 29/08/2024 15:55, Michael Tremer wrote: > Okay, Rust is such a nightmare=E2=80=A6 >=20 > I didn=E2=80=99t run a full clean build after the revert because my build s= ystem is busy with other things=E2=80=A6 I just assumed it would be working f= ine. >=20 > I can revert clamav as well for now until we have a solution so that at lea= st the system can finish the build. >=20 > I would like to leave this for you to find a solution as you are way more i= nvolved in this than I am. If you need me, you know where to find me. >=20 > -Michael >=20 >> On 29 Aug 2024, at 15:24, Adolf Belka wrote: >> >> Hi All, >> >> On 29/08/2024 15:04, Adolf Belka wrote: >>> Hi Michael & Matthias, >>> >>> I just re-ran my build after the removal of the coreutils patch. >>> >>> The build went past coreutils with no problem. However it has then failed= at clamav (1.4.0) with the message >>> >>> error: package `home v0.5.9` cannot be built because it requires rustc 1.= 70.0 or newer, while the currently active rustc version is 1.67.0 >>> Either upgrade to rustc 1.70.0 or newer, or use >>> cargo update -p home(a)0.5.9 --precise ver >>> where `ver` is the latest version of `home` supporting rustc 1.67.0 >>> >>> Rust was reverted back to 1.67.0 due to problems with building ruby for a= arch64 and riscv64. >>> >>> https://git.ipfire.org/?p=3Dipfire-2.x.git;a=3Dcommit;h=3D33ee3958de834f7= eb686fb5b5daa56d511bb18e9 >>> >>> So until rust has the fix for building ruby for aarch64 and riscv64 then = it looks like there needs to be a limit set to the version of rust-home to 0.= 5.3, which is the version that we have with rust-1.67.0 >>> >>> Unless of course I have not understood the root cause of this problem, wh= ich definitely could be the case. >>> >> I have realised that clamav has the rust modules bundled into the source t= arball and home is at 0.5.9 in that bundle. >> >> Looking through clamav, I can't find a way to easily tell clamav to use th= e rust-home version that is in IPFire. Hopefully Matthias with his knowledge = of building clamav with rust can find a way. >> >> Regards, >> >> Adolf. >> >>> Regards, >>> >>> Adolf. >=20 >=20 --===============7875106898351610197==--