Summary: | net-libs/libfwbuilder-4.0.1: sandbox error (ACCESS VIOLATION) | ||
---|---|---|---|
Product: | Gentoo Linux | Reporter: | Juergen Rose <rose> |
Component: | Current packages | Assignee: | Joshua Kinard <kumba> |
Status: | RESOLVED CANTFIX | ||
Severity: | normal | ||
Priority: | High | ||
Version: | 10.0 | ||
Hardware: | All | ||
OS: | Linux | ||
Whiteboard: | |||
Package list: | Runtime testing required: | --- | |
Bug Depends on: | 174351 | ||
Bug Blocks: | |||
Attachments: | /var/tmp/portage/net-libs/libfwbuilder-4.0.1/temp/build.log |
Description
Juergen Rose
2010-06-06 06:48:37 UTC
Hi, can you please attach the build.log and the environment from /var/tmp/portage/net-libs/libfwbuilder-4.0.1/temp to display the use flag setup and such things. Thanks, Michael Created attachment 234345 [details]
/var/tmp/portage/net-libs/libfwbuilder-4.0.1/temp/build.log
kumba, i've CC'ed you because of you being the last comitter (just some hours before this bug), complaint to me if you don't agree or cannot handle this. Michael If I erase distcc (emerge -C distcc), I can emerge libfwbuilder-4.0.1 Michael, I don't think there's a workable fix for this. I dug up Bug #174351, which highlights the apparent crux of the issue, and it looks like these two features (distcc and sandbox) aren't compatible. The violation is caused not by the package being merged, but by distcc itself trying to write to its log file, so I think it's that, or some other element of portage/sandbox that needs to be addressed, not libfwbuilder. Marking as CANTFIX until the dependent bug is resolved or someone advises of a better solution. FYI, I'm working on a 4.1.1 release, too, so that will probably also be affected by this. |