optional package for libraries are not hybrid-enabled
|Reported by:||pulkomandy||Owned by:||bonefish|
installing optional package with libraries only installs them for the 'main' gcc. For example, on a gcc2 hybrid you don't get the gcc4 version of the lib.
With the current runtime loader behaviour, this means when running a gcc4 app, the gcc2 lib could be loaded.
Even worse, running a gcc2 app on a gcc4h install in this case leads to load of the lib, which itself depends on libsupc++. Loading this in a gcc2 image causes a lot of weird bugs in unrelated places.
I think this could be solved by renaming the gcc4 libs, for example using "4so" as a suffix instead of just so. This would help avoiding mixups, and allow to put the libs in the same directory. As a result, the optional packages for gcc4 can be installed in a gcc2 hybrid without creating problems.
On the other hand :
- The package manager may solve that in a better way ? (installing the libs at the right place somehow ?)
- There is some work needed on build of packages, for example sdl-config, allegro-config and other pkg-config files should look to setgcc setting and use the right lib path according to that.