#321 annocheck failing to identify some Rust exectuables as Rust executables on some architectures
Closed 2 years ago by mvadkert. Opened 2 years ago by mulhern.

See instance of this problem here:
https://osci-jenkins-1.ci.fedoraproject.org/job/fedora-ci/job/rpminspect-pipeline/job/master/77082/testReport/(root)/tests/_annocheck/

This is detected by the INFO message: "Written in a language other than C/C++/Go/Rust".

All the executables checked in the example are Rust executables. Two Rust executables do not receive that message in each instance, six do. The two Rust executables that do not get that message are:
- stratis-setup-generator
- stratis-clevis-setup-generator
Both of these executables are hard links to stratis-str-cmp.

The list of executables that have that message are:
- stratis-str-cmp
- stratis-base32-decode (hard link to stratis-str-cmp)
- stratis-predict-usage (hard link to stratis-str-cmp)
- stratisd-min
- stratisd
- stratis-min

The important difference has got to be something to do with the debuginfo file being used by annocheck: For the six that aren't identified as Rust executables, the debug info file is: stratisd-debuginfo-3.0.4-1.fc35, for the ones that are identified as Rust executables the debug info file is stratisd-dracut-debuginfo-3.0.4-1.fc35 because these are included in the dracut subpackage of stratisd.

The arches where identification fails are: armv7hl, i686, x86_64, s390x. The arches where it appears to succeed are aarch64 and ppc64le.

It is unclear to me whether this behavior is caused by rpm macros, the Rust toolchain, or annocheck itself.


This seems like something https://github.com/rpminspect/rpminspect/issues could benefit from.

Ok, I've reported it there.

Closing, seems this is an RFE for annocheck.

Metadata Update from @mvadkert:
- Issue status updated to: Closed (was: Open)

2 years ago

Login to comment on this ticket.

Metadata