Build my own Vix image

[twol]

Never had to do it, but basically when the build downloads a component there is a also a 2nd folder stored with the same component name plus .done - so delete the 2nd folder

[birdman]

Can I ask, if I get future errors, is it possible to just re-download a certain component? If so, would I just delete it from the sources folder and run make update again or would something else be needed?

It is if you set up the environment and run a suitable bitbake command.

I can post a script that lets you do this, if you're interested.

[lincsat]

It is if you set up the environment and run a suitable bitbake command.

I can post a script that lets you do this, if you're interested.

That would be useful - thanks

[birdman]

That would be useful - thanks

Here it is.

do-it.zip

It will require some editing, as it defines root to be where the build goes (so also hardwires a developer build, as that's the tree I copied this script from.).
It takes the machine architecture to work on from the MACHINE environment variable (I was being quick and lazy), so you could also hard-wire that if you're only ever going to work on one.

[Huevos]

There is no necessity to update Ubuntu for branch 4.4.

Ubuntu 16.04 works fine.

[ccs]

I installed ubuntu-16.04.1-desktop-i386 and used these commands in terminal:

#1 - Install packages on your buildserver
sudo apt-get install -y autoconf automake bison bzip2 curl cvs diffstat flex g++ gawk gcc gettext git-core gzip help2man ncurses-bin ncurses-dev libc6-dev libtool make texinfo patch perl pkg-config subversion tar texi2html wget zlib1g-dev chrpath libxml2-utils xsltproc libglib2.0-dev python-setuptools zip info coreutils diffstat chrpath libproc-processtable-perl libperl4-corelibs-perl sshpass default-jre default-jre-headless java-common libserf-dev qemu quilt libssl-dev

That list has a lot of differences to the one mentioned here...

Hate to point to another image! .. but have a look at the bottom half of this page
https://github.com/openatv/enigma2

In the git change from OpenATV to Openvix and away you go.

I've just had a play, and a number (loads) of packages on both lists must have failed for one reason or another. eg gcc-8

Sorry, I've not kept any logs, I was just testing Ubuntu on a usb stick, it worked fine, but somehow corrupted windows searching when I rebooted to windows 10.
I had copied one file from the windows filesystem to Ubuntu, surely if Ubuntu lets me do it there shouldn't be a problem?
I had to restore a backup image to get it working again.

[lincsat]

I'm still getting build errors and whatever I do, I can't get past an error building qemu-native, even the do-it doesn't compile it.

I've even got a new SSD and installed Ubuntu 20 from scratch and just added the 4.4 build environment. Tried release and developer images for the vuultimo4k and the zgemmah7, all fails at the same point. I did notice several warnings for unable to get checksum file, but that's usual. I'll have another go after the Weekend in case there is a down depositary. It's more likely just me doing something stupid though.

[Willo3092]

That list has a lot of differences to the one mentioned here...

That was the cause of my issues. I then updated to Ubuntu 18.04.4 LTS and followed the insructions here:

https://github.com/openatv/enigma2/b...e011/README.md

Then made sure I had gcc-8 by following the instructions here:

https://askubuntu.com/questions/1028...n-ubuntu-18-04

I've managed to build 5 OpenViX 5.4.000 release images now.

So to make a developer image is it just a matter of changing 'release' to 'developer' in the script?

MACHINE=zgemmah9combo DISTRO=openatv DISTRO_TYPE=release make image

... and what difference is there?

[birdman]

That was the cause of my issues. I then updated to Ubuntu 18.04.4 LTS...

Building on 20.04 LTS (which is 2-years newer....and has been out for a few months) also works fine.

[ccs]

Building on 20.04 LTS (which is 2-years newer....and has been out for a few months) also works fine.

That's what I was using, I'll try again when time/the weather permits.

[lincsat]

That's what I was using, I'll try again when time/the weather permits.

Yes, me too - even an openatv build is failing for me right now.

[ccs]

Yes, me too - even an openatv build is failing for me right now.

... but I fell flat on my face at the first hurdle.

[ccs]

... but I fell flat on my face at the first hurdle.

This is were I get to, running 20.04 from a usb stick, absolutely bog standard.

ubuntu@ubuntu:~$ sudo apt-get install -y autoconf automake bison bzip2 chrpath coreutils cpio curl cvs debianutils default-jre default-jre-headless diffstat flex g++ gawk gcc gcc-8 gettext git git-core gzip help2man info iputils-ping java-common libc6-dev libegl1-mesa libglib2.0-dev libncurses5-dev libperl4-corelibs-perl libproc-processtable-perl libsdl1.2-dev libserf-dev libtool libxml2-utils make ncurses-bin patch perl pkg-config psmisc python3 python3-git python3-jinja2 python3-pexpect python3-pip python-setuptools qemu quilt socat sshpass subversion tar texi2html texinfo unzip wget xsltproc xterm xz-utils zip zlib1g-dev
Reading package lists... Done
Building dependency tree       
Reading state information... Done
Note, selecting 'git' instead of 'git-core'
Package xterm is not available, but is referred to by another package.
This may mean that the package is missing, has been obsoleted, or
is only available from another source

Package quilt is not available, but is referred to by another package.
This may mean that the package is missing, has been obsoleted, or
is only available from another source

Package python3-pip is not available, but is referred to by another package.
This may mean that the package is missing, has been obsoleted, or
is only available from another source

Package subversion is not available, but is referred to by another package.
This may mean that the package is missing, has been obsoleted, or
is only available from another source

Package texinfo is not available, but is referred to by another package.
This may mean that the package is missing, has been obsoleted, or
is only available from another source
However the following packages replace it:
  install-info info

Package qemu is not available, but is referred to by another package.
This may mean that the package is missing, has been obsoleted, or
is only available from another source

E: Unable to locate package chrpath
E: Unable to locate package cvs
E: Unable to locate package gcc-8
E: Unable to locate package help2man
E: Unable to locate package libegl1-mesa
E: Unable to locate package libproc-processtable-perl
E: Unable to locate package libsdl1.2-dev
E: Couldn't find any package by glob 'libsdl1.2-dev'
E: Couldn't find any package by regex 'libsdl1.2-dev'
E: Unable to locate package libserf-dev
E: Unable to locate package python3-git
E: Package 'python3-pip' has no installation candidate
E: Unable to locate package python-setuptools
E: Package 'qemu' has no installation candidate
E: Package 'quilt' has no installation candidate
E: Unable to locate package sshpass
E: Package 'subversion' has no installation candidate
E: Unable to locate package texi2html
E: Package 'texinfo' has no installation candidate
E: Package 'xterm' has no installation candidate
ubuntu@ubuntu:~$

Even had to post on here using Firefox/Ubuntu because I couldn't save the text anywhere.

[lincsat]

Looks like it can't install the required packages due to them being in use in the portable system. If you have a spare HDD or SSD, try installing on that. I've managed to get all the pre-requisites done, except for the

Use update-alternatives for having gcc redirected automatically to gcc-8

as It appears to be already set. I've also completed the step detailed in here -

https://github.com/openatv/enigma2/issues/1780

The builds (openvix and openatv, ZGemma H7 and Vu+ Ultimo4k) start but always bug out with errors, even after several re-runs, so I'm guessing a depository is offline and I'll try again after the weekend

[ccs]

Yes - the stick is mounted read-only, the internal hd is mounted as /media/ubuntu/....... and will be why I can save files in the home directory, but not on the stick.

I'd have thought that the error messages (or lack of) would have indicated that the filesystem was read-only??