On Sun, 2009-10-25 at 20:26 -0400, Chris Knadle wrote:
> The reason the -dev libraries aren't installed along with the normal > "binary" libraries is that most people only use the executable portion > of libraries, so distributions usually only install a very minimal set > of -dev libraries to start with in order to save space. At least some > distributions also deal with dependencies on versions of the source > for a package. For instance on Debian after installing a source > package via "apt-get source <package>" it's possible to run "apt-get > build-dep <package" to install all of the required development > libraries necessary to build [i.e. compile] that source package. > > As you're trying to compile AIDE from source that's not through Fedora > then these source dependencies are not available (and I don't know how > these work through RPM/YUM or even if Fedora/RHEL deals with source > dependencies), so you'll have to figure out by hand which development > libraries you'll need to install. > On further thought about your reply and investigation (via Google) I believe you've outlined a solution. There is an RPM/YUM analog to the apt-get build-dep you described above. It is yum-builddep. I can run it against the AIDE source RPM to get a list of the needed development libraries. Secondly, I'm thinking my plan of generating an AIDE binary (from source) intended to run on Fedora from Ubuntu or Xubuntu (either on the same or a different PC) might not work. The ./configure script output is based on the environment in which it is run. > _______________________________________________ Mid-Hudson Valley Linux Users Group http://mhvlug.org http://mhvlug.org/cgi-bin/mailman/listinfo/mhvlug Upcoming Meetings (6pm - 8pm) MHVLS Auditorium Oct 7 - Glade - Linux GUIs made easy Nov 4 - Google Wave Dec 2 - MythTV Jan 6 - Git
