That's strange, it works fine for me. I even tried it in a container to minimize dependencies -- starting with the ubi8 image, yum install git cargo, then I cloned and built your project just fine.
You didn't mention which architecture, but I'm using x86_64.
I should note that whatever support I may be able to provide here is informal. If you do have a Red Hat support contract, you may want to also reach out through those channels.
Actually, I discovered the problem when trying to do cargo install rnr which failed because of regex-syntax. My hope was to see more, if I have a minimal project.
I am in a bash shell (no restrictions whatsoever). But I have to check memory of the VM. Perhaps the VM setting is too low. Will test and report back.
No worries, I'm glad you solved it! I'm surprised that got SIGTERM instead of the usual SIGKILL for out-of-memory situations, but now I'll be aware of this possibility too.
I wonder if it would be possible for cargo to detect that rustc got killed by the oom killer and display a nice message that the oom killer was invoked.
I nice message would be fine, of course. Usually 1.5 (or even 2.5GB) is not common, it may happen in restriced environments.
In my case, for specific reasons, I have to install RHEL 8.4 on my laptop where I actually have 16GB. So, I did some tests to see what I will have in terms of software.
So, I am really happy to be able to use Rust which makes my daily life much easier as for instance I can install Rust software with cargo install when a system package is not available.