30 replies to this topic

[TheCount]

Many thanks to everyone who contributed.

 

All sorted and working back on my original setup of a mounted usb drive.

[levi45@]

ERROR: enigma-info-homebuild-r0 do_install: ExecutionError('/home/mypc/openpli-oe-core/build/tmp/work/pulse4k-oe-linux-gnueabi/enigma-info/homebuild-r0/temp/run.do_install.8925', 128, None, None)
ERROR: Logfile of failure stored in: /home/mypc/openpli-oe-core/build/tmp/work/pulse4k-oe-linux-gnueabi/enigma-info/homebuild-r0/temp/log.do_install.8925
Log data follows:
| DEBUG: Executing python function extend_recipe_sysroot
| NOTE: Direct dependencies are ['virtual:native:/home/mypc/openpli-oe-core/openembedded-core/meta/recipes-devtools/pseudo/pseudo_git.bb:do_populate_sysroot']
| NOTE: Installed into sysroot: []
| NOTE: Skipping as already exists in sysroot: ['pseudo-native']
| DEBUG: Python function extend_recipe_sysroot finished
| DEBUG: Executing shell function do_install
| fatal: detected dubious ownership in repository at '/home/mypc/openpli-oe-core'
| To add an exception for this directory, call:
|
|     git config --global --add safe.directory /home/mypc/openpli-oe-core
| fatal: detected dubious ownership in repository at '/home/mypc/openpli-oe-core/openembedded-core'
| To add an exception for this directory, call:
|
|     git config --global --add safe.directory /home/mypc/openpli-oe-core/openembedded-core
| fatal: detected dubious ownership in repository at '/home/mypc/openpli-oe-core'
| To add an exception for this directory, call:
|
|     git config --global --add safe.directory /home/mypc/openpli-oe-core
| WARNING: /home/mypc/openpli-oe-core/build/tmp/work/pulse4k-oe-linux-gnueabi/enigma-info/homebuild-r0/temp/run.do_install.8925:174 exit 128 from 'OE_REVISION=`cd /home/mypc/openpli-oe-core && git rev-list --count HEAD`'
| WARNING: Backtrace (BB generated script):
|     #1: do_install, /home/mypc/openpli-oe-core/build/tmp/work/pulse4k-oe-linux-gnueabi/enigma-info/homebuild-r0/temp/run.do_install.8925, line 174
|     #2: main, /home/mypc/openpli-oe-core/build/tmp/work/pulse4k-oe-linux-gnueabi/enigma-info/homebuild-r0/temp/run.do_install.8925, line 388
| ERROR: ExecutionError('/home/mypc/openpli-oe-core/build/tmp/work/pulse4k-oe-linux-gnueabi/enigma-info/homebuild-r0/temp/run.do_install.8925', 128, None, None)
ERROR: Task (/home/mypc/openpli-oe-core/meta-openpli/recipes-openpli/enigma2/enigma-info.bb:do_install) failed with exit code '1'
NOTE: Tasks Summary: Attempted 1715 tasks of which 1709 didn't need to be rerun and 1 failed.

Summary: 1 task failed:
  /home/mypc/openpli-oe-core/meta-openpli/recipes-openpli/enigma2/enigma-info.bb:do_install
Summary: There was 1 WARNING message shown.
Summary: There was 1 ERROR message shown, returning a non-zero exit code.
make: *** [Makefile:131: image] Error 1

 

[WanWizard]

| fatal: detected dubious ownership in repository at '/home/mypc/openpli-oe-core'

 
You need to address these. It even tells you how.
 

git config --global --add safe.directory /home/mypc/openpli-oe-core/openembedded-core

This is git specific, and has nothing to do with building OE.

[levi45@]

 

| fatal: detected dubious ownership in repository at '/home/mypc/openpli-oe-core'

 
You need to address these. It even tells you how.
 

git config --global --add safe.directory /home/mypc/openpli-oe-core/openembedded-core

This is git specific, and has nothing to do with building OE.

 

Thanks i have miss that bit sorry. Also i have this error on building feeds about gtwebkit please can you see what is the issue many thanks . Or would you like me to open new thread for this issue ?

Attached Files

•  log   256.67KB   1 downloads

Edited by levi45@, Yesterday, 17:44.

[WanWizard]

Next time, yes, please, as this is unrelated. "fatal error: Killed signal terminated program cc1plus" is usually caused by the OOM killer kicking in, lack of memory for the compiler.

[levi45@]

Next time, yes, please, as this is unrelated. "fatal error: Killed signal terminated program cc1plus" is usually caused by the OOM killer kicking in, lack of memory for the compiler.

Thanks is that lack of swap memory or disk memory? . I have more than 480gb disk space free. May be you can move this posts from here to new thread not to confuse users please

[WanWizard]

No, memory memory . If this is the case, you should see OOM killer dumps in your dmesg or journal.

 

We've noticed on our buildservers that even with 16GB of memory, some recipes struggle, so you might have to do something about the number of BB threads and parallel make if it turns out lack of memory is the problem.

 

The issue is usually inbalance between number of CPU's and the total amount of memory. If one compile task takes 2GB, and you have a 16 core machine, you should have 32GB to deal with a maximum parallel build...

[levi45@]

No, memory memory . If this is the case, you should see OOM killer dumps in your dmesg or journal.

 

We've noticed on our buildservers that even with 16GB of memory, some recipes struggle, so you might have to do something about the number of BB threads and parallel make if it turns out lack of memory is the problem.

 

The issue is usually inbalance between number of CPU's and the total amount of memory. If one compile task takes 2GB, and you have a 16 core machine, you should have 32GB to deal with a maximum parallel build...

Sep  9 19:10:19 sss2222222 kernel: [852648.102770] Out of memory: Killed process 2617537 (cc1plus) total-vm:1257524kB, anon-rss:1149544kB, file-rss:0kB, shmem-rss:0kB, UID:1000 pgtables:2388kB oom_score_adj:0

 
 

[WanWizard]

I hate to be right....

 

We have this in our buildserver config:

# by default limit based on number of CPU threads
BB_NUMBER_THREADS = "${@min(len(os.sched_getaffinity(0))-2,18)}"
PARALLEL_MAKE = "-j ${@min(len(os.sched_getaffinity(0))-4,10)}"

# limit parallel make for these packages to prevent OOM issues
PARALLEL_MAKE:pn-kodi = "-j ${@min(len(os.sched_getaffinity(0))-4,8)}"
PARALLEL_MAKE:pn-qtwebengine = "-j ${@min(len(os.sched_getaffinity(0))-4,8)}"
PARALLEL_MAKE:pn-nodejs = "-j ${@min(len(os.sched_getaffinity(0))-4,8)}"
PARALLEL_MAKE:pn-chromium = "-j ${@min(len(os.sched_getaffinity(0))-4,8)}"

to limit parallelism generic, and limit it further for specific packages. I think for homebuilds you chould add it to your local.conf.

[levi45@]

I hate to be right....

 

We have this in our buildserver config:

# by default limit based on number of CPU threads
BB_NUMBER_THREADS = "${@min(len(os.sched_getaffinity(0))-2,18)}"
PARALLEL_MAKE = "-j ${@min(len(os.sched_getaffinity(0))-4,10)}"

# limit parallel make for these packages to prevent OOM issues
PARALLEL_MAKE:pn-kodi = "-j ${@min(len(os.sched_getaffinity(0))-4,8)}"
PARALLEL_MAKE:pn-qtwebengine = "-j ${@min(len(os.sched_getaffinity(0))-4,8)}"
PARALLEL_MAKE:pn-nodejs = "-j ${@min(len(os.sched_getaffinity(0))-4,8)}"
PARALLEL_MAKE:pn-chromium = "-j ${@min(len(os.sched_getaffinity(0))-4,8)}"

to limit parallelism generic, and limit it further for specific packages. I think for homebuilds you chould add it to your local.conf.

thank you very much , all try and let you know the outcome .

[WanWizard]

Note that these settings are for 16GB machines with 6 cores / 12 threads. You may have to adjust them for your hardware.