Package: abootimg
Version: 0.6-1
Severity: normal
Tags: upstream

By inspection of its source code, abootimg has the same bug as Android
mkbootimg: because it writes host structs directly into the file,
if the size or endianness of any of the integers in those structs does
not match the expected size/endianness (4-byte int, little-endian),
the image will be misinterpreted by the Android device.

Another possibility would be to only build abootimg on little-endian
platforms (any-i386, any-amd64, armel, armhf, mipsel etc., but not
powerpc).

-- System Information:
Debian Release: jessie/sid
  APT prefers proposed-updates
  APT policy: (500, 'proposed-updates'), (500, 'unstable'), (500, 'testing'), 
(500, 'stable'), (1, 'experimental')
Architecture: amd64 (x86_64)
Foreign Architectures: i386

Kernel: Linux 3.10-3-amd64 (SMP w/4 CPU cores)
Locale: LANG=en_GB.utf8, LC_CTYPE=en_GB.utf8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash


-- 
To UNSUBSCRIBE, email to [email protected]
with a subject of "unsubscribe". Trouble? Contact [email protected]

Reply via email to