1177 replies to this topic

[dax]

I have not tested solo2 build. If I find some time I will test. Maybe something is missing in VU BSP layer.

I'm testing now from scratch

[dax]

Ok, building from scratch (just a backup of sources dir) on archlinux machine for solo2

ERROR: openpli-enigma2-image-1.0-r0 do_image_ubi: Function failed: do_image_ubi (log file is located at /home/davide/openpli/openpli-next/build/tmp/work/vusolo2-oe-linux/openpli-enigma2-image/1.0-r0/temp/log.do_image_ubi.2721)
ERROR: Logfile of failure stored in: /home/davide/openpli/openpli-next/build/tmp/work/vusolo2-oe-linux/openpli-enigma2-image/1.0-r0/temp/log.do_image_ubi.2721
Log data follows:
| DEBUG: Executing python function set_image_size
| DEBUG: Python function set_image_size finished
| DEBUG: Executing shell function do_image_ubi
| ubinize: volume size was not specified in section "ubifs", assume minimum to fit image "/home/davide/openpli/openpli-next/build/tmp/work/vusolo2-oe-linux/openpli-enigma2-image/1.0-r0/deploy-openpli-enigma2-image-image-complete/openpli-enigma2-5-vusolo2.rootfs.ubifs"94724096 bytes (90.3 MiB)
| cp: cannot stat '/home/davide/openpli/openpli-next/build/tmp/deploy/images/vusolo2/openpli-enigma2-5-vusolo2.vmlinux.gz': No such file or directory
| WARNING: /home/davide/openpli/openpli-next/build/tmp/work/vusolo2-oe-linux/openpli-enigma2-image/1.0-r0/temp/run.do_image_ubi.2721:1 exit 1 from 'cp -f /home/davide/openpli/openpli-next/build/tmp/deploy/images/vusolo2/openpli-enigma2-5-vusolo2.vmlinux.gz /home/davide/openpli/openpli-next/build/tmp/work/vusolo2-oe-linux/openpli-enigma2-image/1.0-r0/deploy-openpli-enigma2-image-image-complete/vuplus/solo2/kernel_cfe_auto.bin'
| ERROR: Function failed: do_image_ubi (log file is located at /home/davide/openpli/openpli-next/build/tmp/work/vusolo2-oe-linux/openpli-enigma2-image/1.0-r0/temp/log.do_image_ubi.2721)
ERROR: Task (/home/davide/openpli/openpli-next/meta-openpli/recipes-openpli/images/openpli-enigma2-image.bb:do_image_ubi) failed with exit code '1'
NOTE: Tasks Summary: Attempted 4715 tasks of which 10 didn't need to be rerun and 1 failed.

Summary: 1 task failed:
  /home/davide/openpli/openpli-next/meta-openpli/recipes-openpli/images/openpli-enigma2-image.bb:do_image_ubi

git log
commit 9b01a0443f5946751425b8ef26e43e896b50becd
Merge: 0b07979 47a6556
Author: Erik Slagter <erik@openpli.org>
Date:   Sun Dec 11 15:22:39 2016 +0100

    Merge remote-tracking branch 'origin/master' into master-next

commit 47a65563292c3b71cbcc3e19cb638422b7c949f6
Author: Erik Slagter <erik@openpli.org>
Date:   Sun Dec 11 15:21:12 2016 +0100

    streamproxy: update
    
        commit c0037caea19180e69ae9186dc2d74388f8c30c56
        Author: Erik Slagter <erik@openpli.org>
        Date:   Sun Dec 11 15:17:41 2016 +0100
    
            add VU+ Uno4k support.

commit 43d9c3c3f75d0ba705fd32d62fdb85f8f6ad1929
Merge: 66c5f42 b1ed93c
Author: littlesat <littlesat99@yahoo.com>
Date:   Sat Dec 10 12:45:13 2016 +0100

    Merge pull request #144 from persianpros/master
    
    Update git revs

I have not tested solo2 build. If I find some time I will test. Maybe something is missing in VU BSP layer.

Probably... If you can test for solo2.

[betacentauri]

I can confirm that solo2 build fails. Most likely duo2, solose, zero builds will also fail.

[dax]

Sorry betacentauri but i'm a little bit confused

I also tested today vusolo2, vusolo4k, osminiplus master and master-next builds. VU and Edison have already merged the PR. All builds were successful here.

When you post the build process was ok?

I can confirm that solo2 build fails. Most likely duo2, solose, zero builds will also fail.

Also for you fail due to do_image_ubi?

[betacentauri]

Yup, same error.

 

Mhmm strange . I wrote that, but now it don't work. Perhaps I build solo and not solo2 image. Can't remember and check anymore. Or did I only check PLi4 solo2 build?? I don't know. Sorry, for false evidence.

 

osminiplus, et8500 and vu solo master-next builds work. Just tested again.

[dax]

Don't worry, just for clarity

[gjstroom]

VuSolose build fine over here, I have IMGDEPLOYDIR_forcevariable = "${DEPLOY_DIR_IMAGE}" added to local.conf

Now trying Solo2...

Edited by gjstroom, 11 December 2016 - 23:23.

[gjstroom]

VuSolose build fine over here, I have IMGDEPLOYDIR_forcevariable = "${DEPLOY_DIR_IMAGE}" added to local.conf

Now trying Solo2...

Solo2 build also OK.

[betacentauri]

Yes, with this variable set. But we don't want to use it.

[dax]

Yes, with this variable set. But we don't want to use it.

[christophecvr]

Yes, with this variable set. But we don't want to use it.

On this point you're right of not using it since it does break updated builds.

 

Just a review off all location at start needs to be done this before the tasks rootfs and ubinize are done

[mirakels]

my guess then would be that redefining the IMGDEPLYDIR is not the optimal solution,

and it is worthwhile investigating if http://forums.openpl...ndpost&p=624919

can be used for other images than vuduo2 too (with maybe some tweaking).

[betacentauri]

I guess some little tweakings are needed for solo2, duo2,.. boxes.

[foxbob]

Build all vu+ box is Ok.

[betacentauri]

But only with IMGDEPLOYDIR_forcevariable = .... Or? Did you test master-next?

[Erik Slagter]

We now have the weird situation that we need to run the build twice, once with the force variable and once without, because the bsp's that have been adapted, won't build succesfully WITH the workaround...

[frimmino]

hi, but when it will be released the new OpenPLi 5.0 for dreambox 8000 original ?

[littlesat]

O.M.G.

[betacentauri]

I tried to fix solo2 problem. But first try was not successful

[Erik Slagter]

Still very good to hear you're having a look at it