Description of problem: When rpmlint checks a package with only .cmo (Ocaml object file) or .cmx (Ocaml native object file) files in /usr/lib[64], it issues the only-non-binary-in-usr-lib warning. However, those files are binary. Can BinariesCheck.check() be modified to include them? Version-Release number of selected component (if applicable): rpmlint-0.78-2.fc6 How reproducible: Always Steps to Reproduce: 1. Build an Ocaml package that puts .cmo or .cmx files into /usr/lib[64], but no .o or .so files. 2. Run rpmlint on the package Actual results: rpmlint complains that there are only nonbinary files in /usr/lib[64] Expected results: rpmlint should not complain, since those files are binary Additional info:
Hello Jerry, do you have a test package somewhere that could be used to test this? Also, I'm completely clueless wrt. Ocaml - are both *.cmo and *.cmx architecture dependent files? file(1) says: Objective caml native object file (.cmx) (Version 010). Objective caml object file (.cmo) (Version 006). ...so does that mean that *.cmx is arch dependent, *.cmo arch independent? What we're interested in in that particular rpmlint check is whether there's only arch-independent stuff in /usr/lib (the "binary" word in the warning identifier is somewhat misleading - binary files can be arch independent too, but changing it could break people's warning message filters... :P).
Hm, Google gave me this: https://gforge.inria.fr/plugins/scmsvn/viewcvs.php/trunk/INSTALL?rev=9116&root=coq&view=auto "The important fact is that some files are architecture dependent (.cmx, .o and executable files for instance) but others are not (.cmo and .vo)." ...so I suppose presence of *.cmo should not suppress the warning, *.cmx should.
Done upstream, will be in the next release: http://rpmlint.zarb.org/cgi-bin/trac.cgi/changeset/1308
Done in upcoming 0.79-1.