Build my own Vix image

[ccs]

.... I just went back to 18.04 which defaults to python2.

If you want to stay on 20.04, have a look here ....

https://linuxhint.com/update_alternatives_ubuntu/

[bbbuk]

I'm going to try sticking with 20.04 and use update alternatives as it's mentioned in openatv readme for 6.5 but have selected Python 2 instead of 3 as the manual default.

Just re-running build again and will let you know outcome.

[birdman]

.... I just went back to 18.04 which defaults to python2.

If you want to stay on 20.04, have a look here ....

https://linuxhint.com/update_alternatives_ubuntu/

Or, indeed, here:
https://www.world-of-satellite.com/s...l=1#post498864

[ccs]

Or, indeed, here:
https://www.world-of-satellite.com/s...l=1#post498864

..... private link, unfortunately.

[bbbuk]

Builds fine on 18.04

But think this was user error on my behalf more than version of ubuntu I was building on because I noticed the site.conf that I would paste (from a previous back-up) before freshly building had "-native" under BUILD_OPTIMIZATION but when I checked against one it freshly generated itself never had "-native"

[twol]

I use 18.04 for all OE-A 4.4 builds and in general it has always been painless and therefore I think its the easiest & safest base to use. Running nextp3 builds (the next OE-A branch) I use 20.04 and have been building both python 2 &3 images for some time without any build issues - although I use different build environments for python 2 & 3 to handle their different requirements in the final image creation..

[birdman]

..... private link, unfortunately.

Sorry about that. What it said was this (about a build I did on Kubuntu 20.04)

What issue was that?

I've just built the OE4.4-based 5.4.xxx for an mbtwin from scratch and apart from a qemu issue (which was nothing to do with gcc, and I now have a simple patch to fix) it completed OK.

(The qemu issue is now fixed).

[bbbuk]

@Birdman, so I should be okay to build using Unbuntu 20.04 without incident especially now that I believe I found issue I had previously due to building with "-native" ?

[birdman]

@Birdman, so I should be okay to build using Unbuntu 20.04 without incident [...]

I would expect that to be the case.

[...]especially now that I believe I found issue I had previously due to building with "-native" ?

Build what with "-native"?
There used to be a -march=native option in the Makefile (which was a pain for me, as I have my set-up on a USB disk and might build it on any of a variety of systems, for whom "native" is not the same) and hence I managed to get a command-line option to set this "usefully" (for me).
But that (-march=native) was removed from the OE 4.4 build, as it caused problems elsewhere.
However, since it was removed I don't see how you can be using it - perhaps you mean something else?

[bbbuk]

... But that (-march=native) was removed from the OE 4.4 build, as it caused problems elsewhere. However, since it was removed I don't see how you can be using it - perhaps you mean something else?

I kept using a back-up copy I made of it which could well have been from OE 4.3 days

[Willo3092]

I've installed Ubuntu 18.04 on a different PC and getting the following error:

ERROR: Task (/home/willo/openvix/build-enviroment/meta-oe-alliance/meta-oe/recipes-distros/openvix/softcams/openvix-softcams-oscam-pcscd-latest-mipsel.bb:do_compile) failed with exit code '1'
NOTE: Tasks Summary: Attempted 5236 tasks of which 2905 didn't need to be rerun and 1 failed.

Summary: 1 task failed:
/home/willo/openvix/build-enviroment/meta-oe-alliance/meta-oe/recipes-distros/openvix/softcams/openvix-softcams-oscam-pcscd-latest-mipsel.bb:do_compile
Summary: There were 53 WARNING messages shown.
Summary: There was 1 ERROR message shown, returning a non-zero exit code.
Makefile:998: recipe for target 'image' failed
make: *** [image] Error 1


I'm sure I've had something like this before but can't for the life of me remember what the fix was.

I have still got my original pc which does build successfully if it's possible to copy files from that?

log.do_compile.zip

[ccs]

.... quick search

https://www.world-of-satellite.com/s...l=1#post484869

[birdman]

I'm sure I've had something like this before but can't for the life of me remember what the fix was.

The actual error (twice) is:

 fatal error: webif/pages.h: No such file or directory 

    6 | #include "webif/pages.h" 
      |          ^~~~~~~~~~~~~~~

That's actually supposed to be built as part of the build (it's what pages_gen.c is supposed to do).
Odd....

[birdman]

FWIW I've just done an update for my et8000 build, which did a fetch and compile of the svn11677 version of openvix-softcams-oscam-pcscd-latest-mipsel and it compiled OK.
And that is on Kubuntu 20.10.

EDIT: Although Vix as a whole won't build on Kubuntu 20.10 as some code in openembedded-core can't handle gcc versions of 10+ (they start with 2 digits, not one). So I'll have to work out a PR for that. (Fix added and tested, and with it in the build completes).
Won't affect 20.04, though.

[birdman]

Although Vix as a whole won't build on Kubuntu 20.10 as some code in openembedded-core can't handle gcc versions of 10+ (they start with 2 digits, not one). So I'll have to work out a PR for that.

The fix actually went into openembedded-core in March this year.
When will it end up in Vix?