[László Böszörményi] > As noted by libtiff upstream as well, this function was internal of > tiff and its declaration was in a header file that was not installed > publicly. They could change that without prior notice.
While it might sound sensible on the surface, the realities is that the libraries binary interface (aka ABI) changed, removing a public symbol from the library. Such API change require a no major SONAME number to avoid breaking programs using the library. > If linuxcnc-uspace still wants to use it, then copy that function[1] > and its details to their source tree. They already done copying with > the _TIFFsetString() function declaration. Then I can add a break for > its older versions for tiff. It is not linuxcnc-uspace that is using it. It is the tcl/tk Img library. To test for yourself, try running 'wish' and give it the 'package require Img' command to load the Img library. linuxcnc do the equivalent loading, but using the python Tk library. Removing the symbol without bumping the SONAME made it impossible for programs using the symbol to keep the old working library version. This was the ratinale for my severity setting critical. Given that the symbol removal without bumping SONAME broken libtk-img and linuxcnc, what is your argument for lowering the severity to normal? -- Happy hacking Petter Reinholdtsen
