Sergey, On Monday 15 January 2007 10:46, Sergey Mkrtchyan wrote: > Randall R Schulz wrote: > > Sergey, > > > > Did you look at the output of "make install" to ensure there were > > no errors? > > Well, there were so much of it, running on screen for quite a long > time, I didn't even manage to catch something there. But I remember > that at the end it gave an Error, saying that it was impossible to > write something on a file, I thought that was not that problematic ;)
Always keep the output of configure and make in a log file. I usually do something like this: % configure 2>&1 |tee configure-out % make 2>&1 |tee make-out I never use "make install". > > I don't have anything else specific to offer about this particular > > problem, but if you have software that needs to be installed in > > stock system locations such as /usr/include but you have only a > > source tarball (as in: configure; make; su -c 'make install'), then > > you should consider using "checkinstall" to produce RPMs for > > installation. That way you'll know if there were any file conflicts > > and you can reliably reverse the effects of the installation. > > So, do I understand you correctly, that it is not that easy to > reverse system after installing from sources, and it is more > preferable to use RPMs (which can be obtained somehow by > "checkinstall"), since then I can remove them from YaST? No, it's not easy. For practical purposes, it could be impossible, since "make install", when run as root, can overwrite files that originated in RPMs. While those RPMs can always be reinstalled, knowing which ones were compromised can be difficult or tedious, at least. RPMs are _always_ preferable (on an RPM-based system such as SuSE Linux). Installation from an RPM will not (be default) allow you to overwrite a file that originated in an RPM and, as I mentioned, can easily be reversed simply by uninstalling the package. > > Checkinstall, which is available from the stock installation > > sources, if I recall correctly, does not work with every piece of > > software, but when it does, it's the way to go. > > Sorry my being too uninformed of it, but this "checkinstall" should > be there in the sources(shell script or something)? I didn't find > anything like that there. You didn't say which version of SuSE Linux you're running, but on version 10.0 "checkinstall" comes from the package named "checkinstall" (imagine that). You should familiarize yourself with the search funcationality in YaST's "Software Management" module. > So now, what is my way out? Can I just remove that directory from > system and try to reisntall it? I guess no ;) I don't know. Run "make install" again and capture the output. Then at least you'll know what it did and what actions might (I emphases _might_) reverse the installation. > Thank you very much. > Sergey Randall Schulz -- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
