Build my own Vix image

**twol** · 03-08-20, 15:08

https://github.com/oe-alliance/oe-al...nigma2-plugins —- remove the .bb
https://github.com/oe-alliance/oe-al...iance-feeds.bb - remove the dependency

You might find the build blows out because of some other dependency - just remove it.

Although this is a bit like a permanent self destruct - something is wrong with your build environment

**ccs** · 03-08-20, 15:25

Originally Posted by twol

https://github.com/oe-alliance/oe-al...nigma2-plugins —- remove the .bb
https://github.com/oe-alliance/oe-al...iance-feeds.bb - remove the dependency

You might find the build blows out because of some other dependency - just remove it.

Although this is a bit like a permanent self destruct - something is wrong with your build environment

Sorry, no idea what you're suggesting here. Are you saying I should edit the relevant source files, I've so far found it impossible to find such files in the build setup I'm running.

All I'm doing is following the basic steps highlighted in this thread, I'm getting errors which are already known about, and now a syntax error in the source of a plugin.

I haven't the slightest idea why my build environment could now be wrong.

**Huevos** · 03-08-20, 16:04

Originally Posted by BrianTheTechHead

Me too.
Using build-enviroment 4.4 on Debian 10.4 in a VirtualBox VM with 4GB RAM and an 80GB virtual hard drive.

Haven't worked out what one can do about the the lack of feeds for 5.4.
But it loaded everything somehow, except for the picons.

You need a webserver running on your build server.

So let's say the root folder of the webserver is /var/www ...

Create a folder for feeds... /var/www/feeds

In site.conf add the domain name of your feeds (and your enigma repo if you want). e.g...

Code:

SCONF_VERSION = "1"
BB_NUMBER_THREADS = "32"
PARALLEL_MAKE = "-j 16"
BUILD_OPTIMIZATION = "-O2 -pipe"
DL_DIR = "/home/openvix/sources"
INHERIT += "rm_work"
ENIGMA2_URI = "git://github.com/yourRepo/enigma2.git;protocol=git;branch=Dev"
DISTRO_FEED_URI = "http://your.feeds.domain/feeds/${DISTRO_NAME}/${DISTRO_TYPE}/${DISTRO_VERSION}/${MACHINE}"

Note: in the above file my sources folder is not in the build folder. So if I trash a build I retain all the sources files for other build envs.

Now build your image.

Once you image is built, symlink the webserver to the IPK folder. e.g...

Code:

mkdir -p /var/www/feeds/openvix/developer/5.4/h7
ln -s /home/openvix/5.4/builds/openvix/developer/h7/tmp/deploy/ipk/* /var/www/feeds/openvix/experimental/5.4/h7

**twol** · 03-08-20, 16:27

Originally Posted by ccs

Sorry, no idea what you're suggesting here. Are you saying I should edit the relevant source files, I've so far found it impossible to find such files in the build setup I'm running.

All I'm doing is following the basic steps highlighted in this thread, I'm getting errors which are already known about, and now a syntax error in the source of a plugin.

I haven't the slightest idea why my build environment could now be wrong.

of course edit your local files - you should have a meta-oe directory and inside that a recipes-oe-alliance directory - inside that you have the files I was highlighting

**ccs** · 03-08-20, 17:10

Originally Posted by twol

of course edit your local files - you should have a meta-oe directory and inside that a recipes-oe-alliance directory - inside that you have the files I was highlighting

Eventually found the .bb files but the build got worse, so starting again from scratch.

Found the files around about here....

Code:

 /home/openvixbuilder/openvix/build-enviroment/meta-oe-alliance/meta-oe/recipes-oe-alliance/enigma2-plugins

I couldn't find the .py files, any clues much appreciated.

**birdman** · 03-08-20, 18:17

Originally Posted by ccs

Not my day today, yahoo!!

That error message is what you'd get when running a python2 script (all of the xml2po.py ones are) with python3.

**Valiant** · 04-08-20, 10:14

Been a while since I built 5.3 for my miraclebox after vix support was dropped , so tried to build again and encountered an error straight away, miraclebox is not supported by the build process.

My environment is ok, I built vuuno4k and osmini images without error over the weekend after updating ubuntu.

If there is no way to build a later stable version for the miraclebox then I will leave it on 5.3.001 or 4 , I just thought there might be a local parameter or list I could change to allow the build to progress.

**twol** · 04-08-20, 11:04

Originally Posted by Valiant

Been a while since I built 5.3 for my miraclebox after vix support was dropped , so tried to build again and encountered an error straight away, miraclebox is not supported by the build process.

My environment is ok, I built vuuno4k and osmini images without error over the weekend after updating ubuntu.

If there is no way to build a later stable version for the miraclebox then I will leave it on 5.3.001 or 4 , I just thought there might be a local parameter or list I could change to allow the build to progress.

Its still in the makefile mbtwinplus, so no reason that it will not build - whether it will have enough to run the image is another story.

**ccs** · 04-08-20, 12:36

Originally Posted by birdman

That error message is what you'd get when running a python2 script (all of the xml2po.py ones are) with python3.

Thanks, as always, that sorted it when I opted for python2. I was expecting python3 to be used now, is that not the case?

Can't get passed this (repeated, always the same) checksum error....

Code:

File: '/home/openvixbuilder/openvix/build-enviroment/sources/ntp-4.2.8p13.tar.gz' has md5 checksum 19bb20214e0a88629e17a5b6c605d45d when ea040ab9b4ca656b5229b89d6b822f13 was expected
File: '/home/openvixbuilder/openvix/build-enviroment/sources/ntp-4.2.8p13.tar.gz' has sha256 checksum 53a4b4b6569e8ef8b0aa6b7adbf736563467dba67aa77c6f4a37b7387b01508f when 288772cecfcd9a53694ffab108d1825a31ba77f3a8466b0401baeca3bc232a38 was expected

It suggests changing the checksums, maybe it's not advisable, but where do I find the relevant file? I've spent ages trying to find it, but failed miserably.

Code:

If this change is expected (e.g. you have upgraded to a new version without updating the checksums) then you can use these lines within the recipe:
SRC_URI[md5sum] = "19bb20214e0a88629e17a5b6c605d45d"
SRC_URI[sha256sum] = "53a4b4b6569e8ef8b0aa6b7adbf736563467dba67aa77c6f4a37b7387b01508f"
Otherwise you should retry the download and/or check with upstream to determine if the file has become corrupted or otherwise unexpectedly modified.

**Valiant** · 04-08-20, 13:09

Thanks twol, ill have another go and post the error that I get.

**ccs** · 04-08-20, 13:14

Post #204.... md5 checksum confirmed as ok - 19bb20214e0a88629e17a5b6c605d45d after downloading the file onto a windows laptop.

**ccs** · 04-08-20, 14:23

For reference, the file is

Code:

http://www.eecis.udel.edu/~ntp/ntp_spool/ntp4/ntp-4.2/ntp-4.2.8p13.tar.gz

**lincsat** · 04-08-20, 14:42

How would I get the build to use my own passwd file so I don't have to manually set if a settings restore fails?

**twol** · 04-08-20, 15:28

Originally Posted by ccs

Thanks, as always, that sorted it when I opted for python2. I was expecting python3 to be used now, is that not the case?

Can't get passed this (repeated, always the same) checksum error....

Code:

File: '/home/openvixbuilder/openvix/build-enviroment/sources/ntp-4.2.8p13.tar.gz' has md5 checksum 19bb20214e0a88629e17a5b6c605d45d when ea040ab9b4ca656b5229b89d6b822f13 was expected
File: '/home/openvixbuilder/openvix/build-enviroment/sources/ntp-4.2.8p13.tar.gz' has sha256 checksum 53a4b4b6569e8ef8b0aa6b7adbf736563467dba67aa77c6f4a37b7387b01508f when 288772cecfcd9a53694ffab108d1825a31ba77f3a8466b0401baeca3bc232a38 was expected

It suggests changing the checksums, maybe it's not advisable, but where do I find the relevant file? I've spent ages trying to find it, but failed miserably.

Code:

If this change is expected (e.g. you have upgraded to a new version without updating the checksums) then you can use these lines within the recipe:
SRC_URI[md5sum] = "19bb20214e0a88629e17a5b6c605d45d"
SRC_URI[sha256sum] = "53a4b4b6569e8ef8b0aa6b7adbf736563467dba67aa77c6f4a37b7387b01508f"
Otherwise you should retry the download and/or check with upstream to determine if the file has become corrupted or otherwise unexpectedly modified.

If you look in the build log file you will see at what stage it failed and be able to find the .bb where you need to update the checksums

**ccs** · 04-08-20, 16:14

Originally Posted by twol

If you look in the build log file you will see at what stage it failed and be able to find the .bb where you need to update the checksums

If ~/openvix/build-enviroment/builds/openvix/dev/et10000/tmp/log/cooker/et10000/ is were the logs are stored, then I've found the relevant .bb file, with the wrong? checksum.

/home/openvixbuilder/openvix/build-enviroment/meta-openembedded/meta-networking/recipes-support/ntp/ntp_4.2.8p13.bb

Took a bit of finding is an understatement.

Why am I the only one seeing this checksum error? Am I picking up the wrong version of ntp?

I'll start again tomorrow when 5.4.000 is released, and dev/master are in sync. I started the build yesterday when 5.4 was just being finalised.

Thread: Build my own Vix image

Thread Tools

Display

The Following 2 Users Say Thank You to Huevos For This Useful Post:

The Following 2 Users Say Thank You to twol For This Useful Post:

The Following User Says Thank You to birdman For This Useful Post:

The Following User Says Thank You to twol For This Useful Post:

Posting Permissions

Options

About

Site Links

Social Media