9 replies to this topic

[Beeker]

Build environment with openembedded-core, meta-openembedded en bitbake pushed to master HEAD of today.

Problems with Samba, Enigma2-openplugins, faac, iperf, giflib etc solved.

But the last problem is the hardest one.

Kernel modules fails to split for dreambox since bitbake is switched to python 3 and utf-8 is the default and it is not allowed to mix it with other codecs.

Tested some other boxes like et1000.vudou2, ultimo, these build fine.

Error:

File: '/usr/lib/python3.5/codecs.py', lineno: 321, function: decode
     0317:
     0318:    def decode(self, input, final=False):
     0319:        # decode input (taking the buffer into account)
     0320:        data = self.buffer + input
 *** 0321:        (result, consumed) = self._buffer_decode(data, self.errors, final)
     0322:        # keep undecoded input until the next call
     0323:        self.buffer = data[consumed:]
     0324:        return result
     0325:
Exception: UnicodeDecodeError: 'utf-8' codec can't decode byte 0xf6 in position 21: invalid start byte

ERROR: linux-dreambox-3.2-r14.19.52 do_package: Function failed: split_kernel_module_packages
ERROR: Logfile of failure stored in: /home/hains/github/openpli-oe-core/build/tmp/work/dm8000-oe-linux/linux-dreambox/3.2-r14.19.52/temp/log.do_package.2781
ERROR: Task /home/hains/github/openpli-oe-core/meta-dream/recipes-bsp/linux/linux-dreambox_3.2.bb:do_package (/home/hains/github/openpli-oe-core/meta-dream/recipes-bsp/linux/linux-dreambox_3.2.bb:do_package) failed with exit code '1'

As workaround i apply a patch to openpli-oe-core/openembedded-core/meta-/classes/kernel-module-split.bbclass  line 53

      cmd = "%sobjcopy -j .modinfo -O binary %s %s" % (d.getVar("HOST_PREFIX", True) or "", file, tmpfile)
        subprocess.call(cmd, shell=True)
 -     f = open(tmpfile)
 +     f = open(tmpfile, encoding="ISO-8859-1")
       l = f.read().split("\000")
       f.close()
       os.close(tf[0])
       os.unlink(tmpfile)

Then image for DM8000 build fine and image is bootable and working as before. So far so good, but it isn't of course the real solution.
       
This patch doesn't break the build for the et10000 BTW.

I know this can be very complicated, but the workaround is quit simple. So perhaps the real solution also.

I tried a lot of things like adding utf-8 to the defconfigs file. But there are so many thus perhaps i missed the one...

Anyone an idea, hint,what's wrong ?

Attached Files

•  log.do_package.2781.txt   222.98KB   4 downloads

[mx3L]

It looks like it deals with binary file, maybe just specify to open, that it should read it in binary mode:

f = open(tmpfile, 'rb')

[goldeneye]

Why bother? Dreamboxes are no longer actively supported. Builds are only made if possible... Now a perfect time to abandon Dreamboxes completely. Turn off support, adjust OpenPli homepage, remove the Dreambox feeds and done.... Problem solved...

[Beeker]

 

It looks like it deals with binary file, maybe just specify to open, that it should read it in binary mode:

f = open(tmpfile, 'rb')

No.

0050:        tmpfile = tf[1]
     0051:        cmd = "%sobjcopy -j .modinfo -O binary %s %s" % (d.getVar("HOST_PREFIX", True) or "", file, tmpfile)
     0052:        subprocess.call(cmd, shell=True)
     0053:        f = open(tmpfile, 'rb')
 *** 0054:        l = f.read().split("\000")
     0055:        f.close()
     0056:        os.close(tf[0])
     0057:        os.unlink(tmpfile)
     0058:        vals = {}
Exception: TypeError: a bytes-like object is required, not 'str'

 

It has something to do with the antique kernel of dreamboxes.

 

ET8500 for example has kernel 3.8.7 and that is no problem.

 

Something in the source of the kernel must be adapted..but what?

[Beeker]

Why bother? Dreamboxes are no longer actively supported. Builds are only made if possible... Now a perfect time to abandon Dreamboxes completely. Turn off support, adjust OpenPli homepage, remove the Dreambox feeds and done.... Problem solved...

 

Yes it's partytime for  dreambox haters.

 

Just wait. When openpli-dev's update OE-core it's game over..

 

Well i think it's game over for dreamboxes anyway..This problem solved or not..

Edited by Beeker, 3 July 2016 - 12:34.

[betacentauri]

Does Python part of enigma2 work with python3??
I think I heard years ago that eg "print a" is not working any longer in Python 3. You need to call "print(a)". Is that right?

[Beeker]

Python 2.7.11 is still present in image.

 

All plugins still working.

 

I far as i know. only bitbake has moved to python 3 and some other packages in build environment.

 

But no problem with E2 so far.

Edited by Beeker, 3 July 2016 - 13:09.

[zeros]

For utf-8 support is needed newer Python version than the existing 2.7.3
Python-3.5.1 - it would be OK.

[Beeker]

Bitbake is now python 3.5.1. That's the problem. At least for dreambox. Other boxes(not all tested) build fine without local changes in openembedded-core.

 

Kernel is too old (3.2)...

 

Thus it needs a backport patch or something else is wrong.

Edited by Beeker, 3 July 2016 - 13:41.

[Erik Slagter]

I don't think this has anything to do with either kernels, dreambox drivers, python versions. "Something" is splitting "something" (apparently something that should be interpreted as text). This "something" contains non-UTF-8 encoded characters (probably latin-1, but who knows). But the "something" that is splitting the "something" assumes UTF-8 encoding, and yes, UTF-8 tokens can never start with bit 7 set, they're always a continuation of a string of tokens that started earlier (or an explicit start token).

 

So, the solution is simply to use the correct encoding, either in the "something" text or in the "something" that processes the "something".