Summary: | ACCESS VIOLATION (access_wr) emerging dev-python/pyogg-1.3-r1 | ||
---|---|---|---|
Product: | Gentoo Linux | Reporter: | Bill Skellenger <william> |
Component: | New packages | Assignee: | Gentoo Linux bug wranglers <bug-wranglers> |
Status: | RESOLVED DUPLICATE | ||
Severity: | normal | CC: | ticho |
Priority: | High | ||
Version: | unspecified | ||
Hardware: | x86 | ||
OS: | Linux | ||
Whiteboard: | |||
Package list: | Runtime testing required: | --- |
Description
Bill Skellenger
2006-10-22 17:44:56 UTC
Hm, even sandbox bombs: make[2]: Nothing to be done for `all-am'. make[2]: Leaving directory `/var/tmp/portage/sandbox-1.2.17/work/build-default-i686-pc-linux-gnu' make[1]: Leaving directory `/var/tmp/portage/sandbox-1.2.17/work/build-default-i686-pc-linux-gnu' >>> Source compiled. --------------------------- ACCESS VIOLATION SUMMARY --------------------------- LOG FILE = "/tmp/sandbox-sys-apps_-_sandbox-1.2.17-12664.log" access_wr: / -------------------------------------------------------------------------------- There is a helpful tip when emerging sandbox: >>> Source unpacked. >>> Compiling source in /var/tmp/portage/sandbox-1.2.17/work/sandbox-1.2.17 ... * If configure fails with a 'cannot run C compiled programs' error, try this: * FEATURES=-sandbox emerge sandbox ACCESS DENIED access_wr: / * Configuring sandbox for ABI=default... * econf: updating sandbox-1.2.17/config.guess with /usr/share/gnuconfig/config.guess These tips are great -- at least it points the user in a direction so that they can try to fix the problem themselves. I didn't get the indicated message (cannot run C compiled programs), but I *was* able to install sandbox using the indicated command: FEATURES=-sandbox emerge sandbox >>> sys-apps/sandbox-1.2.17 merged. Improving this warning might be warranted. After the sandbox upgrade:
>>> dev-python/pyogg-1.3-r1 merged
|