1177 replies to this topic

[Taapat]

I see in my git that I had a problem directly on 3.1.3, and this patch fix this problem.

 

But I wanted to add that I have not checked how works current master-next.

I see that just now oe is updated.

But still it is possible that I have a newer oe version, so on the master-next missing something else.

[MastaG]

Ah thanks Taapat, the patch fixed ffmpeg for me.

I've also ported xtrend's softfloat kernel patches to linux 2.6.18 (patching all the assembler fpu entries for binutils 2.5+).
This seem to have fixed the one time kernel panic as well

I now have PLi-5 running on the DM800HD (still with glibc downgraded to 2.19).

Fun times

[Taapat]

I've also ported xtrend's softfloat kernel patches to linux 2.6.18

 

And what does it mean?

You can compile a kernel 2.6.18 with gcc 6 without errors?

[MastaG]

I haven't tried that yet.
I forgot to mention I'm also still using gcc 4.9.
I'll focus on gcc 6.0 later this week :-)

The assembler refactoring based on xtrends softfloat patch was required for binutils only.

[Akki]

Hi

 

Do you have problems building a PLI 5 Image?

 

In the end always get this error:

ERROR: openpli-enigma2-image-1.0-r0 do_image_ubi: Function failed: do_image_ubi (log file is located at /home/akki/openatv/openpli-oe-core/build/tmp/work/vuduo2-oe-linux/openpli-enigma2-image/1.0-r0/temp/log.do_image_ubi.17334)
ERROR: Logfile of failure stored in: /home/akki/openatv/openpli-oe-core/build/tmp/work/vuduo2-oe-linux/openpli-enigma2-image/1.0-r0/temp/log.do_image_ubi.17334
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/akki/openatv/openpli-oe-core/build/tmp/work/vuduo2-oe-linux/openpli-enigma2-image/1.0-r0/deploy-openpli-enigma2-image-image-complete/openpli-enigma2-5-vuduo2.rootfs.ubifs"98787328 bytes (94.2 MiB)
| cp: cannot stat '/home/akki/openatv/openpli-oe-core/build/tmp/deploy/images/vuduo2/openpli-enigma2-5-vuduo2.rootfs.ubi': No such file or directory
| WARNING: /home/akki/openatv/openpli-oe-core/build/tmp/work/vuduo2-oe-linux/openpli-enigma2-image/1.0-r0/temp/run.do_image_ubi.17334:1 exit 1 from 'cp /home/akki/openatv/openpli-oe-core/build/tmp/deploy/images/vuduo2/openpli-enigma2-5-vuduo2.rootfs.ubi /home/akki/openatv/openpli-oe-core/build/tmp/deploy/images/vuduo2/vuplus/duo2/root_cfe_auto.bin'
| ERROR: Function failed: do_image_ubi (log file is located at /home/akki/openatv/openpli-oe-core/build/tmp/work/vuduo2-oe-linux/openpli-enigma2-image/1.0-r0/temp/log.do_image_ubi.17334)
ERROR: Task (/home/akki/openatv/openpli-oe-core/meta-openpli/recipes-openpli/images/openpli-enigma2-image.bb:do_image_ubi) failed with exit code '1'
NOTE: Tasks Summary: Attempted 4440 tasks of which 10 didn't need to be rerun and 1 failed.

Summary: 1 task failed:
  /home/akki/openatv/openpli-oe-core/meta-openpli/recipes-openpli/images/openpli-enigma2-image.bb:do_image_ubi
Summary: There were 31 WARNING messages shown.
Summary: There was 1 ERROR message shown, returning a non-zero exit code.
Makefile:89: die Regel für Ziel „image“ scheiterte
make: *** [image] Fehler 1
akki@akki-VirtualBox:~/openatv/openpli-oe-core$ 

[Taapat]

@Akki try somting similar: https://github.com/T...fc317aa8b969b79

[athoik]

So it's the DEPLOY_DIR_IMAGE that doesn't work any more?

meta-openpli/conf/distro/openpli.conf:DEPLOY_DIR_IMAGE = "${DEPLOY_DIR}/images/${MACHINE}"
bitbake/conf/bitbake.conf:DEPLOY_DIR_IMAGE = "${DEPLOY_DIR}/images"

I guess bitbake.conf needs DEPLOY_DIR_IMAGE ?= "${DEPLOY_DIR}/images" in order to be able to override?

[athoik]

It should be this one:
 

openembedded-core/meta/classes/image.bbclass:IMGDEPLOYDIR = "${WORKDIR}/deploy-${PN}-image-complete"

Changing IMGDEPLOYDIR = "${DEPLOY_DIR_IMAGE}" might do.

Edit1. It works...
 

diff --git a/meta-openpli/conf/distro/openpli.conf b/meta-openpli/conf/distro/openpli.conf
index bc0556c..adb1e9a 100644
--- a/meta-openpli/conf/distro/openpli.conf
+++ b/meta-openpli/conf/distro/openpli.conf
@@ -20,6 +20,7 @@ IMAGE_LINK_NAME = ""
 CACHE ?= "${TMPDIR}/cache/${LIBC}/${MACHINE}"
 DEPLOY_DIR ?= "${TMPDIR}/deploy/${LIBC}"
 DEPLOY_DIR_IMAGE = "${DEPLOY_DIR}/images/${MACHINE}"
+IMGDEPLOYDIR = "${DEPLOY_DIR_IMAGE}"

 VIRTUAL-RUNTIME_dev_manager = "busybox-mdev"
 VIRTUAL-RUNTIME_login_manager = "busybox"

.....

diff --git a/meta/classes/image.bbclass b/meta/classes/image.bbclass
index 6111f6d..5cb6838 100644
--- a/meta/classes/image.bbclass
+++ b/meta/classes/image.bbclass
@@ -74,7 +74,7 @@ IMAGE_INSTALL[type] = "list"
 export PACKAGE_INSTALL ?= "${IMAGE_INSTALL} ${ROOTFS_BOOTSTRAP_INSTALL} ${FEATURE_INSTALL}"
 PACKAGE_INSTALL_ATTEMPTONLY ?= "${FEATURE_INSTALL_OPTIONAL}"

-IMGDEPLOYDIR = "${WORKDIR}/deploy-${PN}-image-complete"
+IMGDEPLOYDIR ?= "${WORKDIR}/deploy-${PN}-image-complete"

 # Images are generally built explicitly, do not need to be part of world.
 EXCLUDE_FROM_WORLD = "1"

Edit2. Some commits in openembedded if someone can find a better solution.

commit 93631befe8b962bf99524746b49f4ebca336175c
Author: Joshua Lock <joshua.g.lock@intel.com>
Date:   Wed Oct 12 21:46:41 2016 +0100

    Remove RM_OLD_IMAGE, it's no longer useful

    Since the move to put image deployment under sstate control in
    d54339d4b1a7e884de636f6325ca60409ebd95ff old images are automatically
    removed before a new image is deployed (the default behaviour of the
    sstate logic).

    RM_OLD_IMAGE is therefore no longer required to provide this
    behaviour, remove the variable and its users.

    Signed-off-by: Joshua Lock <joshua.g.lock@intel.com>
    Signed-off-by: Ross Burton <ross.burton@intel.com>

commit d54339d4b1a7e884de636f6325ca60409ebd95ff
Author: Ed Bartosh <ed.bartosh@linux.intel.com>
Date:   Thu Sep 1 11:56:01 2016 +0300

    image.bbclass: Put image_complete under sstate control

    Adding image_complete task should make sstate machinery
    to generate manifest for deployed images and do final
    deployment to DEPLOY_DIR_IMAGE.

    Made sure IMGDEPLOYDIR doesn't contain images from past deployments
    to prevent them to be included into sstate manifests.

    Set stamp-extra-info flag for do_image_complete task. This flag
    is used in the name of sstate manifest. Setting it to predetermined
    value for image_complete should help to get correct manifest
    filenames when processing runQueueTask events.

    Signed-off-by: Ed Bartosh <ed.bartosh@linux.intel.com>
    Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>

commit 6d969bacc718e21a5246d4da9bf9639dcae29b02
Author: Ed Bartosh <ed.bartosh@linux.intel.com>
Date:   Thu Sep 1 11:56:00 2016 +0300

    image: Deploy images to IMGDEPLOYDIR

    Changed deployment directory from DEPLOY_DIR_IMAGE to
    IMGDEPLOYDIR to make sstate machinery to do final deployment and
    generate manifest.

    Renamed variable deploy_dir to deploy_dir_image in selftest code
    to avoid confusion with DEPLOYDIR variable.

    Updated the code of rootfs.py:Rootfs class to use IMGDEPLOYDIR variable
    as it's now used as a new deployment destination.

    Signed-off-by: Ed Bartosh <ed.bartosh@linux.intel.com>
    Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>

commit 8969b885044eb46dba3dbf62a0243aef673443d3
Author: Ed Bartosh <ed.bartosh@linux.intel.com>
Date:   Wed Aug 31 14:02:50 2016 +0300

    image/populate_sdk_base: Add *DEPLOYDIR variables

    This is a preparation for changing deployment directory for image
    and populate_sdk targets.

    Introduced new variables, IMGDEPLOYDIR and SDKDEPLOYDIR. Set it to current
    image/sdk deployment locations.

    Signed-off-by: Ed Bartosh <ed.bartosh@linux.intel.com>
    Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>

Edited by athoik, 8 November 2016 - 18:14.

[seroga]

IMGDEPLOYDIR = "${DEPLOY_DIR_IMAGE}"

It works, thanks!

[Akki]

Thanks @Taapat and @athoik, after changing the files was the build up to the circuit without error.

 

These changes should be taken over by the Devs in the master-next branch,
So that you get no errors.

[blzr]

alternatively, to avoid touching oe submodule bbclass, openpli.conf could be adjusted like this:

diff --git a/meta-openpli/conf/distro/openpli.conf b/meta-openpli/conf/distro/openpli.conf
index bc0556c..7d05ab9 100644
--- a/meta-openpli/conf/distro/openpli.conf
+++ b/meta-openpli/conf/distro/openpli.conf
@@ -20,6 +20,7 @@ IMAGE_LINK_NAME = ""
 CACHE ?= "${TMPDIR}/cache/${LIBC}/${MACHINE}"
 DEPLOY_DIR ?= "${TMPDIR}/deploy/${LIBC}"
 DEPLOY_DIR_IMAGE = "${DEPLOY_DIR}/images/${MACHINE}"
+IMGDEPLOYDIR_forcevariable = "${DEPLOY_DIR_IMAGE}"
 
 VIRTUAL-RUNTIME_dev_manager = "busybox-mdev"
 VIRTUAL-RUNTIME_login_manager = "busybox"

however I guess default image.bbclass assignment should be weaken indeed, to allow override it in layers
(btw, I somehow thought you can simply override even hard assignment in distro.conf, and it turned out you can't /without forcing/ in this case?)

Edited by blzr, 8 November 2016 - 20:11.

[parageria]

hi

i am a new man for compile - build images

but

i make my openpli 5 image for dm800se without errors and works.

the only problem is samba ....a try to compile samba 3.0.37.r9 without success

i compile samba 3.6.25 with success (from oe-alliance recipes) i can see my ext4 hdd (usb) from my pc

but i cant access it (connection refused)

 

if there is any help  (recipes,tricks,patch....)

 

thanks

[fairbird]

Hi all ..

I need recipes to build openopera + hbbtv ?!

I can not found it in core and after build feed I can found plugins on ipk folder !

[parageria]

hi

i am a new man for compile - build images

but

i make my openpli 5 image for dm800se without errors and works.

the only problem is samba ....a try to compile samba 3.0.37.r9 without success

i compile samba 3.6.25 with success (from oe-alliance recipes) i can see my ext4 hdd (usb) from my pc

but i cant access it (connection refused)

 

if there is any help  (recipes,tricks,patch....)

 

thanks

 

OK i make samba to work ( recompile samba package)  recipes from link on post #546

Thanks

[parageria]

 

hi

i am a new man for compile - build images

but

i make my openpli 5 image for dm800se without errors and works.

the only problem is samba ....a try to compile samba 3.0.37.r9 without success

i compile samba 3.6.25 with success (from oe-alliance recipes) i can see my ext4 hdd (usb) from my pc

but i cant access it (connection refused)

 

if there is any help  (recipes,tricks,patch....)

 

thanks

 

 

OK i make samba to work ( rebuild samba package)  recipes from link on post #546

Thanks

Edited by parageria, 8 November 2016 - 21:57.

[fairbird]

@Taapat

How to fix this error please ?!

ERROR: enigma2-plugin-extensions-blurayplayer-1+gitAUTOINC+79f0e54f22-r0 do_compile: python setup.py build execution failed.
ERROR: enigma2-plugin-extensions-blurayplayer-1+gitAUTOINC+79f0e54f22-r0 do_compile: Function failed: do_compile (log file is located at /home/raed/openpli5/openpli-oe-core/build/tmp/work/mips32el-oe-linux/enigma2-plugin-extensions-blurayplayer/1+gitAUTOINC+79f0e54f22-r0/temp/log.do_compile.10536)
ERROR: Logfile of failure stored in: /home/raed/openpli5/openpli-oe-core/build/tmp/work/mips32el-oe-linux/enigma2-plugin-extensions-blurayplayer/1+gitAUTOINC+79f0e54f22-r0/temp/log.do_compile.10536
Log data follows:
| DEBUG: Executing shell function do_compile
| ERROR: python setup.py build execution failed.
| running build
| running build_py
| creating build
| creating build/lib.linux-x86_64-2.7
| creating build/lib.linux-x86_64-2.7/Extensions
| creating build/lib.linux-x86_64-2.7/Extensions/BlurayPlayer
| copying src/BlurayAudioSelection.py -> build/lib.linux-x86_64-2.7/Extensions/BlurayPlayer
| copying src/BlurayUi.py -> build/lib.linux-x86_64-2.7/Extensions/BlurayPlayer
| copying src/BlurayPlayerDirBrowser.py -> build/lib.linux-x86_64-2.7/Extensions/BlurayPlayer
| copying src/plugin.py -> build/lib.linux-x86_64-2.7/Extensions/BlurayPlayer
| copying src/ChangeFunctions.py -> build/lib.linux-x86_64-2.7/Extensions/BlurayPlayer
| copying src/__init__.py -> build/lib.linux-x86_64-2.7/Extensions/BlurayPlayer
| copying src/icon.png -> build/lib.linux-x86_64-2.7/Extensions/BlurayPlayer
| copying src/picon.png -> build/lib.linux-x86_64-2.7/Extensions/BlurayPlayer
| copying src/piconhd.png -> build/lib.linux-x86_64-2.7/Extensions/BlurayPlayer
| running build_ext
| building 'Extensions.BlurayPlayer.blurayinfo' extension
| creating build/temp.linux-x86_64-2.7
| creating build/temp.linux-x86_64-2.7/src
| mipsel-oe-linux-gcc -mel -mabi=32 -mhard-float -march=mips32 --sysroot=/home/raed/openpli5/openpli-oe-core/build/tmp/sysroots/dm800se -DNDEBUG -g -O3 -Wall -Wstrict-prototypes -Os -pipe -g -feliminate-unused-debug-types -fdebug-prefix-map=/home/raed/openpli5/openpli-oe-core/build/tmp/work/mips32el-oe-linux/enigma2-plugin-extensions-blurayplayer/1+gitAUTOINC+79f0e54f22-r0=/usr/src/debug/enigma2-plugin-extensions-blurayplayer/1+gitAUTOINC+79f0e54f22-r0 -fdebug-prefix-map=/home/raed/openpli5/openpli-oe-core/build/tmp/sysroots/x86_64-linux= -fdebug-prefix-map=/home/raed/openpli5/openpli-oe-core/build/tmp/sysroots/dm800se= -fPIC -I/home/raed/openpli5/openpli-oe-core/build/tmp/sysroots/dm800se/usr/include/python2.7 -c src/blurayinfo.c -o build/temp.linux-x86_64-2.7/src/blurayinfo.o
| src/blurayinfo.c: In function 'storeInfo':
| src/blurayinfo.c:96:52: error: 'BLURAY_CLIP_INFO {aka struct bd_clip}' has no member named 'clip_id'
|    clip = _mk_path(tList[pos].clip_id, ti->clips[ii].clip_id);
|                                                     ^
| error: command 'mipsel-oe-linux-gcc' failed with exit status 1
| ERROR: Function failed: do_compile (log file is located at /home/raed/openpli5/openpli-oe-core/build/tmp/work/mips32el-oe-linux/enigma2-plugin-extensions-blurayplayer/1+gitAUTOINC+79f0e54f22-r0/temp/log.do_compile.10536)
ERROR: Task /home/raed/openpli5/openpli-oe-core/meta-openpli/recipes-openpli/enigma2-plugins/enigma2-plugin-extensions-blurayplayer.bb:do_compile (/home/raed/openpli5/openpli-oe-core/meta-openpli/recipes-openpli/enigma2-plugins/enigma2-plugin-extensions-blurayplayer.bb:do_compile) failed with exit code '1'
NOTE: Tasks Summary: Attempted 811 tasks of which 805 didn't need to be rerun and 1 failed.

Summary: 1 task failed:
  /home/raed/openpli5/openpli-oe-core/meta-openpli/recipes-openpli/enigma2-plugins/enigma2-plugin-extensions-blurayplayer.bb:do_compile
Summary: There were 2 ERROR messages shown, returning a non-zero exit code.
raed@fairbird:~/openpli5/openpli-oe-core/build$

[Taapat]

Use actual libbluray from master-nex: https://github.com/O...09b2a8e667f3643

[SpaceRat]

i compile samba 3.6.25 with success (from oe-alliance recipes) i can see my ext4 hdd (usb) from my pc
but i cant access it (connection refused)
 
if there is any help  (recipes,tricks,patch....)

Which configuration do you use for Samba?

The PLi one from 3.0.x (Will likely not work well) or one of those in the oe-a recipe?

You have to be aware that oe-a has pam and Samba-Integration for pam, so changing passwords on the shell on an oe-a image also changes the password for the corresponding Samba user.
The default password for the root user is empty however.

And now to the point:
Samba 3.6.25 brings SMBv2 support to Linux, which wasn't available in Samba 3.0.x.
SMBv1.0 to SMBv2.0 is a huge step and by default, empty passwords are not allowed for SMBv2.

To keep the box wide open (As with previous versions of Samba) and still allow optional secure setups with as few changes as possible, the following "cheat" was used in the oe-a default config:

Default:

[global]
   guest account = root
   security = user
   map to guest = bad user

guest account works with root rights and any bad user gets mapped to guest.

username=root,password=

is not "bad" though, but perfectly correct for the default setup, so it does not get mapped to guest but blocked for having an empty password.

Two options:
1. Use any bullshit credentials instead for full access, e.g. try to login as user "r00t" (Which does not exit -> bad -> mapped to guest = root)
2. Set a (Samba) password for user root, then you can login using username "root" and that newly set password.
You might have to use smbpasswd to set a Samba password, in case the pam integration fails in OpenPLi (It works in oe-a images, there you can simply use passwd to keep Linux and Samba passwords in sync).


And if you change the above part of the default config to

[global]
   guest account = nobody
   security = user
   map to guest = bad user

you will get a secure Samba setup, where only valid logins will lead to success, as the guest account works with the rights of user "nobody" (Make sure it exists!).

[fairbird]

@Taapat

Thank you Solved ...

[parageria]

 

i compile samba 3.6.25 with success (from oe-alliance recipes) i can see my ext4 hdd (usb) from my pc
but i cant access it (connection refused)
 
if there is any help  (recipes,tricks,patch....)

Which configuration do you use for Samba?

The PLi one from 3.0.x (Will likely not work well) or one of those in the oe-a recipe?

You have to be aware that oe-a has pam and Samba-Integration for pam, so changing passwords on the shell on an oe-a image also changes the password for the corresponding Samba user.
The default password for the root user is empty however.

And now to the point:
Samba 3.6.25 brings SMBv2 support to Linux, which wasn't available in Samba 3.0.x.
SMBv1.0 to SMBv2.0 is a huge step and by default, empty passwords are not allowed for SMBv2.

To keep the box wide open (As with previous versions of Samba) and still allow optional secure setups with as few changes as possible, the following "cheat" was used in the oe-a default config:

Default:

[global]
   guest account = root
   security = user
   map to guest = bad user

guest account works with root rights and any bad user gets mapped to guest.

username=root,password=

is not "bad" though, but perfectly correct for the default setup, so it does not get mapped to guest but blocked for having an empty password.

Two options:
1. Use any bullshit credentials instead for full access, e.g. try to login as user "r00t" (Which does not exit -> bad -> mapped to guest = root)
2. Set a (Samba) password for user root, then you can login using username "root" and that newly set password.
You might have to use smbpasswd to set a Samba password, in case the pam integration fails in OpenPLi (It works in oe-a images, there you can simply use passwd to keep Linux and Samba passwords in sync).


And if you change the above part of the default config to

[global]
   guest account = nobody
   security = user
   map to guest = bad user

you will get a secure Samba setup, where only valid logins will lead to success, as the guest account works with the rights of user "nobody" (Make sure it exists!).

 

thank you very match

i take recipes from link post #546, rebuild samba 3.6.25,and install it from my box $opkg install samba-base (my feeds local on pc).its works without problem

Edited by parageria, 9 November 2016 - 13:54.