Re: shared modules and versioned symbols

On Wed, 8 Sep 1999, Sascha Schumann wrote: > On Wed, Sep 08, 1999 at 03:47:18PM +0200, Gergely Madarasz wrote: > > > > > > On Wed, 8 Sep 1999, Gergely Madarasz wrote: > > > > > Btw I was wondering... won't the shared modules have issues with this > > > version stuff ? I'm about to check it now... > > > > I checked it, it seems it really has issues... > > How did you check what? I compiled a shared module. > > the smallest problem is > > that when linking the shared module the version script has to be passed so > > the modules internal symbols get version info... this is a small change in > > the makefile. > > Why? Passing the --version-script at the final link step within > php4 should be enough since it will mean that all symbols > within that library are versioned. I was talking about dynamically loadable modules, like xml.so, mysql.so > > The bigger problem is with the symbols of the main libphp4 which are used > > by the module. The module needs to be linked against libphp4 to pick up > > the version information, which is in the current build process impossible > > because libphp4.so is linked only at the end of the build. > > Any suggestions? > > I don't see a problem here. We are going to create a shared > library and this library is versioned. Nothing else needs to > be versioned. We just need to make sure that all symbols > within a single DSO are versioned. But there are more DSO's. Greg