On Wednesday 25 February 2004 14:32, Patrick Okui wrote: > On Wed, Feb 25, 2004 at 03:46:38PM +0300, Alphonse Ogulla wrote: > > On Tuesday 24 February 2004 15:47, joseph mpora wrote: > > > There is something that has always puzzled me. Programs compiled from > > > source give me so much trouble while working under redhat. I have used > > > redhat (6.2,7.2 and now 9.0) for a long time but I have always have > > > trouble compiling 2 out of every 3 programs I compile from scratch. > > > > > > Funny enough the programs in question (eg bash 2.05b) compile > > > beautifully under slackware 9(the only other linux distro I have used > > > for a reasonable period) > > > > > > Is there anyone else using a linux distro for development? Which > > > distros have given you guys the least trouble compiling programs from > > > source? > > > > > > To lug-admin: am still getting double posts! you ignored all my posts > > > on this matter so I will assume it CAN NOT be fixed? > > > > > > Joseph > > > > Not recommended. Compiling and installing apps from source might break > > your system in future i.e cause dependency hell when trying to install > > newer packages at a later stage. Its advisable to instead create a > > package from the source and then install it to maintain system integrity. > > [confusion type=random] > > Err, you've lost me there. "creating a package" (irrespective of Un*X used) > usually means that you basically record what "make install" would > ordinarily do with a compiled binary... plus maybe list files you install. > How does that help maintain system integrity?
Perhaps I should have said system consistency. > > imho autoconf and other configure thingiemagics will check for the usual > location of the library files/binaries in the filesystem so....unless maybe > you are talking about if you later on decide to do a package install (e.g. > rpm or pkg_install) that only checks its database and could require what > you installed as source? > If you really must install an app from source, then better do it in a place not controlled by the package manager. Take for example you decide to replace an old package by an equivalent app that is compiled from source. In the event that an upgrade to the system is performed and the package manager decides the old (replaced) package should be upgraded, then it will blindly overwrite files of your new app since it has no idea it exists. -- Alphonse Ogulla Nairobi, Kenya Proud Debian user and admin --------------------------------------------- This service is hosted on the Infocom network http://www.infocom.co.ug
