From: Adolf Belka <adolf.belka@ipfire.org>
To: development@lists.ipfire.org
Subject: Re: Failure to build clamav due to rust reversion
Date: Thu, 29 Aug 2024 20:06:46 +0200 [thread overview]
Message-ID: <7d25fe95-d7fc-4ef8-9159-3daa8fc6371a@ipfire.org> (raw)
In-Reply-To: <7C213CC0-31F6-476B-A148-E7D35169130A@ipfire.org>
[-- Attachment #1: Type: text/plain, Size: 2634 bytes --]
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 source 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…
>
> I didn’t run a full clean build after the revert because my build system is busy with other things… I just assumed it would be working fine.
>
> I can revert clamav as well for now until we have a solution so that at least the system can finish the build.
>
> I would like to leave this for you to find a solution as you are way more involved in this than I am. If you need me, you know where to find me.
>
> -Michael
>
>> On 29 Aug 2024, at 15:24, Adolf Belka <adolf.belka(a)ipfire.org> 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 aarch64 and riscv64.
>>>
>>> https://git.ipfire.org/?p=ipfire-2.x.git;a=commit;h=33ee3958de834f7eb686fb5b5daa56d511bb18e9
>>>
>>> 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, which definitely could be the case.
>>>
>> I have realised that clamav has the rust modules bundled into the source tarball 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 the 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.
>
>
next prev parent reply other threads:[~2024-08-29 18:06 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-08-29 13:04 Adolf Belka
2024-08-29 13:24 ` Adolf Belka
2024-08-29 13:55 ` Michael Tremer
2024-08-29 18:06 ` Adolf Belka [this message]
2024-08-29 17:18 ` Matthias Fischer
2024-08-29 21:17 ` Adolf Belka
2024-08-30 8:37 ` Matthias Fischer
2024-08-30 15:39 ` 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=7d25fe95-d7fc-4ef8-9159-3daa8fc6371a@ipfire.org \
--to=adolf.belka@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