On Fri, 2005-08-26 at 11:22 -0400, James Welch (jimwelc) wrote: > Hello All, > > I am fairly new to RPM and I was hoping someone could help me figure out > some dependency issue I seem to be running across with an rpm package I > have built(RHEL-9). It looks as though my package has an automatic > generated dependencies with libstdc++.so.5 > libstdc++.so.5(CXXABI_1.2) > libstdc++.so.5(GLIBCPP_3.2) Yes RPM automatically generates requires and provides. > Even though I did not manually specify any of these within my spec file. > Are these default dependencies that are included by rpm V 4.2? These come from the mechanism to find requirements of ELF binaries/shared libararies. They are there because libraries/binaries in your package link against them. ldd should tell you which. > It seems > that when I try to install my rpm on a newer release of RH(RHEL-ES-4) > that has a newer version of the shared library (libstdc++.so.6) present > it gags stating the following: > > Error: Failed dependencies: > libstdc++.so.5(CXXABI_1.2) is needed by mypackage > libstdc++.so.5(GLIBCPP_3.2) is needed by mypackage > Suggested resolutions: compat-libstdc++-33.3.2.3-47.3.i386.rpm You have a few options: 1) rebuild your rpm for the target distribution. This is probably the best thing to do as it means that you keep in sync with the system. 2) install compat-libstdc++ which rpm has already told you will fulfil your packages requirements - up2date compat-libstdc++ Paul _______________________________________________ Rpm-list mailing list Rpm-list@xxxxxxxxxx https://www.redhat.com/mailman/listinfo/rpm-list
