Hello fredvs, you wrote on Fri, 10 Apr 2020 17:57:15 -0700 (MST):
> > Why do you think so? AFAIK, it is _meant_ to be handled in such a > > way. > > But how will you do is the library dont provide the "nude" symlink and > only provide the soname, like libportaudio.so.2? > Oblige people to create by their self a symlink libportaudio.so ? What I wanted to say is meant to be handled in such a way is the _transition_ from one API to an incompatible follower that requires modifications to the code using it. I must concede, though, that I'm not at all thoroughly familiar with the matter. What I wrote is just what I read and gathered from the available sources. > Sorry but I prefer to link directly to libportaudio.so.2. That is only required if your program explicitly needs that specific version. Otherwise, the system linker takes (should take) care of providing the neccessary links to the current library file. That means, if your programm requires libportaudio.so.2, because it uses a feature not provided by, say libportaudio.so.3*, you have to specify the specific link. This could in principle even go further down the version tree. > You have to take in account that the soname is updated each time that a > minor version appear, so you are always uptodate if you use the soname > (the soname is the name of the library + ".so" + the first number). How this is to be handled depends on the requirements of your program. If it can work with "any" version of the library, no version needs to be specified. If it requires a specific version, this has to be given. If it can work with any version up to somw specific one, it depends on whether sysmbol versioning is implemented by the library. If it is, you should be able to specify the oldest version providing the required functions, and then you (or the user) might have to provide an appropriate link. (That is, if "ldconfig" doesn't do this already.) That's at laest as I see this and as far as I understood the matter. you wrote on Thu, 9 Apr 2020 18:10:11 -0700 (MST): > > _What_ "bug"? ... > Fpc will strip the code into libX11.so, without the so number. > You are obliged to create a symlink libX11.so that point to ink to > libX11.so.6. That's what the system linker (helper "ldconfig") should have taken care of when it (re)created the current library links after an update. > The bug is not about using dev package (even if it should not be needed > for fpc users). In this respect, I've found arguments that someone doing development - and that certainly applies to fpc users - should be required to provide the neccessary preconditions, including installing required packages. Providing specific development packages isn't even that old a custom, the distribution I use, Slackware, e.g. doesn't have specific development packages at all. If, for a distribution that does have them, an fpc package does _not_ provide the pertaining dependencies (e.g. for a Debian package), that package can be considered thoroughly broken. > Now I can install fpc and msegui on a RPi with Raspbian distro without the > need to be connected to install some no needed dev-package. The Debian "dev" package (and probabely those of other distributions) also contains the header files for the API functions. You'll only get away without _these_ if your compiler provides it's own API data, which fpc does by means of the precompiled .ppu files. Then, one really only needs the library link, which can also be set by the package installer, usually by means of a post-install script. So, in the end, the "bug" you reproach against fpc is just the omission to provide the neccessary library link. (And the reason I didn't even notice this is my not using a distribution requiring development packages, even already having the library headers installed before installing an "official" fpc package.) That's at least, to repeat, as I see and understand the matter. Sorry for the long text. -- -- (Weitergabe von Adressdaten, Telefonnummern u.ä. ohne Zustimmung nicht gestattet, ebenso Zusendung von Werbung oder ähnlichem) ----------------------------------------------------------- Mit freundlichen Grüßen, S. Schicktanz ----------------------------------------------------------- _______________________________________________ mseide-msegui-talk mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/mseide-msegui-talk
