Summary: | sys-devel/libtool-2.2.8 fails with access violation on /dev/dri/card0 via `print` when /usr/Amaya/wx/bin/print exists | ||
---|---|---|---|
Product: | Gentoo Linux | Reporter: | keenblade <keenblade> |
Component: | [OLD] Core system | Assignee: | Gentoo Linux bug wranglers <bug-wranglers> |
Status: | RESOLVED CANTFIX | ||
Severity: | normal | ||
Priority: | High | ||
Version: | unspecified | ||
Hardware: | AMD64 | ||
OS: | Linux | ||
Whiteboard: | |||
Package list: | Runtime testing required: | --- | |
Attachments: |
full build log
full build log emerge --info --verbose output of "strace -f -s 4096 -o log ebuild libtool-2.2.8.ebuild compile" |
Description
keenblade
2010-05-28 03:53:21 UTC
Fabulous, now, how about attaching full build log ? Created attachment 233377 [details]
full build log
Ok. Here the full fail build log is.
2.2.7b is going away, so double check 2.2.8 ... not that this error really makes sense in the first place ... post `emerge --info --verbose` as an attachment (In reply to comment #3) > 2.2.7b is going away, so double check 2.2.8 ... not that this error really > makes sense in the first place ... > > post `emerge --info --verbose` as an attachment > I checked 2.2.8 and it fails to build, too. The error is the same. I am attaching new build log and "emerge --info --verbose". Created attachment 234447 [details]
full build log
full build log for libtool-2.2.8
Created attachment 234449 [details]
emerge --info --verbose
Bug 192548, Bug 192872, Bug 192540... Running ati-drivers or some other "special" drivers? (In reply to comment #7) > Bug 192548, Bug 192872, Bug 192540... Running ati-drivers or some other > "special" drivers? > I use xf86-video-nouveau-0.0.16_pre20100510 which is in portage for my nvidia card. Also x11-drivers/nvidia-drivers-195.36.24 is installed which is in portage. But I use nouveau at the moment. if you run each step manually via `ebuild`, does it still fail ? might be useful to get to the compile step and run that through strace: strace -f -s 4096 -o log ebuild libtool-2.2.8.ebuild compile Created attachment 234615 [details] output of "strace -f -s 4096 -o log ebuild libtool-2.2.8.ebuild compile" (In reply to comment #10) > if you run each step manually via `ebuild`, does it still fail ? > > might be useful to get to the compile step and run that through strace: > strace -f -s 4096 -o log ebuild libtool-2.2.8.ebuild compile > Running each step manually via ebuild, it does not fail. Although compile phase gives the same sandbox error, install and qmerge phases goes fine. The log file for strace output is 640mb sized. But I attached the console output of the strace you wanted sized 57kb. whatever is installing this is broken: /usr/Amaya/wx/bin/print nothing should be installing a binary named `print` Amaya would be bug #165280. The workaround for this "bug" is to remove the Amaya bin directory from your PATH variable. For Gentoo there is nothing here to fix. SpanKY and Jeroen Roovers, thank you both. You were right. Amaya was the problem. The bug is solved for me now. Many thanks again. |