Build my own Vix image

[twol]

I can confirm that applying the change here https://github.com/openembedded/openembedded-core/commit/16f2684ebeffa72b5d90525cf9102751b68c298e from Birdmans post #988 plus unzipping Birdman's zip from #968 into meta-local/recipes-local fixes the build.
The 1st change is a simple edit of openembedded-core/meta/classes-global/base-bbclass so will try to add this to the README for local builders.

 

[Willo3092]

I can confirm that applying the change here https://github.com/openembedded/openembedded-core/commit/16f2684ebeffa72b5d90525cf9102751b68c298e from Birdmans post #988 plus unzipping Birdman's zip from #968 into meta-local/recipes-local fixes the build.
The 1st change is a simple edit of openembedded-core/meta/classes-global/base-bbclass so will try to add this to the README for local builders.

It works now! Thanks to all involved in sorting it out

 

[h58]

I created a new build-enviroment OEA-6.9 AX 4K HD51 on LinuxMint22.2 (Ubuntu) with no Errors

Thanks for the great buildsystem.

 

[h58]

Today i would build an image, but there is a error...

 

[lincsat]

I got a build error yesterday, looks like it's the same enigme2 component. I'm running it again today to see if was just a glitch before reporting it

ERROR: oe_runmake failed
WARNING: /media/vix/oe60/build-enviroment/builds/openvix/Developer/gb7252/tmp/work/gbquad4kpro-oe-linux-gnueabi/enigma2/6.9+git/temp/run.do_compile.3439887:195 exit 1 from 'exit 1'
WARNING: Backtrace (BB generated script):
    #1: bbfatal_log, /media/vix/oe60/build-enviroment/builds/openvix/Developer/gb7252/tmp/work/gbquad4kpro-oe-linux-gnueabi/enigma2/6.9+git/temp/run.do_compile.3439887, line 195
    #2: die, /media/vix/oe60/build-enviroment/builds/openvix/Developer/gb7252/tmp/work/gbquad4kpro-oe-linux-gnueabi/enigma2/6.9+git/temp/run.do_compile.3439887, line 179
    #3: oe_runmake, /media/vix/oe60/build-enviroment/builds/openvix/Developer/gb7252/tmp/work/gbquad4kpro-oe-linux-gnueabi/enigma2/6.9+git/temp/run.do_compile.3439887, line 174
    #4: autotools_do_compile, /media/vix/oe60/build-enviroment/builds/openvix/Developer/gb7252/tmp/work/gbquad4kpro-oe-linux-gnueabi/enigma2/6.9+git/temp/run.do_compile.3439887, line 161
    #5: do_compile, /media/vix/oe60/build-enviroment/builds/openvix/Developer/gb7252/tmp/work/gbquad4kpro-oe-linux-gnueabi/enigma2/6.9+git/temp/run.do_compile.3439887, line 156
    #6: main, /media/vix/oe60/build-enviroment/builds/openvix/Developer/gb7252/tmp/work/gbquad4kpro-oe-linux-gnueabi/enigma2/6.9+git/temp/run.do_compile.3439887, line 208

 

[twol]

I got a build error yesterday, looks like it's the same enigme2 component. I'm running it again today to see if was just a glitch before reporting it

ERROR: oe_runmake failed
WARNING: /media/vix/oe60/build-enviroment/builds/openvix/Developer/gb7252/tmp/work/gbquad4kpro-oe-linux-gnueabi/enigma2/6.9+git/temp/run.do_compile.3439887:195 exit 1 from 'exit 1'
WARNING: Backtrace (BB generated script):
    #1: bbfatal_log, /media/vix/oe60/build-enviroment/builds/openvix/Developer/gb7252/tmp/work/gbquad4kpro-oe-linux-gnueabi/enigma2/6.9+git/temp/run.do_compile.3439887, line 195
    #2: die, /media/vix/oe60/build-enviroment/builds/openvix/Developer/gb7252/tmp/work/gbquad4kpro-oe-linux-gnueabi/enigma2/6.9+git/temp/run.do_compile.3439887, line 179
    #3: oe_runmake, /media/vix/oe60/build-enviroment/builds/openvix/Developer/gb7252/tmp/work/gbquad4kpro-oe-linux-gnueabi/enigma2/6.9+git/temp/run.do_compile.3439887, line 174
    #4: autotools_do_compile, /media/vix/oe60/build-enviroment/builds/openvix/Developer/gb7252/tmp/work/gbquad4kpro-oe-linux-gnueabi/enigma2/6.9+git/temp/run.do_compile.3439887, line 161
    #5: do_compile, /media/vix/oe60/build-enviroment/builds/openvix/Developer/gb7252/tmp/work/gbquad4kpro-oe-linux-gnueabi/enigma2/6.9+git/temp/run.do_compile.3439887, line 156
    #6: main, /media/vix/oe60/build-enviroment/builds/openvix/Developer/gb7252/tmp/work/gbquad4kpro-oe-linux-gnueabi/enigma2/6.9+git/temp/run.do_compile.3439887, line 208

Built yesterday and this afternoon - no errors on gigablue

 

[lincsat]

Mine has just finished building, Gigablue gbquad4KPro, it completed but took quite a while. Looks like it was a glitch yesterday which is why I wait before reporting

 

[el bandido]

These build errors look to be the exact same as to what twol has already fixed, but the fix or repair does not exist in enigma2 Release yet.

When the image stops or crashes it lists the directory for the crash log. Posting screenshots or snippets provides at most clues, but the log will usually show what really happened. It is easy to get confused when hunting the exact log because other logs may exist in the same location and look almost identical. Here is an example:
log: /home/pli/builds/OE-6.0-1/build-enviroment/builds/openvix/release/tmp/work/osmini4k-oe-linux-gnueabi/enigma2/6.9+git/temp/log.do_compile.850479

You can take a log file of a crash and feed it into ChatGPT. Drag the logfile into the window of ChatGPT, or copy and paste the whole log. Then type something like: "Carefully analyze log and write a complete report in .md format." Wait a bit and you will get an explanation. In 2025, this did not work too well using ChatGPT. In the eight month of 2026, I get a full report along with an explanation that points to edits in 2022...

 

[h58]

i use chatgpt, he tells the same ...

my python 3.14 is different...
- **Recipe:** `enigma2`
- **Version:** `6.9+git`
- **Target:** `ax51-oe-linux-gnueabi`
- **CPU/toolchain target:** ARM, Cortex-A15, hard-float
(`arm-oe-linux-gnueabi-g++`)
- **C++ standard:** GNU C++20
- **Python headers used by the build:** **Python 3.14**
- **Build command:** `make -j 8`
- **Primary failing source:** `python/enigma_python.cpp`
- **Primary failing source line:** `4785`
- **Primary error:** `PyInt_FromLong` is not declared
- **Compiler suggestion:** `PyLong_FromLong`
- **Final BitBake result:** `ERROR: oe_runmake failed`
- **Final exit status:** `1`

A conditional compatibility definition can sometimes bridge old code to
Python 3, for example conceptually:

``` cpp
#ifndef PyInt_FromLong
#define PyInt_FromLong PyLong_FromLong
#endif
```

Ich werde in Python nicht rumdoktern.

Seltsamerweise lassen sich alle anderen gängigen Enigma2 Images für ax51 (hd51) bis zu Ende bauen:
MACHINE=ax51 DISTRO=openatv DISTRO_TYPE=release make enigma2-image
MACHINE=ax51 DISTRO=openbh DISTRO_TYPE=release make enigma2-image
MACHINE=ax51 DISTRO=openhdf DISTRO_TYPE=release make enigma2-image
MACHINE=ax51 DISTRO=openspa DISTRO_TYPE=release make enigma2-image

Am 11.07.2026 ließ sich Openvix Image noch bauen mit:
MACHINE=ax51 DISTRO=openvix DISTRO_TYPE=release make enigma2-image