Error compiling image

angelofsky1980

BlackHole Driver Specialist
Hello,

Yes i get same now, since yesteray , compilation is ok if you take any ubuntu release but prior to 12.04

But ... i can not still figure out why

Code:
ERROR: Function failed: do_fetch (see /home/linux/openvuplus/build/vuduo2/tmp/work/mips32el-oe-linux/opera-hbbtv/opera-hbbtv-0.2-r2_20150622_0/temp/log.do_fetch.13327 for further information)
ERROR: Logfile of failure stored in: /home/linux/openvuplus/build/vuduo2/tmp/work/mips32el-oe-linux/opera-hbbtv/opera-hbbtv-0.2-r2_20150622_0/temp/log.do_fetch.13327
Log data follows:
| ERROR: Function failed: do_fetch (see /home/linux/openvuplus/build/vuduo2/tmp/work/mips32el-oe-linux/opera-hbbtv/opera-hbbtv-0.2-r2_20150622_0/temp/log.do_fetch.13327 for further information)
| cp: cannot stat `/home/linux/openvuplus/resource/sources/opera-hbbtv_20150622_0.tar.gz': No such file or directory
[/ccode]

Where is the password ? ...

[code]
do_fetch() {
   if [ ! -e ${DL_DIR}/${SRC_FILE} -a -e /etc/vuplus_browser.pwd ]; then
sshpass -f /etc/vuplus_browser.pwd sftp -o StrictHostKeyChecking=no guestuser@code.vuplus.com << +
get ${SRC_FILE}

=> -f option is for password file ... empty one or just 1st line as anonymous or same "guestuser" are not working ...

And without this, there is no way to retreive the file.

I suggest to ask directly to Vu+ via www.vuplus.com
 

Souldream

Vu+ Newbie
Code:
sftp -o StrictHostKeyChecking=no guestuser@code.vuplus.com

Code:
~/openvuplus# sftp -o StrictHostKeyChecking=no guestuser@code.vuplus.com
guestuser@code.vuplus.com's password:
Permission denied, please try again.
guestuser@code.vuplus.com's password:
Permission denied, please try again.
guestuser@code.vuplus.com's password:
Permission denied (publickey,password).

I try anonymous, empty pwd, guestuser , vuplus ... all are rejected and no way to download the file.
 

Souldream

Vu+ Newbie
when i brought many years ago an Elanvision from Marusys ... i was not happy.
The box was REALLY far to be finished and high priced.
They closed official forum and let user on road.....
When they released UFS 910 .... external friends needed to release Kofolas to make ******* works on their box.

Enigma2 has been done external ... but hardware problem was there on UFS 910 ( 5w / smartcard .... and reboot box with green BSOD ), they always claimed this was ST drivers.

I have not followed them over 920 .... and i waitted to get a DUO².
But as i see they do not care about DEV ... only be able to L33ch works from Dream Multimedia ...... hoo and i forget ... is this too hard to update Bitbake to make it work on last linux distribution ?? No .... but seems Marusys , it is !
Like taking nearly 1 week to reply to 1 email and give what ? few letters for a guestaccount .... either not taking time to just a reply like => thanks for your inquieries, we forwarded to our technical dpt ....

Morality => if you can do the little things, you can do the big things as well

If monday i have no reply from them ... Marusys will be black listed for my all next and future buys !

Let's make the wheel turn ....
 

angelofsky1980

BlackHole Driver Specialist
when i brought many years ago an Elanvision from Marusys ... i was not happy.
The box was REALLY far to be finished and high priced.
They closed official forum and let user on road.....
When they released UFS 910 .... external friends needed to release Kofolas to make ******* works on their box.

Enigma2 has been done external ... but hardware problem was there on UFS 910 ( 5w / smartcard .... and reboot box with green BSOD ), they always claimed this was ST drivers.

I have not followed them over 920 .... and i waitted to get a DUO².
But as i see they do not care about DEV ... only be able to L33ch works from Dream Multimedia ...... hoo and i forget ... is this too hard to update Bitbake to make it work on last linux distribution ?? No .... but seems Marusys , it is !
Like taking nearly 1 week to reply to 1 email and give what ? few letters for a guestaccount .... either not taking time to just a reply like => thanks for your inquieries, we forwarded to our technical dpt ....

Morality => if you can do the little things, you can do the big things as well

If monday i have no reply from them ... Marusys will be black listed for my all next and future buys !

Let's make the wheel turn ....

LOL!
Your post is amazing and funny!

You wrote about illegal things (not welcome here).
You wrote about other manufacturer (not supported here).
You wrote about people who leech other work ... you are wrong again and you don't know NOTHING about Open Source software.

Other things are out of my control (Vu+ Dev Team replies for example) so if you want to "blacklist" Vu+ you are free to do but please not be a moralist or turn over your decision on this Board because you are in the wrong place.
 

Souldream

Vu+ Newbie
LOL!
Your post is amazing and funny!

You wrote about illegal things (not welcome here).
You wrote about other manufacturer (not supported here).
You wrote about people who leech other work ... you are wrong again and you don't know NOTHING about Open Source software.

Other things are out of my control (Vu+ Dev Team replies for example) so if you want to "blacklist" Vu+ you are free to do but please not be a moralist or turn over your decision on this Board because you are in the wrong place.


Yes sorry, seems i am the wrong place, i thought you was the OFFICIAL board for VU+ but seems i am wrong, good point to explain me this.

So VU+ seems having not official support board, that's the point.

Then for ->

-> Illegal things, speaking about Soft ware ... do you think really VU+ will be sold like any others enigma2 without it ? Time to stop hypocrisis.... and speaking about , doesn't mean we Use or Promote them .... this is your rules , ok but i have not infringed them ... no link, no bin and do not promote them, just explained a situation .... seems you jumped quite fast on this .. ok
-> Others manufacturers , really ? Check your deep source ! Or i think you missed something around ....
-> Open source in 1 way ? Taking in one way and ... ok ... if this is your "open source" way to see how things are going ...
Where are source for XBMC ? Haa yes This is "Closed source"
Yes why not, take source from others, make them closed and release a binary tree open on git ?

Finally this is the Selling Dpt replied with a good =>

Dear Sir,


Many thanks for your request.

We will get back to you soon after verifying this matter.


Thank you and Best Regards.,

Vu+ Team

No worry, this is my last post about VU+ box !
 

angelofsky1980

BlackHole Driver Specialist
Yes sorry, seems i am the wrong place, i thought you was the OFFICIAL board for VU+ but seems i am wrong, good point to explain me this.

So VU+ seems having not official support board, that's the point.

Then for ->

-> Illegal things, speaking about Soft ware ... do you think really VU+ will be sold like any others enigma2 without it ? Time to stop hypocrisis.... and speaking about , doesn't mean we Use or Promote them .... this is your rules , ok but i have not infringed them ... no link, no bin and do not promote them, just explained a situation .... seems you jumped quite fast on this .. ok
-> Others manufacturers , really ? Check your deep source ! Or i think you missed something around ....
-> Open source in 1 way ? Taking in one way and ... ok ... if this is your "open source" way to see how things are going ...
Where are source for XBMC ? Haa yes This is "Closed source"
Yes why not, take source from others, make them closed and release a binary tree open on git ?

Finally this is the Selling Dpt replied with a good =>



No worry, this is my last post about VU+ box !

Vu+ is a STB manufacturer. The manufacturer releases their official image and a lot of third-party images and Teams exists.
BH (and this Board) is a third-party Team: we support only Vu+ genuine boxes and Vu+ authorized rebrand company like GI (in Announcements sections I remember a post about that).
Other Teams can support more than one manufacturer: it's their choice.

About illegal software: we don't want anything related to them here. Support, talk, references, software, correlated plugins, configs, etc. It's quite clear into our Rules. We are not hypocrites: we don't want them here. There are A LOT of websites where can talk about them.

About other manufacturers: I've been looked into sources and there is no secrets: the main code (whitin September 2011 IT WAS OPEN SOURCE - if I remember correctly - and next the Enigma2 project changed to CLOSED SOURCE) was made by DMM. Vu+ has took the LATEST OPEN SOURCE code from DMM git, has published it to their git server fully avaiable for everyone as requested by License. Same thing has done with OE.

About open source: if you have take a look correctly in the sources, you can get XBMC sources without issues. I've downloaded them without issues only reading the .bb file related to XBMC.

Again, don't spam your time trying to make a flame ....
 

gggabcsi

Vu+ Newbie
Hi Guys,
Going to build image, but stucked at this error
can somebody look at this, is there any solution for this?
Thank you in advance for the support.

using the following method:

git clone git://code.vuplus.com/git/openvuplus.git
make image MACHINE=vusolo2

Code:
ERROR: Error executing a python function in /root/openvuplus/openembedded-core/meta/recipes-devtools/quilt/quilt-native_0.51.bb:
OSError: [Errno 2] No such file or directory

ERROR: The stack trace of python calls that resulted in this exception/failure was:
ERROR:  File "relocatable_binaries_preprocess", line 6, in <module>
ERROR:
ERROR:  File "relocatable_binaries_preprocess", line 3, in relocatable_binaries_preprocess
ERROR:
ERROR:  File "relocatable.bbclass", line 7, in rpath_replace
ERROR:
ERROR:  File "relocatable.bbclass", line 36, in process_dir
ERROR:
ERROR:  File "/usr/lib/python2.7/subprocess.py", line 710, in __init__
ERROR:  errread, errwrite)
ERROR:
ERROR:  File "/usr/lib/python2.7/subprocess.py", line 1335, in _execute_child
ERROR:  raise child_exception
ERROR:
ERROR: The code that was being executed was:
ERROR:  0002:def relocatable_binaries_preprocess(d):
ERROR:  0003:  rpath_replace(d.expand('/root/openvuplus/build/vusolo2/tmp/work/x86_64-linux/quilt-native/quilt-native-0.51-r1/sysroot-destdir/'), d)
ERROR:  0004:
ERROR:  0005:
ERROR:  *** 0006:relocatable_binaries_preprocess(d)
ERROR:  0007:
ERROR: (file: 'relocatable_binaries_preprocess', lineno: 6, function: <module>)
ERROR:  0001:
ERROR:  0002:def relocatable_binaries_preprocess(d):
ERROR:  *** 0003:  rpath_replace(d.expand('/root/openvuplus/build/vusolo2/tmp/work/x86_64-linux/quilt-native/quilt-native-0.51-r1/sysroot-destdir/'), d)
ERROR:  0004:
ERROR:  0005:
ERROR:  0006:relocatable_binaries_preprocess(d)
ERROR:  0007:
ERROR: (file: 'relocatable_binaries_preprocess', lineno: 3, function: relocatable_binaries_preprocess)
ERROR: Function failed: relocatable_binaries_preprocess
 

bpwats

Vu+ Newbie
Hello trying to compile the image for Duo 4k from latest Git repo on latest stable Ubuntu 18.
Is there a bright mind that can help with this?

TIA

Code:
bryan@Vader-Bionic:~/openvuplus_3.0$ make image MACHINE=vuduo4k
[*] Building image for vuduo4k
NOTE: Your conf/bblayers.conf has been automatically updated.
WARNING: Unable to get checksum for libtinyxml-native SRC_URI entry tinyxml.pc: file could not be found                                                                                       | ETA:  00:00:13
NOTE: glibc can't be built with -Os, -Os -Wno-error will be used instead.####################################################################################################                 | ETA:  00:00:02
NOTE: glibc can't be built with -Os, -Os -Wno-error will be used instead.
Parsing recipes: 100% |#######################################################################################################################################################################| Time: 00:00:28
Parsing of 1981 .bb files complete (0 cached, 1981 parsed). 2496 targets, 419 skipped, 0 masked, 0 errors.
NOTE: Resolving any missing task queue dependencies

Build Configuration:
BB_VERSION        = "1.27.0"
BUILD_SYS         = "x86_64-linux"
NATIVELSBSTRING   = "Ubuntu-18.04"
TARGET_SYS        = "arm-oe-linux-gnueabi"
MACHINE           = "vuduo4k"
DISTRO            = "vuplus"
DISTRO_VERSION    = "3.0.0"
TUNE_FEATURES     = "arm armv7a vfp neon callconvention-hard"
TARGET_FPU        = "vfp-neon"
meta-bsp         
meta-openvuplus   = "master:dc3e18c06a24020d8750c9c4bb20aa5308a698eb"
meta-oe           
meta-networking   
meta-multimedia   
meta-filesystems 
meta-python       = "(HEADdetachedatff3c52f44):ff3c52f44da3cd8c2e350677c85d161b9819ddcc"
meta              = "(HEADdetachedat7ffe10df73):7ffe10df73cc20d10fcd41b121074445273bd60e"

NOTE: Preparing RunQueue
NOTE: Executing SetScene Tasks
NOTE: Executing RunQueue Tasks
ERROR: Function failed: do_compile (log file is located at /home/bryan/openvuplus_3.0/build/vuduo4k/tmp/work/x86_64-linux/automake-native/automake-native-1.15-r0/temp/log.do_compile.32584)
ERROR: Logfile of failure stored in: /home/bryan/openvuplus_3.0/build/vuduo4k/tmp/work/x86_64-linux/automake-native/automake-native-1.15-r0/temp/log.do_compile.32584
Log data follows:
| DEBUG: Executing shell function do_compile
| NOTE: make -j 4
| : && /bin/mkdir -p doc && { PATH='/home/bryan/openvuplus_3.0/build/vuduo4k/tmp/work/x86_64-linux/automake-native/automake-native-1.15-r0/build/t/wrap:'$PATH && export PATH; } && /usr/bin/perl /home/bryan/openvuplus_3.0/build/vuduo4k/tmp/work/x86_64-linux/automake-native/automake-native-1.15-r0/automake-1.15/doc/help2man --output=doc/automake-1.15.1 automake-1.15
| help2man: can't get `--help' info from automake-1.15
| Try `--no-discard-stderr' if option outputs to stderr
| Makefile:3687: recipe for target 'doc/automake-1.15.1' failed
| make: *** [doc/automake-1.15.1] Error 255
| ERROR: oe_runmake failed
| WARNING: exit code 1 from a shell command.
| ERROR: Function failed: do_compile (log file is located at /home/bryan/openvuplus_3.0/build/vuduo4k/tmp/work/x86_64-linux/automake-native/automake-native-1.15-r0/temp/log.do_compile.32584)
ERROR: Task 557 (virtual:native:/home/bryan/openvuplus_3.0/openembedded-core/meta/recipes-devtools/automake/automake_1.15.bb, do_compile) failed with exit code '1'
NOTE: Tasks Summary: Attempted 185 tasks of which 181 didn't need to be rerun and 1 failed.
NOTE: Writing buildhistory

Summary: 1 task failed:
  virtual:native:/home/bryan/openvuplus_3.0/openembedded-core/meta/recipes-devtools/automake/automake_1.15.bb, do_compile
Summary: There was 1 WARNING message shown.
Summary: There was 1 ERROR message shown, returning a non-zero exit code.
Makefile:154: recipe for target 'image' failed
make: *** [image] Error 1
 

Ev0

Admin
Hello trying to compile the image for Duo 4k from latest Git repo on latest stable Ubuntu 18.
Is there a bright mind that can help with this?

Probably your Ubuntu is too new.

I use 12.04.5LTS to build BH
 

reaper7

Vu+ Newbie
Few days ago I bought duo4k and I also have problem with build image for this device,
looks similar as @bpwats say:
Code:
$ make image MACHINE=vuduo4k
[*] Building image for vuduo4k
NOTE: Your conf/bblayers.conf has been automatically updated.
WARNING: Unable to get checksum for libtinyxml-native SRC_URI entry tinyxml.pc: file could not be found       | ETA:  00:00:30
NOTE: glibc can't be built with -Os, -Os -Wno-error will be used instead.########                             | ETA:  00:00:18
NOTE: glibc can't be built with -Os, -Os -Wno-error will be used instead.
Parsing recipes: 100% |#######################################################################################| Time: 00:00:56
Parsing of 1981 .bb files complete (0 cached, 1981 parsed). 2496 targets, 419 skipped, 0 masked, 0 errors.
NOTE: Resolving any missing task queue dependencies

Build Configuration:
BB_VERSION        = "1.27.0"
BUILD_SYS         = "x86_64-linux"
NATIVELSBSTRING   = "Ubuntu-18.04"
TARGET_SYS        = "arm-oe-linux-gnueabi"
MACHINE           = "vuduo4k"
DISTRO            = "vuplus"
DISTRO_VERSION    = "3.0.0"
TUNE_FEATURES     = "arm armv7a vfp neon callconvention-hard"
TARGET_FPU        = "vfp-neon"
meta-bsp         
meta-openvuplus   = "master:7d1731f7951314527c250a33463cc38843dcfc6b"
meta-oe           
meta-networking   
meta-multimedia   
meta-filesystems 
meta-python       = "(HEADdetachedatff3c52f44):ff3c52f44da3cd8c2e350677c85d161b9819ddcc"
meta              = "(HEADdetachedat7ffe10df73):7ffe10df73cc20d10fcd41b121074445273bd60e"

NOTE: Preparing RunQueue
NOTE: Executing SetScene Tasks
NOTE: Executing RunQueue Tasks
ERROR: Function failed: do_compile (log file is located at /opt/projects/openvuplus_3.0/build/vuduo4k/tmp/work/x86_64-linux/automake-native/automake-native-1.15-r0/temp/log.do_compile.11556)
ERROR: Logfile of failure stored in: /opt/projects/openvuplus_3.0/build/vuduo4k/tmp/work/x86_64-linux/automake-native/automake-native-1.15-r0/temp/log.do_compile.11556
Log data follows:
| DEBUG: Executing shell function do_compile
| NOTE: make -j 4
| : && /bin/mkdir -p doc && { PATH='/opt/projects/openvuplus_3.0/build/vuduo4k/tmp/work/x86_64-linux/automake-native/automake-native-1.15-r0/build/t/wrap:'$PATH && export PATH; } && /usr/bin/perl /opt/projects/openvuplus_3.0/build/vuduo4k/tmp/work/x86_64-linux/automake-native/automake-native-1.15-r0/automake-1.15/doc/help2man --output=doc/automake-1.15.1 automake-1.15
| help2man: can't get `--help' info from automake-1.15
| Try `--no-discard-stderr' if option outputs to stderr
| Makefile:3687: recipe for target 'doc/automake-1.15.1' failed
| make: *** [doc/automake-1.15.1] Error 255
| ERROR: oe_runmake failed
| WARNING: exit code 1 from a shell command.
| ERROR: Function failed: do_compile (log file is located at /opt/projects/openvuplus_3.0/build/vuduo4k/tmp/work/x86_64-linux/automake-native/automake-native-1.15-r0/temp/log.do_compile.11556)
ERROR: Task 557 (virtual:native:/opt/projects/openvuplus_3.0/openembedded-core/meta/recipes-devtools/automake/automake_1.15.bb, do_compile) failed with exit code '1'
NOTE: Tasks Summary: Attempted 110 tasks of which 106 didn't need to be rerun and 1 failed.
NOTE: Writing buildhistory

Summary: 1 task failed:
  virtual:native:/opt/projects/openvuplus_3.0/openembedded-core/meta/recipes-devtools/automake/automake_1.15.bb, do_compile
Summary: There was 1 WARNING message shown.
Summary: There was 1 ERROR message shown, returning a non-zero exit code.
Makefile:154: recipe for target 'image' failed
make: *** [image] Error 1

We have new receivers, new systems in computers, time runs forward...

Maybe just toolchain is too old?? not main system on PC?

You can not require users to install archaic systems to build the image for receivers from 2018 year

Time to refresh toolchain
 

Ev0

Admin
You can not require users to install archaic systems to build the image for receivers from 2018 year

Time to refresh toolchain
We don't.

We build and post the images so you don't need to do anything.

If you want to build them yourself, then you have to use the older systems.
 
Top