-
Notifications
You must be signed in to change notification settings - Fork 43
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
Error while compiling with Aur package #191
Comments
it is worth noting that other notan modules do get compiled |
This is interesting. Since this seems to happen in |
i'm being told that notan graphics and notan macro has the same metadata and that it should be recompiled with diferent metadata |
It seems there is a typo and cmake is missing in makedepends, quoting petsam in the aur
|
Thank you so much! I got an email with the comment, but could not make much sense of it. Thank you for the context - I made the changes and will publish the update in the next release. Please let me know and reopen if this still fails. |
I added cmake to makedepends and removed the -t in pkgbuild and res/pkgbuild and i'm still getting the same error |
I think it would probably make sense to report this as an issue in
This is a wild guess, but the error looks like it could have something to do with compiling shaders, maybe there is something specific AUR packages are built vs. how you build as a regular user? |
Oculante compiles successfully and runs as intended, i was unable to run the example from notan, the error i got was |
Thanks for testing. For I guess since it compiles fine when run locally, I assume that there is either something missing in |
i am sad to announce that the 6.65 AUR package has the same error |
i am sad to announce, that the 6.66 AUR package has the same error, why not ask for help in the AUR?, i truly don't know what is the issue, and people in notan also don't know what the issue is :c |
Yeah, I am sorry for that. I also don't know anything about Arch/AUR, and am not sure where to start. I can try asking for help, but I can't test. |
i could test it if you wish |
@LuisB79 I have been using the AUR package successfully for a while so I wonder if there is something specific in your system that could be causing it. If you have tried reaching for help at some Arch users forums would you mind linking the discussion here? Otherwise, would you mind sharing some more details about your system? I probably won't be able to help much soon but I am very curious about source of the issue. Also, sorry for the Some simple details about my system for comparison: I worry this might be much more difficult to track than finding differences but it would be a start. |
Sure, its all been on discord i havent made a proper thread in the aur forums Distro: Arch im using paru for installing aur packages |
I tried to install it with paru and it worked fine. I also took a peek at notan and I am suspecting something related to this function to be a potential source of issues. The function is invoked as part of the macros that fail to compile. Further I think it might be related the glsl_to_spirv crate that is used there, it has some interesting dependencies, quite complex code, and it seems to be deprecated. I don't have X11 anywhere at hand so this might be as much as I can do for this week. |
are you suggesting the use of x11 could be the issue and that it would be solved if i moved to a wayland wm? |
I personally wouldn't go that way, it would be very surprising to me. Not
impossible though so if it sounds reasonable to you, you could try
installing oculante in some different environment.
Rather, I've been thinking that there might be a difference in what this
dependency that I have pointed out has available when you are building with
paru and when I'm building with paru (any other packages missing or maybe
something completely different that I haven't thought of). The most
confusing aspect is the fact that you have built oculante successfully
without the pkgbuild from AUR. I must admit however that this is going
beyond what I would have energy to investigate properly at the moment.
Asking Notan developers what could be going wrong might be the smart move
here.
My lead could also be completely off. This is not something I found through
debugging, it's just a guess.
…On Wed, 28 Jun 2023, 03:05 B79, ***@***.***> wrote:
are you suggesting the use of x11 could be the issue and that it would be
solved if i moved to a wayland wm?
—
Reply to this email directly, view it on GitHub
<#191 (comment)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/AMP4ZP72ZE66HG5W3LYS6XTXNN7M5ANCNFSM6AAAAAAYV5TWZU>
.
You are receiving this because you commented.Message ID:
***@***.***>
|
Tried with wayland, still the same error, its pretty weird ngl |
i still have this issue on 7.4 |
With 7.5 there seems to be more errros compiling
|
Jesus christ, the error was lto, it was lto on the makepkg.conf, literally flew on top of my head because i didnt have the -flto. |
I don't fully understand this is about - you are referring to Link Time Optimization? |
Yes, arch uses makepkg and there are some flags enabled by default, others that you can tune in, anyhow, lto messes with how its compiled, and is well known that various rust programs have difficulties compiling thanks to lto |
I do have a couple of optimizations enabled in my Cargo.toml, and one of them is lto: [profile.release]
codegen-units = 1
# incremental = false
lto = true
strip = true
opt-level = 3
panic = "abort" Do you think this will cause trouble in your case, or is #226 enough and I should edit the PKGBUILD? |
i am not sure, since disabling the lto flag in my makepkg.conf is what let me compile the program, i didnt edit the cargo.toml, i wonder if makepkg adds another flag on top of that |
its worth noting that lto is enabled by default in arch |
i have seem to run into an error while compiling, cargo cannot compile notan_graphics
i have attempted at cleaning the cargo cache, it did not fixed it.
The text was updated successfully, but these errors were encountered: