[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Bug#1114917: Lintian give E:binary-from-other-architecture on eBPF *.o files



Package: lintian

Hi.  Running lintian on recent 'nsd' in experimental results in a
binary-from-other-architecture complaint.  I'm not certain where these
files should be placed, but it seems /usr/lib/bpf/nsd/ isn't necessarily
an obvious incorrect place for objects for a different architecture, or
is it?

It would be nice if lintian could detect eBPF object files and treat
them somewhat different than an "ordinary" ELF object.  I think this
test is still fairly correct in general, but in this situation I think
something is missing in lintian, although I'm not certain exactly what.

Thoughts?

/Simon

Bastien Roucaries <rouca@debian.org> writes:

>> I used /usr/lib/bpf/nsd/ for nsd 4.13.0-2 in experimental.  Lintian
>> gives an E: on this, so I suggest things needs to be improved further,
>> but at least it will be possible to test XDP things now.
>> 
>> E: nsd: binary-from-other-architecture
>> [usr/lib/bpf/nsd/xdp-dns-redirect_kern.o]
>> N: 
>> N:   This ELF binary appears to have been built for an architecture other than
>> N:   the one of the binary package being tested. This may occur when a
>> N:   pre-built binary is shipped in the package or when an attempt to
>> N:   cross-compile didn't work.
>> N: 
>> N:   Visibility: error
>> N:   Show-Always: no
>> N:   Check: binaries/architecture/other
>
> This one should be fixed on lintian side. Please fill a bug

Attachment: signature.asc
Description: PGP signature


Reply to: