There are some ebuilds where emerge works till it prints "source unpacked" and after that nothing happens: following are: *libstdc++-v3-3.3.6 *lm_sensors-2.9.1 http://forums.gentoo.org/viewtopic-t-365978.html my portage-version 2.0.51.22-r2, but other versions could be affected too. Reproducible: Always Steps to Reproduce: 1. 2. 3. phillipo stated that filter-flags "-fstack-protector" is causing the problem
Apparently it was hung in awk. In the forums Boef reported that after emerge sync it was fixed. +++ i686-pc-linux-gnu-gcc -v ++ local specfiles= ++ awk -v spec=cc1 'BEGIN { sstr=""; outside=1 } $1=="*"spec":" { sstr=""; outside=0; next } outside || NF==0 || ( substr($1,1,1)=="*" && substr($1,length($1),1)==":" ) { outside=1; next } { sstr=sstr $0 } END { print sstr }'
*** Bug 101135 has been marked as a duplicate of this bug. ***
Martin, when raising bugs, it is important that you _always_ attach the output of 'emerge info'. Please do so in the future. For the record, problem was triggered by use of gcc-4 which doesn't (yet?) have any specs files, causing the 'awk' invocation to sit waiting for stdin (fixed by azarah in toolchain-funcs).