AB-Com PULSe 4K SE. Crazy offer only £129! FREE UK DELIVERY!
Superb quality and spec AB-Com PULSe 4K SE. Crazy offer! Only £129! FREE UK DELIVERY! 4K UHD, Enigma 2, Multiboot 4 images & more!...
AB-Com PULSe 4k Rev II Twin tuner only £179! FREE UK DELIVERY!
Superb quality and spec AB-Com PULSe 4K Rev II Twin Satellite tuner only £179! FREE UK DELIVERY! 4K UHD, Enigma 2, SATA HDD facility, Multiboot 4 images & more!...

Build my own Vix image

Getting a new error today whilst compiling the rtl8852cu part due to an argument list being too long. Attached is the compile log (hope it's the right log).

Not sweating it right now in case it gets corrected in the next few days.
 

Attachments

lincsat said:
Getting a new error today whilst compiling the rtl8852cu part due to an argument list being too long. Attached is the compile log (hope it's the right log).

Not sweating it right now in case it gets corrected in the next few days.
Click to expand...
A workaround would be to run the build from a place with a shorter pathname, since that is copied multiple times into each command line.

Bind-mount the build-environment somewhere (I put mine under /var/tmp/dev-build). Although the pathname change may (will?) mean you need to redo everything from scratch.
 
birdman said:
A workaround would be to run the build from a place with a shorter pathname, since that is copied multiple times into each command line.

Bind-mount the build-environment somewhere (I put mine under /var/tmp/dev-build). Although the pathname change may (will?) mean you need to redo everything from scratch.
Click to expand...

Not familiar with that, so would I create the mount like this
Code: 
mount --bind /media/lincsat/imagebuilder/openvixbuilder/build-enviroment /var/tmp/dev-build

Then
Code: 
cd /var/tmp/dev-build

and run all the commands including make update and make image from there
 
lincsat said:
Not familiar with that, so would I create the mount like this
Code: 
mount --bind /media/lincsat/imagebuilder/openvixbuilder/build-enviroment /var/tmp/dev-build

Then
Code: 
cd /var/tmp/dev-build

and run all the commands including make update and make image from there
Click to expand...
Yes. (Or you can use mount -o bind ....they seem to be the same).
 
lincsat said:
The svn.streamboard.tv site has been offline for a few days causing builds to fail at the initial stage. Is there an easy way to disable the streamboard/oscam check temporally until the site is back online, maybe with a recipes-local file?
Click to expand...

It's down again.

The five *.bbappend files discussed here a couple of pages back still seem to work, at least to allow building, but I haven't tested the resulting oscams it builds.
 
BrianG61UK said:
It's down again.

The five *.bbappend files discussed here a couple of pages back still seem to work, at least to allow building, but I haven't tested the resulting oscams it builds.
Click to expand...

I've just built a 6.5.3.003 Dev image for a Zgemma H9SE without needing the files, so I guess streamboard is back online.
 
The oscam bitbake files have changed to use Hains repository. Those append files are not required and may actually cause an issue now.
 
I'm trying to get back into building but have fallen at the first hurdle.
I've created a new build environment but may not have used the latest instructions.

Code: 
willo@beelink:/media/willo/USB-SSD/build-enviroment$ make update
Updating Git repositories...
Already up-to-date.
Synchronising submodule url for 'bitbake'
Synchronising submodule url for 'meta-clang'
Synchronising submodule url for 'meta-oe-alliance'
Synchronising submodule url for 'meta-openembedded'
Synchronising submodule url for 'meta-python2'
Synchronising submodule url for 'meta-qt5.15'
Synchronising submodule url for 'openembedded-core'
Synchronising submodule url for 'meta-oe/recipes-oe-alliance/enigma2-plugins/e2openplugins'
The oe-alliance is now up-to-date.
willo@beelink:/media/willo/USB-SSD/build-enviroment$ MACHINE=hd61 DISTRO=openvix DISTRO_TYPE=release make image
check internet connection: Online      
NOTE: Your conf/bblayers.conf has been automatically updated.
NOTE: Your conf/bblayers.conf has been automatically updated.
NOTE: Your conf/bblayers.conf has been automatically updated.
ERROR:  OE-core's config sanity checker detected a potential misconfiguration.
    Either fix the cause of this error or at your own risk disable the checker (see sanity.conf).
    Following is the list of potential problems / advisories:

    Error, the PACKAGE_ARCHS variable contains duplicates. The following archs are listed more than once: hd61

Summary: There was 1 ERROR message, returning a non-zero exit code.
make: *** [Makefile:1031: image] Error 1
 
Can anyone confirm if these build instructions are still current please?

Code: 
###########################################################################################################################################

1 - Install packages on your buildserver

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-12 gcc-multilib g++-multilib 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 zstd fakeroot lz4 liblz4-tool

###########################################################################################################################################

2 - Set python3 as preferred provider for python

sudo update-alternatives --install /usr/bin/python python /usr/bin/python2 1
sudo update-alternatives --install /usr/bin/python python /usr/bin/python3 2
sudo update-alternatives --config python
select python3

###########################################################################################################################################

3 - Set your shell to /bin/bash

sudo dpkg-reconfigure dash

When asked: Install dash as /bin/sh?
select "NO"

###########################################################################################################################################

4 - modify max_user_watches

echo fs.inotify.max_user_watches=524288 | sudo tee -a /etc/sysctl.conf

sudo sysctl -n -w fs.inotify.max_user_watches=524288

###########################################################################################################################################

5 - Clone oe-alliance git

git clone https://github.com/oe-alliance/build-enviroment.git -b 5.4

then change directory to build-enviroment

###########################################################################################################################################

6 - Update build-enviroment

make update

###########################################################################################################################################

7 - Initialise the first machine so site.conf gets created

MACHINE=hd61 DISTRO=openvix DISTRO_TYPE=release make init

###########################################################################################################################################

8 - Update site.conf

- BB_NUMBER_THREADS, PARALLEL_MAKE set to number of threads supported by the CPU
- add/modify DL_DIR = " location for build sources " to point to a location where you can save derived build sources,
this will reduce build time in fetching these sources again.

###########################################################################################################################################

9 - Building image with feeds

MACHINE=hd61 DISTRO=openvix DISTRO_TYPE=release make image

or

MACHINE=hd61 DISTRO=openvix DISTRO_TYPE=developer make image


###########################################################################################################################################

10 - Building an image without feeds (Build time 1-2h)

MACHINE=hd61 DISTRO=openvix DISTRO_TYPE=release make enigma2-image

or

MACHINE=hd61 DISTRO=openvix DISTRO_TYPE=developer make enigma2-image

###########################################################################################################################################

11 - Building feeds only

MACHINE=hd61 DISTRO=openvix DISTRO_TYPE=release make feeds

or

MACHINE=hd61 DISTRO=openvix DISTRO_TYPE=developer make feeds
###########################################################################################################################################
 
Willo3092 said:
Can anyone confirm if these build instructions are still current please?

Code: 
###########################################################################################################################################

1 - Install packages on your buildserver

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-12 gcc-multilib g++-multilib 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 zstd fakeroot lz4 liblz4-tool

###########################################################################################################################################

2 - Set python3 as preferred provider for python

sudo update-alternatives --install /usr/bin/python python /usr/bin/python2 1
sudo update-alternatives --install /usr/bin/python python /usr/bin/python3 2
sudo update-alternatives --config python
select python3

###########################################################################################################################################

3 - Set your shell to /bin/bash

sudo dpkg-reconfigure dash

When asked: Install dash as /bin/sh?
select "NO"

###########################################################################################################################################

4 - modify max_user_watches

echo fs.inotify.max_user_watches=524288 | sudo tee -a /etc/sysctl.conf

sudo sysctl -n -w fs.inotify.max_user_watches=524288

###########################################################################################################################################

5 - Clone oe-alliance git

git clone https://github.com/oe-alliance/build-enviroment.git -b 5.4

then change directory to build-enviroment

###########################################################################################################################################

6 - Update build-enviroment

make update

###########################################################################################################################################

7 - Initialise the first machine so site.conf gets created

MACHINE=hd61 DISTRO=openvix DISTRO_TYPE=release make init

###########################################################################################################################################

8 - Update site.conf

- BB_NUMBER_THREADS, PARALLEL_MAKE set to number of threads supported by the CPU
- add/modify DL_DIR = " location for build sources " to point to a location where you can save derived build sources,
this will reduce build time in fetching these sources again.

###########################################################################################################################################

9 - Building image with feeds

MACHINE=hd61 DISTRO=openvix DISTRO_TYPE=release make image

or

MACHINE=hd61 DISTRO=openvix DISTRO_TYPE=developer make image


###########################################################################################################################################

10 - Building an image without feeds (Build time 1-2h)

MACHINE=hd61 DISTRO=openvix DISTRO_TYPE=release make enigma2-image

or

MACHINE=hd61 DISTRO=openvix DISTRO_TYPE=developer make enigma2-image

###########################################################################################################################################

11 - Building feeds only

MACHINE=hd61 DISTRO=openvix DISTRO_TYPE=release make feeds

or

MACHINE=hd61 DISTRO=openvix DISTRO_TYPE=developer make feeds
###########################################################################################################################################
Click to expand...

looks fine except it probably should be python3-setuptools not just python-setuptools and you probably only have python 3 installed if on current Ubuntu

Just built HD61 on OE-A 5.4 no issues
 
Last edited:
I've updated to python3-setuptools but still the same problem.

I tried building for the vuono4kse and that seems to be working. Must be a problem relating to hd61?
 
Willo3092 said:
3 - Set your shell to /bin/bash

sudo dpkg-reconfigure dash
Click to expand...
That has not been an option on Ubuntu since 23.04 (or 23.10?).
You'd have to do it by hand.

Although the correct solution is to get people to write scripts correctly, since if a script need bash it should say so, not say sh and expect the user to reconfigure their entire system.

The main culprit here is actually the OE Makefile!!
(Although there are also some in post-/pre-install scripts which use bash syntax and don't specify ANY interpreter - awful coding).
 
Willo3092 said:
I thought I had done by setting up a new build-environment.
I'm using the same site.conf and sources though.
Click to expand...

I've been chatting to twol over PM trying to get a working openvix build for a very old receiver I would like to use in "client mode". Decided to try to build my own image for it and started from scratch following the instructions on the OpenVIX github. I spun up a fresh vm but installed ubuntu 22.04.4 rather than the current version. It appears to be building ok (still running, about 80% through). Just wondering whether it would have been more prudent to use the most recent ubuntu server?
 
Morini said:
Just wondering whether it would have been more prudent to use the most recent ubuntu server?
Click to expand...
Shouldn't matter.
It just uses the base system to build what it needs to build the real Vix distro.
And, IIRC, the "standard" builds are still done on 22.04 anyway.
 
1) Stick to LTS versions (that means 24.04 or 22.04).

2) 24.04 only came out a couple of weeks ago, what's the rush?

3) 22.04 is fine for building branch 5.4.
 
Willo3092 said:
I thought I had done by setting up a new build-environment.
I'm using the same site.conf and sources though.
Click to expand...

Check that your site.conf puts the sources in a different directory to previous versions and not reusing the previous sources
 
lincsat said:
Check that your site.conf puts the sources in a different directory to previous versions and not reusing the previous sources
Click to expand...

I did manage to build a SF4008 release image earlier but the feeds were incomplete for some reason.

I've started from scratch altogether, with a new build environment and sources.
I'm building on a 16gb mini-pc though so will probably take ages.
 
You must log in or register to reply here.

Similar threads

S
[ViX_Misc] Will my change to NFS survive an upgrade?
Replies
10
Views
348
birdman
birdman
G
[GiGaBlue UHD UE 4K] Load ViX image to a particular multiboot slot?
Replies
18
Views
823
Huevos
Huevos
R
[DM920] DM920 in a loop of restarts after uploading my own setting.
Replies
18
Views
3K
DimitarCC
DimitarCC
T
[H9.2S] Add USB DVB-T2 tuner stick
Replies
17
Views
1K
paddycans
paddycans
S
VU+ SOLO
Replies
2
Views
621
SteveyC
S

OpenViX Feeds Status

Back
Top