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

Re: lintian error due to arm64 and aarch64 mismatch on raspberry pi



I just realized that I misread the error message. My apologies. It seems to be expecting all instead of arm64. So how might I build it for all?

On 11/11/23 7:36 pm, Shriram Ravindranathan wrote:
Dear Mentors,

I am trying to build a multiarch package (ITP #1055706) for debian on a raspberry pi. The package builds fine, however, there is a lintian error like so:
Output from debuild:
dpkg-deb: building package 'libmagicenum-dev' in '../libmagicenum-dev_0.9.3-1_all.deb'.
 dpkg-genbuildinfo -O../magic-enum_0.9.3-1_arm64.buildinfo
 dpkg-genchanges -O../magic-enum_0.9.3-1_arm64.changes
dpkg-genchanges: info: including full source code in upload
 dpkg-source --after-build .
dpkg-buildpackage: info: full upload (original source is included)
Now running lintian magic-enum_0.9.3-1_arm64.changes ...
E: libmagicenum-dev: triplet-dir-and-architecture-mismatch is for arm64 instead of all [usr/lib/aarch64-linux-gnu/]
Finished running lintian.

Output from lintian -i -I --show-overrides:
E: libmagicenum-dev: triplet-dir-and-architecture-mismatch is for arm64 instead of all [usr/lib/aarch64-linux-gnu/]
N: 
N:   This package contains a directory under /lib or /usr/lib which doesn't
N:   match the proper triplet for the binary package's architecture. This is
N:   very likely to be a mistake when indicating the underlying build system
N:   where the files should be installed.
N: 
N:   Please refer to File System Structure (Section 9.1.1) in the Debian Policy
N:   Manual for details.
N: 
N:   Visibility: error
N:   Show-Always: no
N:   Check: files/architecture

when I run dpkg --print-architecture it says arm64 but when I run the command arch it says aarch64.
Am I doing something wrong here? how do I get it to build for aarch64?
-- 
Shriram Ravindranathan
ters

Attachment: OpenPGP_0xFC7E951A7BEF0836.asc
Description: OpenPGP public key

Attachment: OpenPGP_signature.asc
Description: OpenPGP digital signature


Reply to: