Bug 226879 - RFE: consider *.cmo and *.cmx as binary
RFE: consider *.cmo and *.cmx as binary
Product: Fedora
Classification: Fedora
Component: rpmlint (Show other bugs)
All Linux
medium Severity medium
: ---
: ---
Assigned To: Ville Skyttä
Fedora Extras Quality Assurance
Depends On:
  Show dependency treegraph
Reported: 2007-02-01 15:17 EST by Jerry James
Modified: 2007-11-30 17:11 EST (History)
0 users

See Also:
Fixed In Version: 0.79-1
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Last Closed: 2007-02-02 11:06:45 EST
Type: ---
Regression: ---
Mount Type: ---
Documentation: ---
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---

Attachments (Terms of Use)

  None (edit)
Description Jerry James 2007-02-01 15:17:37 EST
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):

How reproducible:

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:
Comment 1 Ville Skyttä 2007-02-01 15:41:09 EST
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).
Comment 2 Ville Skyttä 2007-02-01 15:45:30 EST
Hm, Google gave me this:

"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.
Comment 3 Ville Skyttä 2007-02-01 17:02:33 EST
Done upstream, will be in the next release:
Comment 4 Ville Skyttä 2007-02-02 11:06:45 EST
Done in upcoming 0.79-1.

Note You need to log in before you can comment on or make changes to this bug.