Thursday, September 1, 2016

Error while building CM 13 from source

Hello everyone!
I compile CyanogenMod 13 for my Galaxy Note 10.1. The whole process was perfect, but at the end I got an error:
Code:

Construct recovery from boot
mkdir -p /home/alex/Projects/cm13/out/target/product/n8000/obj/PACKAGING/recovery_patch_intermediates/
PATH=/home/alex/Projects/cm13/out/host/linux-x86/bin:$PATH /home/alex/Projects/cm13/out/host/linux-x86/bin/imgdiff /home/alex/Projects/cm13/out/target/product/n8000/boot.img /home/alex/Projects/cm13/out/target/product/n8000/recovery.img /home/alex/Projects/cm13/out/target/product/n8000/obj/PACKAGING/recovery_patch_intermediates/recovery_from_boot.p
build/tools/generate-notice-files.py  /home/alex/Projects/cm13/out/target/product/n8000/obj/NOTICE.txt  /home/alex/Projects/cm13/out/target/product/n8000/obj/NOTICE.html "Notices for files contained in the filesystem images in this directory:" /home/alex/Projects/cm13/out/target/product/n8000/obj/NOTICE_FILES/src
failed to reconstruct target deflate chunk 1 [(null)]; treating as normal
Traceback (most recent call last):
  File "build/tools/generate-notice-files.py", line 191, in <module>
    main(args)
  File "build/tools/generate-notice-files.py", line 181, in main
    file_md5sum = md5sum(filename)
  File "build/tools/generate-notice-files.py", line 80, in md5sum
    return hexify(sum.digest())
  File "build/tools/generate-notice-files.py", line 65, in hexify
    return ("%02x"*len(s)) % tuple(map(ord, s))
TypeError: ord() expected string of length 1, but int found
make: *** [build/core/Makefile:663: /home/alex/Projects/cm13/out/target/product/n8000/obj/NOTICE.html] Ошибка 1
make: *** Ожидание завершения заданий…

It appears when I compile system.img. Boot and recovery images were built without any problems. I assume the problem lies in NOTICE files that generates by python script. I have two options: disable notice files generating or solve this problem. But I know nothing of this.

Hope for your help.


from xda-developers http://ift.tt/2bNA9au
via IFTTT

No comments:

Post a Comment