Any step by step guides to build a version of Openvix?

[outrage_uk]

I have an old GigaBlue HD800 UE Plus which I would like to upgrade to Openvix 5.1, but obviously support for that model stopped at 4.1.

Are there any step by step guides to compile a build anywhere? :confused:

Thanks.

[twol]

There are really loads of stuff via google but try this for starters...
https://github.com/oe-alliance/build-enviroment
...just page down

[Huevos]

Have you got a fast machine running Ubuntu Linux that you can use to build the image?

[outrage_uk]

Yes latest Ubuntu

[twol]

I was having issues with Ubuntu 18.04 and haven‘t been back to see if they are resolved in the last few weeks.... you would be safer (and proven) to use 16.04 as the base until you are able to build on a regular basis (its a learning process!!)
.. if you need 18.04, its not difficult to have a dual boot 16.04/18.04 and the same /home

[birdman]

Currently if I try builds of Dev (the 4.1 branch) and the nextp3 branches then they each fail.

[twol]

I had an issue with the nextp3 branch but I think it was more an issue with the status of nextp3 at that time .... just haven‘t tried for the last 3 weeks on 18.04 mainly because I have other issues with 18.04 and I am dependent on the software package (unify) to maintain my wifi setup!

However everything runs well on 16.04.

[twol]

Currently if I try builds of Dev (the 4.1 branch) and the nextp3 branches then they each fail.
Nextp3 requires an E2 change that I have issued a pull for......

[Huevos]

Currently if I try builds of Dev (the 4.1 branch) and the nextp3 branches then they each fail.No idea why you are having trouble building 4.1.

[birdman]

No idea why you are having trouble building 4.1.This is a Dev build from scratch on an 18.04 system.

ERROR: gnu-config-native-20150728+gitAUTOINC+b576fa87c1-r0 do_unpack: Fetcher failure: Fetch command export DBUS_SESSION_BUS_ADDRESS="unix:path=/run/user/....
fatal: the '--set-upstream' option is no longer supported. Please use '--track' or '--set-upstream-to' instead.

ERROR: gnu-config-native-20150728+gitAUTOINC+b576fa87c1-r0 do_unpack: Function failed: base_do_unpack


The issue on nextp3 is with the .deps file for enigma2_python.Pcpp. There is no rule to create it and it isn't there when it needs to be.
I haven't looked at any detail beyond that, and can't remember what Ubuntu rev I was running when I last had a successful build.

[birdman]

This is a Dev build from scratch on an 18.04 system.
[CODE]ERROR: gnu-config-native-20150728+gitAUTOINC+b576fa87c1-r0 do_unpack: Fetcher failure: Fetch command export DBUS_SESSION_BUS_ADDRESS="unix:path=/run/user/....
fatal: the '--set-upstream' option is no longer supported. Please use '--track' or '--set-upstream-to' instead.

ERROR: gnu-config-native-20150728+gitAUTOINC+b576fa87c1-r0 do_unpack: Function failed: base_do_unpack[/CODEOddly a patch was supplied to fix this 10 months ago.
See
https://patchwork.openembedded.org/patch/145412/.
(although patch 145072, which the above is marked as superseding, has more info...even more odd is that 145072 corresponds to the current bitbake source patch).

EDIT: This patch is already applied in nextp3.
And if you fix this in Dev you run into another bug in bitbake/lib/bb/fetch2/clearcase.py:


File "/var/tmp/dev-build/oe-alliance/bitbake/lib/bb/fetch2/clearcase.py", line 72, in <module>
from distutils import spawn
ImportError: cannot import name 'spawn'
Makefile:886: recipe for target 'image' failed

The fix for that (in nextp3) is:


diff -u /var/tmp/dev-build/oe-alliance/bitbake/lib/bb/fetch2/clearcase.py .
--- /var/tmp/dev-build/oe-alliance/bitbake/lib/bb/fetch2/clearcase.py 2018-08-16 10:59:49.958087281 +0100
+++ ./clearcase.py 2018-06-05 11:38:17.622034161 +0100
@@ -69,7 +69,6 @@
from bb.fetch2 import FetchError
from bb.fetch2 import runfetchcmd
from bb.fetch2 import logger
-from distutils import spawn

class ClearCase(FetchMethod):
"""Class to fetch urls via 'clearcase'"""
@@ -107,7 +106,7 @@
else:
ud.module = ""

- ud.basecmd = d.getVar("FETCHCMD_ccrc") or spawn.find_executable("cleartool") or spawn.find_executable("rcleartool")
+ ud.basecmd = d.getVar("FETCHCMD_ccrc") or "/usr/bin/env cleartool || rcleartool"

if d.getVar("SRCREV") == "INVALID":
raise FetchError("Set a valid SRCREV for the clearcase fetcher in your recipe, e.g. SRCREV = \"/main/LATEST\" or any other label of your choice.")

And you also need to comment out the (unused) "from distutils import spawn" line in npm.py there too.

[birdman]

And after fixing bitbake to get a build to start you get:


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' failedwhile building automake-native.

Which looks like an issue with a Perl script in the build, which I thought had been fixed. Clearly not...

[birdman]

Which looks like an issue with a Perl script in the build, which I thought had been fixed. Clearly not...Not fixed (although looks like it might be in the automake used for nextp3, since I avoided it there).

It's this issue
https://gist.github.com/xywei/03b546054f0d2e2f76c5ac530c88268a (I thought it looked familiar).

of course, if you aren't running with a recent Perl, and aren't building from scratch then you may already have built automake and so not see this.

[twol]

Nextp3 runs clean in a new build - have done it many times (just not on 18.04) - there is an issue on subsequent builds with pam-smbpass (which I have reported) but you can work around.

[twol]

You also need the change in Dev that Huevos has now applied for automake (post #8)