> Other than my daughter being a little sick, all is well here. Thanks > for asking. Hope all is well with you and yours as well. > I hope that she gets better and that your worries fade away.
> I was able to install the debug file, but the other 3 will not > install with rpm -i because of dependency hell. Should I do a rpm -i > --nodeps on the 2 files that give me that issue? Here are the errors: > > warning: /home/nstanosheck/Desktop/libstdc++so7- > 4.2.0-0.3.20060428.fc5.3.ppc64.rpm: Header V3 DSA signature: NOKEY, > key ID 4f2a6fd2 > error: Failed dependencies: > ld64.so.1()(64bit) is needed by libstdc++so7- > 4.2.0-0.3.20060428.fc5.3.ppc64 > ld64.so.1(GLIBC_2.3)(64bit) is needed by libstdc++so7- > 4.2.0-0.3.20060428.fc5.3.ppc64 > libc.so.6()(64bit) is needed by libstdc++so7- > 4.2.0-0.3.20060428.fc5.3.ppc64 > libc.so.6(GLIBC_2.3)(64bit) is needed by libstdc++so7- > 4.2.0-0.3.20060428.fc5.3.ppc64 > libc.so.6(GLIBC_2.4)(64bit) is needed by libstdc++so7- > 4.2.0-0.3.20060428.fc5.3.ppc64 > libgcc_s.so.1()(64bit) is needed by libstdc++so7- > 4.2.0-0.3.20060428.fc5.3.ppc64 > libgcc_s.so.1(GCC_3.0)(64bit) is needed by libstdc++so7- > 4.2.0-0.3.20060428.fc5.3.ppc64 > libgcc_s.so.1(GCC_3.3)(64bit) is needed by libstdc++so7- > 4.2.0-0.3.20060428.fc5.3.ppc64 > libgcc_s.so.1(GCC_4.2.0)(64bit) is needed by libstdc++so7- > 4.2.0-0.3.20060428.fc5.3.ppc64 > libm.so.6()(64bit) is needed by libstdc++so7- > 4.2.0-0.3.20060428.fc5.3.ppc64 > and > warning: /home/nstanosheck/Desktop/libstdc++so7- > devel-4.2.0-0.3.20060428.fc5.3.ppc.rpm: Header V3 DSA signature: > NOKEY, key ID 4f2a6fd2 > error: Failed dependencies: > libstdc++so7 = 4.2.0-0.3.20060428.fc5.3 is needed by > libstdc++so7- devel-4.2.0-0.3.20060428.fc5.3.ppc > The information above is telling you what's missing which libstdc++so7 needs to function. In brief, you need to find: > ld64.so.1()(64bit) > ld64.so.1(GLIBC_2.3)(64bit) > libc.so.6()(64bit) > libc.so.6(GLIBC_2.3)(64bit) > libc.so.6(GLIBC_2.4)(64bit) > libgcc_s.so.1()(64bit) > libgcc_s.so.1(GCC_3.0)(64bit) > libgcc_s.so.1(GCC_3.3)(64bit) > libgcc_s.so.1(GCC_4.2.0)(64bit) > libm.so.6()(64bit) As far as finding the above you could use google to help you or you could go to rpmfind.net. Also try sourceforge.net and freshrpms.net. As you obviously have a 64 bit system you could also use yum to do this kind of search for you. I can't show you a working example because my yum.conf points to 32 bit libraries. However, you should be able to do: #yum search "libgcc_s*" #yum search "ld64.so.1*" #yum search "libc.so.6*" #yum search "libm.so.6*" Of course, you wait for yum to find it and then install it after it's been found. #yum install "libgcc_s*" etc. The * is called a wild card which means that yum will list any character following the previous digit including spaces. The * saves a ton of typing. One small, and annoying detail, (those are the worst usually) make sure that your yum.conf also points to 64 bit libraries of Fedora Core 5 just in case TSS doesn't have those rpms in their libraries! How you modify yum.conf differs according to the version of YDL you are using. The yum.conf of YDL 5 is not the same as YDL 4. The details regarding that are here: http://www.terrasoftsolutions.com/support/solutions/ydl_5.0/yum.shtml If you are interested in modifying yum.conf to include Fedora Core write back and I'll explain that. After the above is installed then you can believe that the primary program of interest should work. Now, regarding the line: warning: /home/nstanosheck/Desktop/libstdc++so7- > 4.2.0-0.3.20060428.fc5.3.ppc64.rpm: Header V3 DSA signature: NOKEY, > key ID 4f2a6fd2 and anything similar to it. rpm is complaining that the file is marked as containing a key which you are not using. You can get around that by: rpm -ivh --nodeps --force lib*.rpm Explanation: You could use i alone, but v (verbose) tells you what's going on and h (hash) provides little marks on the terminal screen as the package is unpacked allowing you to know what is happening and how far the package has proceeded in being unpacked and installed. You know what nodeps is. force tells rpm to ignore the key (created by the author of the package) and install the package without using it. You could install the package without the deps but should you ever really need to use this software you'll have to remember why it's not performing as you would expect. My view is that as you are up at the 64 bit stratosphere, it's worth your effort to get these dependencies installed the right way first. Caveat: If you have more than one rpm which begins with lib then what I've written as a short form to install the rpm won't work. Let's say you found the dependencies, they've been downloaded into your system and they are ready for installation. You want to use the wild card to your advantage and get these dependencies in and finally get to the real work. You could do: rpm -ivh --nodeps ld*1() rpm -ivh --nodeps ld*1(G*) rpm -ivh --nodeps l*6() rpm -ivh --nodeps l*6(G*3) rpm -ivh --nodeps l*6(G*4) This way where the packages are the same you type * to symbolize them instead just type out the characters which distinctly identify each package. Just my $.02 Sincerely, Derick. ======== The scientist's religious feeling takes the form of a rapturous amazement at the harmony of natural law, which reveals an intelligence of such superiority that, in comparison with it, the highest intelligence of human beings is an utterly insignificant reflection. This feeling is the guiding principle of his life and work. -- Albert Einstein, Scientist.
signature.asc
Description: PGP signature
_______________________________________________ yellowdog-general mailing list [email protected] http://lists.terrasoftsolutions.com/mailman/listinfo/yellowdog-general HINT: to Google archives, try '<keywords> site:terrasoftsolutions.com'
