I should expand on this: > Libtool built and linked them in the build tree, they only become > unavailable when installing them into DESTDIR, which is not the final > install location, during the "make install" step for constructing the > packages.
"make install" uses "libtool install" which relinks the targets using the target install location -L paths. This is what produces the .libs/libfoobar.so.1.2.3T files. These T files that are renamed and packaged in DESTDIR, but of course the library depdencies (shown by ldd) are broken until all of the packages in the package-set are installed. And this all breaks if an old libfoobar.so is already installed, since libtool will pick that up, incorrectly, when linking the T file. Solution to that is to uninstall the -devel package of the old release. Which is what we did today for graphviz. (The -devel package contains libfoobar.so and libfoobar.so.0 softlinks. The real, old libfoobar.0.1.2.so is OK, apparently because libtool knows that its not the version it wants.) John On 06/02/2011 08:30 PM, John Ellson wrote: > The graphviz "package-set" is all the packages built from the same > sources (as in same tar.gz). > > The CSWgraphvizperl contents depend on the CSWlibcdt5 contents from the > same package-set. > So, CSWlibcdt5 is not installed, can't be installed, while building > CSWgraphvizperl. The only way it could be installed is if CSWlibcdt5 > sources were separated, so that they weren't all in the same package-set. > > The language bindings aren't plugins, but this library dependecy issue > is the same as for the plugins (e.g CSWgraphvizgd). > > This problem of library dependencies in the *same package-set* is easily > and safely fixed with the overrides. > Libtool built and linked them in the build tree, they only become > unavailable when installing them into DESTDIR, which is not the final > install location, during the "make install" step for constructing the > packages. > > John > > On 06/02/2011 07:39 PM, Maciej Bliziński wrote: >> 2011/6/3 John Ellson <ell...@opencsw.org>: >>> Maciej, >>> >>> You asking about the dependency on the *new* libcdt5 from >>> graphviz2.28.0, right? >> Yes, libcdt5 is with the new graphviz, the previous version of >> graphviz builds libcdt4. >> >>> It does depend on it. The perl language binding extends perl with >>> wrapped functions from libgvc, libgraph, libcdt. >>> >>> Of course, since CSWgraphvizperl is in the same package-set as >>> CSWlibcdt5, is has the same problem of a dependency on a library that is >>> not yet installed. >> What do you mean by 'the same problem'? Can you expand on your reasoning? >> >> Maciej >> > _______________________________________________ > devel mailing list > devel@lists.opencsw.org > https://lists.opencsw.org/mailman/listinfo/devel _______________________________________________ devel mailing list devel@lists.opencsw.org https://lists.opencsw.org/mailman/listinfo/devel
