-
Notifications
You must be signed in to change notification settings - Fork 758
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
scsynth: linker error due to undefined reference to stopServerBootDelayWarningTimer() #4992
Comments
i can't reproduce this on Arch Linux. is it at all possible the build directory or your ccache cache need to be cleaned? here's what i've tried:
i also don't see anything about the current state of things that should cause a linker error, except perhaps that these functions are only used in scsynth_main, i.e. they are used in the perhaps you can take a look at my log and see what is different: |
if i have more time after work and this is still an issue, i'll try using the AUR repo. |
I'm building in a clean chroot using devtools' The current PKGBUILD in use:
I'll dig deeper into this later today, if I have time after work. |
Sorry, I don't have an Arch Linux with me but have you tried deleting the |
@geoffroymontel Everything is created from scratch on every build. No ccache, no leftovers from previous builds. |
Seems the change broke the |
Sorry then, it's my fault :( |
@geoffroymontel no worries, stuff breaks. It's just software :) Okay, from what I understand is, that when building Can't see yet, why that is not working when dynamically linking. |
aha. we compile everything with the shared lib build has actually been broken on macOS since Dec 2019 after #4499. that nobody has reported this, plus the fact that nobody has ever asked for a libsupernova.so or libsclang.so, make me skeptical about libscsynth.so. can you remind me again why you're using that option, i.e. why we shouldn't deprecate it immediately? |
No particular reason, besides that it has been like this since I adopted the package a few years ago. |
It seems some other distros use it, some don't:
does not
Anyways, if this proves to be a maintenance burden and should generally not be supported in the future I wont hold any grudge should it be removed I guess ;-) |
@brianlheim
Yes please, I am facing the same issue building:
It allows to use the internal server from any binding. PR made |
can you elaborate? what project are you using it for? also, i guess we should also add a way to configure supernova as a shared library as well then! |
To being able to use internal server from Lua2SC (my client) I need to have libscsynth as a dll
supernova doesnt have internal server |
ok, thanks! |
FYI @dvzrv i've added it here -- #4906 #5012 is merged, so i will close this and add a new issue for the macOS linking error! thanks @sonoro1234 |
awesome stuff man! Thanks so much! |
@brianlheim hm, seems this one didn't make it into 3.11.1! |
FWIW here's a modified version of the patch that applies on 3.11.1 (only the
|
@dvzrv sorry about that, lots of things in motion. i will make sure it goes in for 3.11.2. ^^ |
Just a quick headsup: This change is not included in 3.11.2. Here's a backport patch: dvzrv@9563fb5 |
Thanks! Ran into this as well with 3.11.2, expected it to be working, quiet surprised this fix was missing. Anyway, thanks for updating the patch, it's quiet an annoying one to rebase. |
sorry again for this, i thought i had cherry-picked the fix but misread the comment above. in the future, it would be a huge help if more people tried to use the release candidates, since that's the main reason we make them available. this is fixed in the upcoming 3.12.0. |
@brianlheim No problem, mistakes happen :) Thanks for making sure it's in the next release! I don't think we have anything in place for testing RC releases, for some packages we do have so called "live" ebuilds that install directly from version control/current HEAD but I'm not sure that would've helped here (I don't think we've run into issues with what's currently in |
Environment
Steps to reproduce
Build supercollider-git from the AUR (PKGBUILD currently not up-to-date) because unable to build ;-)
Expected vs. actual behavior
Excerpt from the build log, showing the linker error:
Full build log:
supercollider-git-build.log
I assume this is related to the recent change in #4984.
I guess we're missing an include somewhere
The text was updated successfully, but these errors were encountered: