-
Notifications
You must be signed in to change notification settings - Fork 4
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Fail to build from master #26
Comments
build-release just calls build-debug with the --release flag, so that's normal. As for the build issues, do you have a proper C linker setup? The backend interfaces with nvtop which is developed in C. Also, it's using the same backend as Mission Center so I'd recommend checking if that fails to build as well. |
I build a whole distro, with 8 desktop environments (including COSMIC), and have zero problems. I don't understand what is missing that is causing this link error:
Most likely I don't have some of your project dependencies, and since it was building fine just a few weeks ago, maybe you know what dependency has been included recently. Thanks! |
The only dependency that's been added is nvtop for GPU usage monitoring, whatever is going on it seems that cargo isn't properly building nvtop on your end. |
I just built nvtop from scratch:
No problem at all. I'm confused. |
I think your project is failing to find nvtop .c files with the headers. For instance, this error:
init_extract_gpuinfo_intel is a method in |
I even tried building in a fresh VM and it still built fine for me. I'm not sure what the issue could be. The command cc works on your system right? |
Could you try building with Rust stable and no extra flags to see if it works? |
(also just checking, you have clang installed right?) |
Do you mind telling exactly how you're building your project? Every single command you type until you have a working binary. |
From the VM? I'm installing rustup and just, doing rustup default stable, and running just build-release and installing whatever dependencies it says I'm missing, and once they're all there it builds fine. Never mentions nvtop |
That's odd that it skipped, does cc output anything when you run it on your system? |
I tried using rust stable There's nothing wrong with my build environment. As I said, I'm building a whole (!) distro with 8 desktop environments and I have zero errors. It's definitely something related to how your project configuration is being set. For now I'm giving up your project, sorry. Let's wait and see if other people will face the same problem. Thanks anyway :) |
I am facing the same problem for the release build. |
If you remove the -flto option from build.rs, the release build is also working: diff --git a/observatory-daemon/build/build.rs b/observatory-daemon/build/build.rs
|
I confirm that. Thanks! |
I'm using these commands to build on PorteuX 1.8 with rust nightly + LLVM 19.1.5:
And get this:
It was building fine a few weeks ago (probably before this daemon was introduced).
Also, I don't understand why
build-debug
is being called if I explicitly calledbuild-release
.The text was updated successfully, but these errors were encountered: