-
Notifications
You must be signed in to change notification settings - Fork 260
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
ABI change without SONAME bump #97
Comments
I admit not knowing much about this, so excuse me if this is a dumb question, but... could you explain it a little, especially considering that fluid_defsfont_get_sample is not part of the public API? So any external program using this function is broken in itself, if it breaks from this symbol being removed. Original comment by: diwic |
Original comment by: quadrispro |
Original comment by: quadrispro |
David, please have a look at the symbols exported by the 1.1.3's library (dpkg-gensynmbols(1)), I cannot assume there's no external application using that call. So, please, bump the SONAME. Original comment by: quadrispro |
Fixed in r428 by reinserting the function, as recommended by plcl here: https://lists.nongnu.org/archive/html/fluid-dev/2011-08/msg00027.html Original comment by: diwic |
Thanks! Original comment by: quadrispro |
FluidSynth 1.1.4 breaks the binary compatibility with the previous releases as it dropped one public symbol:
dpkg-gensymbols: warning: debian/libfluidsynth1/DEBIAN/symbols doesn't match completely debian/libfluidsynth1.symbols
--- debian/libfluidsynth1.symbols (libfluidsynth1_1.1.4-1_amd64)
+++ dpkg-gensymbolsWTLLjv 2011-08-05 07:51:13.943270426 +0000
@@ -89,6 +89,7 @@
+ fluid_allpass_release@Base 1.1.4-1
@@ -121,6 +122,7 @@
+ fluid_comb_release@Base 1.1.4-1
@@ -157,7 +159,7 @@
- fluid_defsfont_get_sample@Base 1.1.3
+#MISSING: 1.1.4-1# fluid_defsfont_get_sample@Base 1.1.3
This means an ABI-change but no SONAME bump has happen'd, could you please fix that?
Reported by: quadrispro
Original Ticket: fluidsynth/tickets/98
The text was updated successfully, but these errors were encountered: