I am building Deb packages MALI USERSPACE DRIVER from mali branch
I build packages using the command:
debuild -us -uc -b
ARCH=arm64
Rootfs = Debian 10 Buster
I am building a Deb package for RK3399 that uses the Mali T86x. Packages are assembled without errors, however, after installing them into the system, ldconfig returns the following warnings:
apt install ./libmali-midgard-t86x-r18p0-x11_1.9-1_arm64.deb
Reading package lists... Done
Building dependency tree
Reading state information... Done
Note, selecting 'libmali-midgard-t86x-r18p0-x11' instead of './libmali-midgard-t86x-r18p0-x11_1.9-1_arm64.deb'
The following NEW packages will be installed:
libmali-midgard-t86x-r18p0-x11
0 upgraded, 1 newly installed, 0 to remove and 1 not upgraded.
Need to get 0 B/8013 kB of archives.
After this operation, 29.8 MB of additional disk space will be used.
Get:1 /work/libmali-midgard-t86x-r18p0-x11_1.9-1_arm64.deb libmali-midgard-t86x-r18p0-x11 arm64 1.9-1 [8013 kB]
debconf: delaying package configuration, since apt-utils is not installed
Selecting previously unselected package libmali-midgard-t86x-r18p0-x11.
(Reading database ... 71506 files and directories currently installed.)
Preparing to unpack .../libmali-midgard-t86x-r18p0-x11_1.9-1_arm64.deb ...
Unpacking libmali-midgard-t86x-r18p0-x11 (1.9-1) ...
Setting up libmali-midgard-t86x-r18p0-x11 (1.9-1) ...
Processing triggers for libc-bin (2.28-10+deb10u2) ...
ldconfig: file /usr/lib/aarch64-linux-gnu/libmali.so is truncated
ldconfig: file /usr/lib/aarch64-linux-gnu/libMali.so.1 is truncated
ldconfig: file /usr/lib/aarch64-linux-gnu/libmali.so.1.9.0 is truncated
ldconfig: file /usr/lib/aarch64-linux-gnu/libmali.so.1 is truncated
ldconfig: file /usr/lib/aarch64-linux-gnu/libmali-midgard-t86x-r18p0-x11.so is truncated
I am building Deb packages MALI USERSPACE DRIVER from mali branch I build packages using the command:
ARCH=arm64 Rootfs = Debian 10 Buster I am building a Deb package for RK3399 that uses the Mali T86x. Packages are assembled without errors, however, after installing them into the system, ldconfig returns the following warnings:
Can you tell me what's going wrong?