139 replies to this topic

[anudanan]

Devtoolset is the magic word. Maybe that is also possible under ubuntu, but I haven’t tested it

[WanWizard]

I've never seen it (but then I am a Redhat guy), software collections (https://www.software...ections.org/en/) is specific to RHEL and CentOS.

[-M-]

By reading this thread you can get scared it might be problem to build OpenPLi. Let me contribute with something positive... I was able to build, on my first attempt!
 
Thanks to all for doing a good work with OpenPLi
 
PS. I'm on an Ubuntu 18.04 host and did like this:

$ sudo apt install sed wget cvs subversion git-core coreutils unzip texi2html texinfo docbook-utils gawk python-pysqlite2 diffstat help2man make gcc build-essential g++ desktop-file-utils chrpath default-jre gettext zip
$ mkdir ~/OpenPLi
$ cd ~/OpenPLi
$ git clone https://github.com/OpenPLi/openpli-oe-core.git
$ cd openpli-oe-core
$ MACHINE=vuduo4k make
$ cd build
$ source env.source
$ export MACHINE=vuduo4k
$ bitbake openpli-enigma2-image

 I also build an enigma2-plugin and install it in the box with "opkg install" command.

Edited by -M-, 4 March 2019 - 08:50.

[serdeliuk]

Hi,

 

I upgraded my development system to Ubuntu 18.04 LTS, here are my steps to build first OpenPli 7.1 image for my Vu Solo4K

 

install Ubuntu 18.04 LTS

# Create your user

adduser marc

 

# grant sudo privileges

echo -e "\nmarcALL=(ALL:ALL) ALL" >> /etc/sudoers

 

# install required packages

apt-get install sed wget cvs subversion git-core \

  coreutils unzip texi2html texinfo docbook-utils \

  gawk python-pysqlite2 diffstat help2man make gcc build-essential g++ \

  desktop-file-utils chrpath default-jre gettext zip libssl-dev python3-distutils

 

# logout and login with your new user

 

# Clone OpenPli 7.1 branch in your home folder

git clone https://github.com/O...openpli-oe-core -b release-7.1 openpli-oe-core-7.1

 

# change to openpli-oe-core-7.1 directory

cd openpli-oe-core-7.1

 

# build first image "which can take few hours, depends on resources"

MACHINE=vusolo4k make image

 

At the end your new image is in openpli-oe-core-7.1/build/tmp/deploy/images/vusolo4k/openpli-homebuild-vusolo4k_usb.zip

 

You should add to your openpli-oe-core-7.1/build/conf/local.conf

MACHINE = "vusolo4k"

BRANCH = "release-7.1"

 

 

Best regards,

 

 

Marc

[serdeliuk]

Just to let you know, the tree grows dramatically after image build to 15GB, it has 8.1GB compressed at best, if you intend to migrate the build tree think twice

 

marc@ubuntu:~/0.VUPLUS$ du -skh ./*

15G ./openpli-oe-core-7.1

15G ./openpli-oe-core-7.1.tar

8.1G ./openpli-oe-core-7.1.tar.7z

Edited by serdeliuk, 5 August 2019 - 17:49.

[WanWizard]

It is all relative... 

wanwizard@buildserver2] $ df -h | grep oe
/dev/sdb2       807G  564G  202G  74% /openpli/oe/release-6.2
/dev/sda2       807G  255G  512G  34% /openpli/oe/release-7.1
 
[wanwizard@buildserver3] $ df -h | grep oe
/dev/sda2       807G  537G  230G  71% /openpli/oe/develop 
/dev/sdb2       807G  414G  353G  54% /openpli/oe/rc

[serdeliuk]

Haha, huge, i presume that there are all packages builded and entire cache. On my old machine i had only/max 38GB for 6.2, but builded only few packages "beside the image" + dependencies, most of my apps where builded on solo4k directly, which perform unexpectedly well.

 

I wonder why 7.1 is bigger than RC or develop.

 

Can you share infos regarding the hardware behind those buildservers? I am building my packages on a virtual machine under my OSX on a 256GB SSD but willing to purchase an old dual xeon with at least 32GB ram.

[Persian Prince]

 

There is a nice step-by-step guide here:

 

http://users.telenet...npliubuntu.html

 

Pr2

Probably we need to consider to "copy" this to our own Wiki.,...

 

 

You could update it with my last changes:

 

https://github.com/O...velop/README.md (pyro branch of OE)

 

https://github.com/O...oming/README.md (master branch of OE)

 

We're using my "image.sh" shell script which makes things easier

Edited by Persian Prince, 5 August 2019 - 21:34.

[-M-]

Respond to serdeliuk post yesterday:

You don't need a new user account and you don't need sudo.

PS. I haven't built 7.1 yet, but I really hope this haven't change.

[WanWizard]

Haha, huge, i presume that there are all packages builded and entire cache.

All images, all packages, complete sstate-cache, rm_work active for release images.
 

I wonder why 7.1 is bigger than RC or develop.

It's the other way around, the second value is "used". I suspect that for debug reasons the RC's where build without rm_work, and with buildhistory active (is used to generate the pinning in reporefs.conf).

 

Also, we've created a cleanup script that runs after every build, which hasn't run for rc, as that hasn't been build for a while.
 

Can you share infos regarding the hardware behind those buildservers?

 

Our buildervers are Intel Core i7 7700K machines, 32GB ram, with 2 SATA disks for storage and the OS (part in raid 1), and 2 Samsung EVO 970 1TB SSD disks for the images (hence two build directories per server).

[serdeliuk]

You don't need a new user account and you don't need sudo.

PS. I haven't built 7.1 yet, but I really hope this haven't change.

 

Hi mister -M-,

 

Indeed, but you're partially right and my previous statement is partially incomplete, i meant to say if your user is root you need to add a new user who will use bitbake, because bitbake will not run under root.

 

In regards to "sudo" just to compile packages or images is not required, but linux users knows that almost all the time you need to install packages and/or run privileged commands, so, sudo will be a nice addition instead of going back and forth between users.

 

 

Best regards,

 

 

Marc

Edited by serdeliuk, 6 August 2019 - 14:50.

[twol]

I am surprised that it runs in sudo as the sanity checker normally objects (certainly when I tried to run from a NAS - which is not supported)

[serdeliuk]

I am surprised that it runs in sudo as the sanity checker normally objects (certainly when I tried to run from a NAS - which is not supported)

 

Does not run in sudo as well as under root user/group, I mentioned sudo because it is useful to have easy access to OS package management yum, apt, etc, or to run privileged commands, as iptables  for examples.

 

Without sudo, the new user will need to logout and relogin with another user which have root access in order to install with apt-get any package.

[DimitarCC]

Hello,

I tried to build the latest develop branch of OpenPLi but i got a problem during build with facelocale.

it searching for locale no_NO (Norwegian) but in the git there is no_NN which i think is wrong. Also it complains about unrecognizable symbol U+00E5 in that file.

Could someone check?

Edited by DimitarCC, 8 August 2019 - 06:22.

[blzr]

yep, definitely this latest fakelocale commit is wrong...
actual language code is language_TERRITORY and not other way around (!)

(and other than that, for these new fakelocale to actually work, they also need to be added to locale.alias)

I'll try to provide PR with fix later today...

[DimitarCC]

@blzr Thanks. It will be great.

[blzr]

Should be fixed now...

[anudanan]

In the past I could built an openpli 7.3 Image on my ubuntu 18.04. Now i´ve a new ubuntu 22.04 system an can build the current developer branch, but not the release-7.x and release-8.x images.

 

I thought bitbake for 7,x and 8.x normally use python2 but on my ubunut 22.04 bitbake use python3 to build the image. I see different pyhton errors with python3.8, python3.10.

 

Is the a way to build with python2 on ubuntu systems 22.04 the release 7.x and 8.x?

Or how is the way to build 7.x and 8.x on ubuntu 22.04

 

I´ve installed update-alternatives to use different python or gcc/g++ versions

[anudanan]

To solve the build problems for openpli release-7.3 with ubuntu 22.04 now I´ve installed on an other harddisk the old ubunut 18.04 version to have a second build environment for the older images. Now the build process is running and until now I see no errors. Only a problem with an undefined ENOATTR is there but it were there also in the past and I can fix it by usind ENOENT instead of ENOATTR..

But it needs some time on my old core2 duo 6400 system to run the complete build and tomorrow or later i will see if it is successful or not

Edited by anudanan, 28 December 2022 - 17:19.

[anudanan]

I´ve tested an other way to build openpli 7.x and 8.x images under ubuntu 22.04 lts

I´ve installed docker on ubuntu 22.04 and inside a docker container I run an ubuntu 18.04 image. That works fine for me.