![]() ![]() Since ldd provides a list of the shared libraries each program requires, both halves of the equation are complete - that is, the packages that make shared libraries available, and the packages that require those shared libraries, are tracked by RPM. RPM does this by running ldd on every executable program in a package's %files list. ![]() The soname is the name used to determine compatibility between different versions of a library. When a package is built by RPM, if any file in the package's %files list is a shared library, the library's soname is automatically added to the list of capabilities the package provides. Than, after a goole or two, i found the Automatic Dependencies page, that says: Why does the RPM automatically adds the requirements? can I control it somehow?Īfter reading Ignacio Vazquez-Abrams answer I realized that rpmbuild is generating an automatic requirements list. How can I fix this? what am I doing wrong? Glibc-2.12-1.80.el6.i686 : The GNU libc librariesĪfter playing with the spec file for a while I noticed that if I delete the %files part from the spec file, than no requirements are needed. Loading mirror speeds from cached hostfile ![]() ![]() Loaded plugins: downloadonly, fastestmirror You could try running: rpm -Va -nofiles -nodigestĪlthough the RPM was built on 64-bit, it requires 32-bit packages, for example, for the glibc package, i have the 64-bit package installed, but the RPM dependencies requires libc.so.6: ~]# yum provides libc.so.6 You could try using -skip-broken to work around the problem When trying to install the package on another 64-bit CentOS 6.3 server, i get the following errors: -> Finished Dependency ResolutionĮrror: Package: 86_64 (myrepo) Provides: test-fms = %/* $RPM_BUILD_ROOT/ I'm trying to build a package using rpmbuild on 64-bit CentOS 6.3 server. ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |