41–49 of 49 posts
Earlier quoted context omitted.
Compiling llvm is a nightmare
it's two commands for me. What issues do you face?
Then after 30min on 99% ram usage it BSoD
Then i created linux vm but couldnt figure out crossplatform build or something like that
Then i created windows vm with 8gb of ram and it worked fine
Earlier quoted context omitted.
64 cores, and it takes 5 minutes? That’s… not awesome. Most people do not have 64 (presumably high performance) cores lying around for the purpose of building dependencies.
10 minutes of a c6i.32xlarge costs less than a dollar at on-demand rates in the us-east-2 AWS region. That'll get you 128 vCPUs and 256 gb of memory. I think people put up with a lot of stuff that there's no reason to any more with on-demand computing.
Im able to compile c# compiler way faster and with less resources
Earlier quoted context omitted.
When LLVM doesn't support your platform :( Granted, that means no Rust support today so probably not relevent to most people reading this thread, but yeah I'm still salty :|
... which platform is that ?
Earlier quoted context omitted.
... which platform is that ?
I for one maintain the official toolchains for QNX. I've been trying to port LLVM, and it's not possible to bootstrap LLVM using LLVM because it hasn't been ported yet.
I don't understand, LLVM would be on the host machine under some Linux or Windows on x86 where the development happens, not on the QNX hardware anyways, no ? Unless for some reason one would want to port Mesa to have LLVMPIPE or something like this, but I have a hard time imagining the use case.
Earlier quoted context omitted.
I for one maintain the official toolchains for QNX. I've been trying to port LLVM, and it's not possible to bootstrap LLVM using LLVM because it hasn't been ported yet.
> it's not possible to bootstrap LLVM using LLVM I don't understand, LLVM would be on the host machine under some Linux or Windows on x86 where the development happens, not on the QNX hardware anyways, no ? Unless for some reason one would want to port Mesa to have LLVMPIPE or something like this, but I have a hard time imagining the use case.
Earlier quoted context omitted.
> it's not possible to bootstrap LLVM using LLVM I don't understand, LLVM would be on the host machine under some Linux or Windows on x86 where the development happens, not on the QNX hardware anyways, no ? Unless for some reason one would want to port Mesa to have LLVMPIPE or something like this, but I have a hard time imagining the use case.
What QNX hardware are you thinking of? The self-hosted x86_64 PC being used to develop on?
Earlier quoted context omitted.
it's two commands for me. What issues do you face?
Started on windows, installed shitton of stuff Then after 30min on 99% ram usage it BSoD Then i created linux vm but couldnt figure out crossplatform build or something like that Then i created windows vm with 8gb of ram and it worked fine
Earlier quoted context omitted.
Started on windows, installed shitton of stuff Then after 30min on 99% ram usage it BSoD Then i created linux vm but couldnt figure out crossplatform build or something like that Then i created windows vm with 8gb of ram and it worked fine
Building things on Windows by itself is a nightmare in most cases. I use WSL (1, not 2, though either should work) and it build just fine. I rec going that route if you want to do linux-ey development but still keep Windows.
Earlier quoted context omitted.
10 minutes of a c6i.32xlarge costs less than a dollar at on-demand rates in the us-east-2 AWS region. That'll get you 128 vCPUs and 256 gb of memory. I think people put up with a lot of stuff that there's no reason to any more with on-demand computing.
I believe the fact that you propose renting cloud resources just for compilation shows that something aint right Im able to compile c# compiler way faster and with less resources