What's new

Custom / Unofficial Build To my compiler friends

LandRocket

Vuplus-Images Elite
Messages
100
Joined
Apr 5, 2016
Reaction score
29
Points
28
Unfortunately I'm still in the same position :( literally.....

My motor decided to die on me last night and haven't really achieved much. I'm stuck on the 4.0 branch for anything except ATV, I did try modifying the dependencies to use sigc++2, which got rid of the "no package" message but failed miserably to compile :(

Sorry I can't give you any better news.....
 

LandRocket

Vuplus-Images Elite
Messages
100
Joined
Apr 5, 2016
Reaction score
29
Points
28
Well, I got my motor going again......

In the mean time, I did go into my 4.1 branch, and did a "git pull", "make update", "MACHINE=vusolo4k DISTRO=openbh make image" and it got a lot further than before, no message about sigc++1.2 so I do wonder if it's just that there has not been enough code contributed to make a working build of the others yet? Perhaps we are just being too keen? :)

| arm-oe-linux-gnueabi-gcc -march=armv7ve -mfpu=neon-vfpv4 -mfloat-abi=hard -mcpu=cortex-a15 --sysroot=/home/enigma/oealliance/build41/builds/openbh/release/vusolo4k/tmp/work/cortexa15hf-neon-vfpv4-oe-linux-gnueabi/blackholesocker/blackholesocker-0.1-r1/recipe-sysroot -fopenmp -Os -pipe -g -feliminate-unused-debug-types -fdebug-prefix-map=/home/enigma/oealliance/build41/builds/openbh/release/vusolo4k/tmp/work/cortexa15hf-neon-vfpv4-oe-linux-gnueabi/blackholesocker/blackholesocker-0.1-r1=/usr/src/debug/blackholesocker/0.1-r1 -fdebug-prefix-map=/home/enigma/oealliance/build41/builds/openbh/release/vusolo4k/tmp/work/cortexa15hf-neon-vfpv4-oe-linux-gnueabi/blackholesocker/blackholesocker-0.1-r1/recipe-sysroot-native= -fdebug-prefix-map=/home/enigma/oealliance/build41/builds/openbh/release/vusolo4k/tmp/work/cortexa15hf-neon-vfpv4-oe-linux-gnueabi/blackholesocker/blackholesocker-0.1-r1/recipe-sysroot= -Wl,-O1 -Wl,--hash-style=gnu -Wl,--as-needed -o blackholesocker blackholesocker-main.o -fopenmp -lz
| /home/enigma/oealliance/build41/builds/openbh/release/vusolo4k/tmp/work/cortexa15hf-neon-vfpv4-oe-linux-gnueabi/blackholesocker/blackholesocker-0.1-r1/recipe-sysroot-native/usr/bin/arm-oe-linux-gnueabi/../../libexec/arm-oe-linux-gnueabi/gcc/arm-oe-linux-gnueabi/6.3.0/ld: cannot find -lz
| collect2: error: ld returned 1 exit status
| Makefile:358: recipe for target 'blackholesocker' failed

Definately more than before........
 
Last edited:

LandRocket

Vuplus-Images Elite
Messages
100
Joined
Apr 5, 2016
Reaction score
29
Points
28
20170517-OBH11-Solo4K.jpg
Holy smokes Batman!!! - but not without a good fight....

Obviously "ld: cannot find -lz" was my clue... took a look around at /home/enigma/oealliance/build41/builds/openbh/release/vusolo4k/tmp/work/cortexa15hf-neon-vfpv4-oe-linux-gnueabi/blackholesocker/blackholesocker-0.1-r1/blackholesocker/Makefile.am and saw the line referring to LDFLAGS (-lz)

Then ran:
/home/enigma/oealliance/build41/builds/openbh/release/vusolo4k/tmp/work/cortexa15hf-neon-vfpv4-oe-linux-gnueabi/blackholesocker/blackholesocker-0.1-r1/recipe-sysroot-native/usr/bin/arm-oe-linux-gnueabi/../../libexec/arm-oe-linux-gnueabi/gcc/arm-oe-linux-gnueabi/6.3.0/ld --help

Which showed me that the -l command refers to libraries to be included in the linking:

Removed the -lz from the end, and hoped that it would give me further clues as to what library it actually wanted....

Then, it went through!! After all that hassle!!!!

Just proves that on this new trunk, you've either got to be patient, or persistent!!!

UPDATE: openvix-image-5.1 has just built from 4.1 trunk without issue....
 
Last edited:

danny187

Super Moderator
Messages
996
Joined
Feb 23, 2016
Reaction score
320
Points
108
View attachment 17575
Holy smokes Batman!!! - but not without a good fight....

Obviously "ld: cannot find -lz" was my clue... took a look around at /home/enigma/oealliance/build41/builds/openbh/release/vusolo4k/tmp/work/cortexa15hf-neon-vfpv4-oe-linux-gnueabi/blackholesocker/blackholesocker-0.1-r1/blackholesocker/Makefile.am and saw the line referring to LDFLAGS (-lz)

Then ran:
/home/enigma/oealliance/build41/builds/openbh/release/vusolo4k/tmp/work/cortexa15hf-neon-vfpv4-oe-linux-gnueabi/blackholesocker/blackholesocker-0.1-r1/recipe-sysroot-native/usr/bin/arm-oe-linux-gnueabi/../../libexec/arm-oe-linux-gnueabi/gcc/arm-oe-linux-gnueabi/6.3.0/ld --help

Which showed me that the -l command refers to libraries to be included in the linking:

Removed the -lz from the end, and hoped that it would give me further clues as to what library it actually wanted....

Then, it went through!! After all that hassle!!!!

Just proves that on this new trunk, you've either got to be patient, or persistent!!!

UPDATE: openvix-image-5.1 has just built from 4.1 trunk without issue....
Yeah, just built latest OpenATV 6.1 and at about 90% on OpenVIX 5.1.

Don't suppose you have come across a way to make the INTERNAL player on Kodi to play SOUND.

I can install pvr clients but they only utlise internal player, but that has no sound like it has been for over a year on all platform lmao
 

LandRocket

Vuplus-Images Elite
Messages
100
Joined
Apr 5, 2016
Reaction score
29
Points
28
Sorry for the late response, managed to spend the last few days staring at hospital walls :(

Believe it or not, I'm still learning all this, and Kodi is out of my realms at the moment; got it on my PC; haven't really done anything with it's Enigma version. I don't even know if Kodi Enigma was ported/forked/????; I know that with Win, most media apps need access to the DirectSound libraries, and if Kodi Enigma didn't have an equivalent library, then that would be causing the developers a lot of headaches :(

So, as much as I'd love to be able to help at this time, unfortunately, I'm probably not quite able to :(
 

LandRocket

Vuplus-Images Elite
Messages
100
Joined
Apr 5, 2016
Reaction score
29
Points
28
Had an error today on the 4.1 branch (20170530) for VU solo4k that mentioned memcpy not being defined in any scope.

Had to modify ~/oealliance/build41/builds/openbh/release/vusolo4k/tmp/work/cortexa15hf-neon-vfpv4-oe-linux-gnueabi/vuplus-displayvfd/vuplus-displayvfd-1.0-r6/displayvfd/upng.cpp to #include <string.h>

Just for information :)
 

LandRocket

Vuplus-Images Elite
Messages
100
Joined
Apr 5, 2016
Reaction score
29
Points
28
@danny187 don't know if this is of interest to you, but had an email this morning, as I'm subscribed to github openatv feed and it reads:

Issue: Inputstream.Adaptive #705
Can the Peak3d inputstream.adaptive be compiled for Mips to use with Kodi in OpenATV ?

Ive managed to install the Generic Linux version, which then does allow for BBCIplayer 3.xx versions to be installed and then Ive successfully compiled the libssd_wv.so for Mips, however when enabled it still states that its unable to load shared library's, so obviously I'm still missing something.

If the OpenATV Dev's could compile this for our platform, then it would not only allow for DASH streams to be played, which is cool, but more importantly it would allow for the playing of DRM protected content, yes that's correct, DRM, how awesome is that on our E2 boxes ?

Many addons are now starting to use inputstream.adaptive and its sadly missing in our E2 Kodi versions. Ive searched everywhere online for a Mips version, but it just simply does not exist.

---
I would suggest that you have a similar issue when it comes to your internal sound problems, and could be worth investigating to see if you can get any more debug info and see what exactly is stopping the internal player from doing what you want it to?

Just a thought :)
 

danny187

Super Moderator
Messages
996
Joined
Feb 23, 2016
Reaction score
320
Points
108
@danny187 don't know if this is of interest to you, but had an email this morning, as I'm subscribed to github openatv feed and it reads:

Issue: Inputstream.Adaptive #705
Can the Peak3d inputstream.adaptive be compiled for Mips to use with Kodi in OpenATV ?

Ive managed to install the Generic Linux version, which then does allow for BBCIplayer 3.xx versions to be installed and then Ive successfully compiled the libssd_wv.so for Mips, however when enabled it still states that its unable to load shared library's, so obviously I'm still missing something.

If the OpenATV Dev's could compile this for our platform, then it would not only allow for DASH streams to be played, which is cool, but more importantly it would allow for the playing of DRM protected content, yes that's correct, DRM, how awesome is that on our E2 boxes ?

Many addons are now starting to use inputstream.adaptive and its sadly missing in our E2 Kodi versions. Ive searched everywhere online for a Mips version, but it just simply does not exist.

---
I would suggest that you have a similar issue when it comes to your internal sound problems, and could be worth investigating to see if you can get any more debug info and see what exactly is stopping the internal player from doing what you want it to?

Just a thought :)
I have them installed now on my Vu+ Uno4k (ARM) and its made no difference for sound on internal lol.

Install this zip in Kodi, then install from repo and install the input.stream and rmtp

To install PVR

opkg install kodi-addons-meta

Then install pvr clients and try.

Or try and play via internal on any stream.
 

Attachments

danny187

Super Moderator
Messages
996
Joined
Feb 23, 2016
Reaction score
320
Points
108
Anyone had this actual on IMAGE Telnet or SSH (not in ubuntu)
-sh: warning: setlocale: LC_ALL: cannot change locale (C.UTF8): No such file or directory

Any idea how to sort?

Basically I broke my OpenPli and tried with new branch, it messed up and I have a mix / match branch image called "homebuild" but still have Kodi 16.1 so that's cool.
 

storm_breaker

Member
Messages
10
Joined
Nov 11, 2017
Reaction score
1
Points
3
Any idea how i can fix this problem ? (branch 4.1. ubuntu 16.04 up to date )

enigma2/enigma2-1.1+gitAUTOINC+576e6d8608-r0/recipe-sysroot/usr/lib/sigc++-2.0/include -fno-rtti -fno-exceptions -rdynamic -funwind-tables -pthread -fopenmp -MT dvb/frontend.o -MD -MP -MF $depbase.Tpo -c -o dvb/frontend.o dvb/frontend.cpp &&\
| mv -f $depbase.Tpo $depbase.Po
| dvb/dvb.cpp: In constructor 'eDVBUsbAdapter::eDVBUsbAdapter(int)':
| dvb/dvb.cpp:323:16: error: 'DTV_ENUM_DELSYS' was not declared in this scope
| prop[0].cmd = DTV_ENUM_DELSYS;
| ^~~~~~~~~~~~~~~
| dvb/frontend.cpp: In member function 'int eDVBFrontend::eek:penFrontend()':
| dvb/frontend.cpp:702:70: error: 'SYS_DVBC_ANNEX_A' was not declared in this scope
| m_multitype = m_delsys[SYS_DVBS] && (m_delsys[SYS_DVBT] || m_delsys[SYS_DVBC_ANNEX_A]);
| ^~~~~~~~~~~~~~~~
| dvb/frontend.cpp: In member function 'virtual bool eDVBFrontend::setDeliverySystem(const char*)':
| dvb/frontend.cpp:2833:17: error: 'SYS_DVBC_ANNEX_A' was not declared in this scope
| p[0].u.data = SYS_DVBC_ANNEX_A;
| ^~~~~~~~~~~~~~~~
| dvb/frontend.cpp: In member function 'std::__cxx11::string eDVBFrontend::getCapabilities()':
| dvb/frontend.cpp:2969:8: error: 'SYS_DVBC_ANNEX_A' was not declared in this scope
| case SYS_DVBC_ANNEX_A: ss << " DVBC_ANNEX_A"; break;
| ^~~~~~~~~~~~~~~~
| dvb/frontend.cpp:2970:8: error: 'SYS_DVBC_ANNEX_C' was not declared in this scope
| case SYS_DVBC_ANNEX_C: ss << " DVBC_ANNEX_C"; break;
| ^~~~~~~~~~~~~~~~
| dvb/frontend.cpp:2953:10: warning: enumeration value 'SYS_DVBC_ANNEX_AC' not handled in switch [-Wswitch]
| switch (it->first)
| ^
| dvb/frontend.cpp:2953:10: warning: enumeration value 'SYS_DMBTH' not handled in switch [-Wswitch]
| Makefile:2149: recipe for target 'dvb/dvb.o' failed
| make[4]: *** [dvb/dvb.o] Error 1
| make[4]: *** Waiting for unfinished jobs....
| Makefile:2149: recipe for target 'dvb/frontend.o' failed
| make[4]: *** [dvb/frontend.o] Error 1
| make[4]: Leaving directory '/home/storm/oe/build-enviroment/builds/openbh
 

storm_breaker

Member
Messages
10
Joined
Nov 11, 2017
Reaction score
1
Points
3
same error in branch v4.0. I think the problem is with a patch for the dvb , but im not sure which one exactly .
 

Ten Below

SuperTux
Staff member
Admin
Moderator
Messages
7,935
Joined
Sep 9, 2014
Reaction score
7,765
Points
628
same error in branch v4.0. I think the problem is with a patch for the dvb , but im not sure which one exactly .
I take back what i said about building on branch 4.1 as updated my environment earlier this evening & decided to have a bash myself & now have a shiny new image to play with :D. The build completed without any error so if you update your own now you should hopefully have better luck this time.

shot1.jpg
 

storm_breaker

Member
Messages
10
Joined
Nov 11, 2017
Reaction score
1
Points
3
Hi TenBelow.The images for Vu+ boxes came ok now .I try to make one image for dm8000 , where i get this error above . I used to make images before for dm8000 from source of openblackhole( 0.1 and 0.2) , but this time i cant manage .The issue is with the lib where there is need of some patching , but i still cant figure it out.I know that openbh is for VU+ boxes , but since that they are also under the oe alliance should be possible that i can create an image for dm8000 , specially that i have already did it long time ago and i still use it on my box.Im not so skilled with coding and i manage before , but this time , looks like more complicated , thats why i asked for help .On purpose i didnt say in the beginning that is for dm8000 , because i know already the answer that will be that openbh is not for dreambox .
There is a need of patch for dvb.cpp , frontend.cpp. eit.cpp to make it working .I manage to eliminate some of the errors , but still struggling with the dvb.cpp :( .If someone can help i will be very thankful .
Thanks
 
Top Bottom