Thread: RPM Depencies and static linking

Hello All,

I've written a fairly basic C program on a linux machine. I've created an rpm for it as well. The program and all the build steps work fine (I also have a make INSTALL that works).

But, when I run the rpm that I built on the same machine I developed it with, rpm reports a 'Failed dependencies' error on glibc.

I understand the error message, it just makes no sense to me why I'm getting it.The program is statically linked and ldd shows it with no depencies. So why would rpmbuild put in the dependency or rpm think there was one there?

Thanks in advance.

You can just open up the rpm config file and see what the dependency says, if it's bogus delete it. Maybe there's a version issue.

Thanks for the reply. Honestly, I couldn't find any 'config' file for the rpm. I did an rpmbuild command with more verbose options, and it looks like because of the file names I have, the rpmlib module is needed, and that's what appears to be needing the glibc module, not my programs.

I suspect it may have something to do with the fact that my tar file is being built from another folder, which has ../ as a prefix, using some sort of PayloadFilesHavePrefix indicator, and I assume the reason for rpmlib.

I'll try to look into that this weekend. Thanks again.