emerge --jobs shouldn't display any output from the underlying build, but I get the following on my screen: >>> Emerging (49 of 62) app-emulation/wine-1.6.1 >>> Installing (41 of 62) app-office/kmymoney-4.6.4 >>> Emerging (50 of 62) app-portage/layman-2.0.0-r1 >>> Installing (50 of 62) app-portage/layman-2.0.0-r1 >>> Emerging (51 of 62) media-video/dvdrip-0.98.11-r1 >>> Failed to emerge media-video/dvdrip-0.98.11-r1, Log file: >>> '/var/tmp/portage/media-video/dvdrip-0.98.11-r1/temp/build.log' >>> Jobs: 48 of 62 complete, 2 running, 1 failed Load avg: 6.25, 7.37, 5.57 (null)*(null) Unable to trace static ELF: /usr/sbin/prelink: /usr/sbin/prelink --reloc-only 0x7b800000 kernel32.dll.so >>> Jobs: 48 of 62 complete, 2 running, 1 failed Load avg: 5.19, 6.92, 5.50 (null)*(null) Unable to trace static ELF: /usr/sbin/prelink: /usr/sbin/prelink --reloc-only 0x7bc00000 ntdll.dll.so >>> Jobs: 48 of 62 complete, 2 running, 1 failed Load avg: 5.00, 6.82, 5.48 (null)*(null) Unable to trace static ELF: /usr/sbin/prelink: /usr/sbin/prelink --reloc-only 0x7ac00000 riched20.dll.so Note that this report is just about the bleeding. wine merges okay despite these.
why does wine run prelink in compile phase anyways? moreover, why doesn't the ebuild ever actually check USE=prelink? if it's automagic detection, what happens if prelink is depcleaned halfway through the build? also, will the binaries continue working if prelink is removed from the system?
(In reply to Tanktalus from comment #0) > emerge --jobs shouldn't display any output from the underlying build, but I > get the following on my screen: We could handle this in portage by creating a new terminal session for the ebuild and its child processes. This would also be useful for ensuring that all child processes are terminated when appropriate, as mentioned in bug 465008, comment #7.
(In reply to Alex Xu (Hello71) from comment #1) please read the ebuild & source if you're interested in knowing about wine<->prelink interaction. it isn't an accident. *** This bug has been marked as a duplicate of bug 431638 ***
