Summary: | net-libs/webkit-gtk-1.10.2-r300 failed | ||
---|---|---|---|
Product: | Gentoo Linux | Reporter: | dama <maruiming2010> |
Component: | [OLD] GNOME | Assignee: | Gentoo Linux Gnome Desktop Team <gnome> |
Status: | RESOLVED INVALID | ||
Severity: | normal | CC: | gentoo-bugs |
Priority: | Normal | ||
Version: | unspecified | ||
Hardware: | AMD64 | ||
OS: | Linux | ||
Whiteboard: | |||
Package list: | Runtime testing required: | --- | |
Attachments: | This is my configuration |
Description
dama
2013-04-11 01:47:21 UTC
Created attachment 345160 [details]
This is my configuration
That looks as if you ran out of disk space / memory while compiling. Going lower than '-j5' *might* help in such case. Thank you Rafał Mużyło. You are right, I do with what you said and all is OK now! @gnome team, how to deal with this? I am not sure if we can solve or workaround it in any way :/ (In reply to comment #4) > @gnome team, how to deal with this? I am not sure if we can solve or > workaround it in any way :/ Overestimating capabilities of your hardware isn't any type of bug (except maybe PEBCAK). In this case it's not even disk space, which (to a point) can be estimated and/or calculated beforehand). I'd say leave it alone. While webkit-gtk is a bit greedy in regard of the resources it uses during build, it's not the only such package. Only you have the power to adapt your configuration to your hardware. It cannot and will never be automagic from Gentoo. You can find on my github repository an example of configuration specific for webkit-gtk so it does not build with too many jobs and exhaust memory. See https://github.com/EvaSDK/etc-portage/blob/master/env/j2-build.conf https://github.com/EvaSDK/etc-portage/blob/master/package.env https://github.com/EvaSDK/etc-portage Do not use the i-know-what-i-am-doing.conf as it probably does not fit your needs (it fits mine). |