Build my own Vix image

[lincsat]

I'm just using the standard build, not tried adding or removing anything yet.

I'm still a novice when it comes to compiling, I assume with your homebuild, you can specify which components to compile and add

 

[abu baniaz]

Homebuild is just name of image. You can call it whatever you want. The component to add/remove was listed elsewhere in this thread. Post 101/103

Anyway, the ultimo4k dev build built fine. Which Ubuntu version are you using?

 

[ronand]

Ideally you would want to be on version 20 of Ubuntu. No problems here building the dev build of Vix 5.4 or OpenATV 6.5.

 

[lincsat]

Homebuild is just name of image. You can call it whatever you want. The component to add/remove was listed elsewhere in this thread. Post 101/103

Anyway, the ultimo4k dev build built fine. Which Ubuntu version are you using?

I'm on 18.04 LTE. I saw those posts to add/remove components from the image, I though you were talking about removing components from the compile.

I'll have another go at compiling from clean and if all else fails, look to upgrading to Ubuntu 20

 

[bbbuk]

I built successfully vix 4.4 branch but "release" version. This was on 18.04.4 LTS

I'll build the developer now and post back.

 

[bbbuk]

I built successfully vix 4.4 branch but "release" version. This was on 18.04.4 LTS

I'll build the developer now and post back.

Successfully built developer version without any issues on 18.04.4 LTS

 

[birdman]

I have attached what I believe are the correct logs. I've not tried building a developer image before, so may have screwed something up. Are you guys succeeding in building the latest developer image?

nfs:

arm-oe-linux-gnueabi-gcc: error: unrecognized -march target: native

How did that get there? It was removed from the Makefile for 4.4.

webkit:

....arm-oe-linux-gnueabi/9.2.0/ld: ./.libs/libwebkitgtk-1.0.so: undefined reference to `WebCore::AccessibilityRenderObject::de|ach()'

That de|ach looks suspiciously like it should be detach. That's a 1-bit error. Which could be a CPU or disk error?
Do you have any other issues on this system?

 

[ronand]

A failing hard drive will cause all sorts of problems like this. Its tempting to use an old machine/drive for these purposes especially if you are not normally using linux.

If you want to start again on another drive/clean system the steps needed to set up the build environment are listed at

github.com/openatv/enigma2

- just substitute openvix for openatv

The only errors you should really be seeing are fetch errors when sources are temporarily unavailable.

 

[twol]

ronand is correct - just check which OpenATV enigma2 branch you are looking at - the default for OpenATV is 6.4 and has build info for Ubuntu 18.04. ATV branch 6.5 is building on Ubuntu 20.04 and has different specs mainly because they are using it to build a python 3 image.

 

[lincsat]

I built the release version OK after cleaning and re-cloning the sources, will try again with developer.

The system isn't new but not old. Water cooled Intel i7, 8 core, 16 Gig RAM, 240GB SSD.

I can't imagine a processor or SSD error would cause the same error on several different attempts, something corrupted on the download sounds more likely especially as it seems to be working after a fresh download - thanks for all the suggestions

 

[ronand]

If it works after a fresh download that indicates possibly something in your sources folder was corrupted (usually a HDD error in my experience). It would probably be no harm to test the ram and ssd to be sure. Anyway don't let that put you off!

 

[BrianTheTechieSnail]

I built the release version OK after cleaning and re-cloning the sources, will try again with developer.
The system isn't new but not old. Water cooled Intel i7, 8 core, 16 Gig RAM, 240GB SSD.
I can't imagine a processor or SSD error would cause the same error on several different attempts, something corrupted on the download sounds more likely especially as it seems to be working after a fresh download - thanks for all the suggestions

Please, may I ask how long it takes to build on that system?
I'm thinking of having a go at this myself.

 

[ronand]

An initial build might take around 10-12 hours on such a system - further builds don't take too long as most of the downloading and compiling doesn't need to be redone.

 

[birdman]

An initial build might take around 10-12 hours on such a system.

My 6+ years old i5 laptop only takes ~4 hours.

 

[lincsat]

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?

 

[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.

View attachment 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.