On Sun, 23 Nov 2008, Chris Burel wrote: > I'm running rpmbuild to try to make an rpm for my own glibc. But for > some reason I'm not getting the expected results from the automatic > dependency finder. I'm using RPM version 4.4.2.3. I already looked > at and applied the patch described in this post: > http://lists.rpm.org/pipermail/rpm-maint/2008-April/002031.html > > unix> rpmbuild -ba -v glibc-2.8-20080929.specs > Executing(%prep): /bin/sh -e /var/tmp/rpm-tmp.11279 > ... > Executing(%build): /bin/sh -e /var/tmp/rpm-tmp.11279 > ... > Executing(%install): /bin/sh -e /var/tmp/rpm-tmp.11279 > ... > Processing files: glibc-2.8.20080929-1 > Provides: config(glibc) = 2.8.20080929-1 > Requires(rpmlib): rpmlib(CompressedFileNames) <= 3.0.4-1 > rpmlib(PartialHardlinkSets) <= 4.0.4-1 rpmlib(PayloadFilesHavePrefix) > <= 4.0-1 > Requires: /bin/bash /bin/sh /usr/bin/perl > Checking for unpackaged file(s): /usr/lib/rpm/check-files %{buildroot} > Wrote: /usr/src/rpm/srpms/glibc-2.8.20080929-1.src.rpm > Wrote: /usr/src/rpm/rpms/i386/glibc-2.8.20080929-1.i386.rpm > > This is clearly wrong, glibc obivously depends on more than bash and > perl. I can invoke the find-requires script directly on the files > described in the generated rpm, and get more expected results: Do the files in the buildroot have executable bits set? That's what controls the dependency extraction - if they're not executable on disk at that point then no dependencies will be generated. Whatever %files assigns as the permissions doesn't affect that (which could explain the difference between build and install time) - Panu - _______________________________________________ Rpm-list mailing list Rpm-list@xxxxxxxxxxxxx http://lists.rpm.org/mailman/listinfo/rpm-list
