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

Re: Where to install arch-dependent eBPF *.o files?



Bastien Roucaries <rouca@debian.org> writes:

>> >>> Should we use /usr/lib/nsd?
>> >>> /usr/lib/x86_64-linux-gnu/nsd/?
>> >>> /usr/lib/bpf/?
>> >>> /usr/lib/bpf/nsd/?
>> >>> /usr/lib/x86_64-linux-gnu/bpf/?
>> >>> /usr/lib/x86_64-linux-gnu/bpf/nsd/?
>> >>
>> >> Not a specialist, but eBPF ELF files are bytecode for a virtual machine...
>> >> I'm interested in the correct answer, because somehow it's related to WASM.
>> >>
>> > Talk to this a debian multiarch BoF at debian, it is a virual so
>> > we must create a arch triplet for this, it is likely a candidate
>> > for an specific arch none long term.
>> > 
>> > for me it is ebpf-none-v1 or
>> > 
>> > so /usr/lib/ebpf-none-v1/
>> 
>> the shortest triplet is bpf, also used by the GNU toolchain. Why would 
>> there be a reason to version these at this point?
> due to file but if GNU toolchain use bpf we could use bpf

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

I also got an interesting complaint about embedded build paths, but this
may be due to the weird way nsd builds these BPF files and some missing
CFLAGS machinery in debian/rules.

I: nsd: file-references-package-build-path [usr/lib/bpf/nsd/xdp-dns-redirect_kern.o]
N: 
N:   The listed file or maintainer script appears to reference the build path
N:   used to build the package as specified in the Build-Path field of the
N:   .buildinfo file.
N:   
N:   This is likely to cause the package to be unreproducible, but it may also
N:   indicate that the package will not work correctly outside of the
N:   maintainer's own system.
N:   
N:   Please note that this tag will not appear unless the .buildinfo file
N:   contains a Build-Path field. That field is optional. You may have to set
N:   DEB_BUILD_OPTIONS=buildinfo=+path or use
N:   --buildinfo-option=--always-include-path with dpkg-buildpackage when
N:   building.
N: 
N:   Please refer to https://reproducible-builds.org/,
N:   https://wiki.debian.org/ReproducibleBuilds/BuildinfoFiles, and the
N:   dpkg-genbuildinfo(1) manual page for details.
N: 
N:   Visibility: info
N:   Show-Always: no
N:   Check: files/contents

/Simon

Attachment: signature.asc
Description: PGP signature


Reply to: