33 replies to this topic

[countpierre]

I have the following error :

 

"

ERROR: Failed to spawn fakeroot worker to run OpenPLi-develop/openembedded-core/meta/recipes-kernel/linux-libc-headers/linux-libc-headers_5.2.bb:do_install: [Errno 32] Broken pipe
WARNING: OpenPLi-develop/bitbake/lib/bb/runqueue.py:2128: ResourceWarning: unclosed file <_io.BufferedWriter name=27>
  return True

WARNING: OpenPLi-develop/bitbake/lib/bb/runqueue.py:2128: ResourceWarning: unclosed file <_io.BufferedReader name=28>
  return True

"

 

Any ideas?

[WanWizard]

Check if everything in "./OpenPLi-develop" is owned by the user you're are building with, and chown if not.

 

It can also be caused by an issue in Python 3.5 (on the host), so check which version your distro is using.

[countpierre]

Check if everything in "./OpenPLi-develop" is owned by the user you're are building with, and chown if not.

 

It can also be caused by an issue in Python 3.5 (on the host), so check which version your distro is using.

 

All owned by build user. Directory structure was built and cloned using the build user.

 

python --version
Python 2.7.13
python3 --version
Python 3.5.3
 

[countpierre]

sudo apt list python*
Listing... Done
python/oldstable,now 2.7.13-2 i386 [installed]
python2.7/oldstable,oldstable,now 2.7.13-2+deb9u3 i386 [installed]
python3/oldstable,now 3.5.3-1 i386 [installed,automatic]
python3.5/oldstable,now 3.5.3-1+deb9u2 i386 [installed,automatic]
 

[WanWizard]

Our buildservers are on 3.5.2, and I've never seen it there. So for the moment I'm out of ideas.

[countpierre]

Our buildservers are on 3.5.2, and I've never seen it there. So for the moment I'm out of ideas.

 

Thank you for looking.

[dax]

Our buildservers are on 3.5.2, and I've never seen it there. So for the moment I'm out of ideas.

 

Did you mean that is possible to build image for all box in environment by using python 3?

[WanWizard]

Not sure what you mean. This is about bitbake, and that uses Python 3. It has nothing to do with the image itself.

[masterw]

I had same kind of error here with when trying to bitbake oscam on a Linux Mint 18.3 32-bit hardware (old laptop).

Then I tried on a Centos 8 64-bit machine and no problems.

 

Perhaps something not supported anymore under 32-bit (i386) environment.

At least following post on github is suggesting this.

[WanWizard]

Quite possible. All our buildservers are Ubuntu x86-64, I use CentOS x86-64 myself as well. Never tried a 32 bit...

[Erik Slagter]

I had same kind of error here with when trying to bitbake oscam on a Linux Mint 18.3 32-bit hardware (old laptop).

Then I tried on a Centos 8 64-bit machine and no problems.

 

Most CPU's from about 2004 onwards are 64 capable. Don't be fooled by lagging Windows support. So I guess you really could install a 64 bit Linux on your laptop.

Edited by Erik Slagter, 25 September 2020 - 09:23.

[countpierre]

 

I had same kind of error here with when trying to bitbake oscam on a Linux Mint 18.3 32-bit hardware (old laptop).

Then I tried on a Centos 8 64-bit machine and no problems.

 

Most CPU's from about 2004 onwards are 64 capable. Don't be fooled by lagging Windows support. So I guess you really could install a 64 bit Linux on your laptop.

 

 

Yes 32 bit problem.

 

Upgraded server to 64 bit and it works.

 

Thanks.

[countpierre]

I noticed that the build finished without building an "nfi" image.

There was only a "ubifs" image.

 

How do I get an "nfi" image??

Edited by countpierre, 7 October 2020 - 14:10.

[WanWizard]

There seems to be something wrong (in the BSP perhaps), as it doesn't produce an nfi anymore on our build servers too.

[mimisiku]

Luckily, the number of DM8000 users is dwindli g fast

[WanWizard]

It's clear nobody in the team still uses it, as far as I can see, it went wrong in develop around the end of May, and nobody noticed...

[countpierre]

It's clear nobody in the team still uses it, as far as I can see, it went wrong in develop around the end of May, and nobody noticed...

 

It still works in release-7.3.

 

Can I use meta-dream from here in some way?

 

Luckily, the number of DM8000 users is dwindli g fast

 

Then why have meta-dream submodule?

AFAIK dm8000 is the only supported dream multimedia box.

[WanWizard]

You can't compare the two.

 

I've gotten to the point that I can get it to build again, and I've forwarded the diff to forum member Neo who maintains the meta-dream BSP.

 

But now it fails to build lots of wifi kernel drivers, giving me the impression it is broken in develop for much longer than May.

[countpierre]

You can't compare the two.

 

I've gotten to the point that I can get it to build again, and I've forwarded the diff to forum member Neo who maintains the meta-dream BSP.

 

But now it fails to build lots of wifi kernel drivers, giving me the impression it is broken in develop for much longer than May.

 

My last successful build of develop that gave an nfi image was back on 25th May.

 

But I then switched to the stable 7.3 while all the kernel rework was being done.

 

 

Okay, I will see what comes back.

 

Thanks for looking.

Edited by countpierre, 8 October 2020 - 14:34.

[WanWizard]

Give me some time, I don't have the mental energy to work on something for every long, so I have to spread it over multiple days.