Summary: | ebuild-ipc - src_unpack(): sandbox:stop caught signal 2 in pid 31535 | ||
---|---|---|---|
Product: | Portage Development | Reporter: | dE <de.techno> |
Component: | Core - Ebuild Support | Assignee: | Portage team <dev-portage> |
Status: | RESOLVED INVALID | ||
Severity: | normal | CC: | gabriel.misailidis |
Priority: | Normal | ||
Version: | unspecified | ||
Hardware: | All | ||
OS: | Linux | ||
Whiteboard: | |||
Package list: | Runtime testing required: | --- | |
Attachments: | www-client/chromium-10.0.648.133 build log |
Description
dE
2011-03-19 08:00:27 UTC
Created attachment 266443 [details]
www-client/chromium-10.0.648.133 build log
This is www-client/chromium build.log not mplayer. change python default to 2.6 #eselect python set python2.6 and try to rebuild. The defaults where python 2.6 How sure are you about? Give the output of #eselect python list unless you've solved the problem. according to the output python3 is used. $ eselect python list Available Python interpreters: [1] python2.6 * [2] python3.1 Please attach the environment file. Comment on attachment 266443 [details]
www-client/chromium-10.0.648.133 build log
* chromium-10.0.648.133.tar.bz2 RMD160 SHA1 SHA256 size ;-) ... [ ok ]
* Package: www-client/chromium-10.0.648.133
[...]
Are you experiencing this problem with any other packages, or just chromium? Do you remember anything in particular that changed just before you started experiencing this? (In reply to comment #6) > Please attach the environment file. It's empty. (In reply to comment #8) > Are you experiencing this problem with any other packages, or just chromium? Do > you remember anything in particular that changed just before you started > experiencing this? The chromium problem was cause of ffmpeg-9999. It's probably an upstream bug. Everything else compiles well. The log shows that the build was killed by signal 2 (SIGINT) which can be produced by kill or Ctrl-C. Did you use kill or Ctrl-C to kill it? If so, why did you do that? I don't remember. However this's the wrong log, I'll place the right one (the mplayer one) We have 11 comments up to now and practically no useful information to work with. Let's just discard this bug, and you can file a new one. |