Gentoo Websites Logo
Go to: Gentoo Home Documentation Forums Lists Bugs Planet Store Wiki Get Gentoo!
Bug 101107 - sys-libs/libstdc++: emerge stops after "source unpacked"
Summary: sys-libs/libstdc++: emerge stops after "source unpacked"
Status: RESOLVED FIXED
Alias: None
Product: Gentoo Linux
Classification: Unclassified
Component: [OLD] Core system (show other bugs)
Hardware: All Linux
: High major (vote)
Assignee: Gentoo Toolchain Maintainers
URL:
Whiteboard:
Keywords:
: 101135 (view as bug list)
Depends on:
Blocks:
 
Reported: 2005-08-02 09:50 UTC by Martin Nowack
Modified: 2005-08-02 22:55 UTC (History)
3 users (show)

See Also:
Package list:
Runtime testing required: ---


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Martin Nowack 2005-08-02 09:50:10 UTC
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
Comment 1 Zac Medico gentoo-dev 2005-08-02 14:41:30 UTC
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 }' 
Comment 2 Stephen Amar 2005-08-02 15:41:21 UTC
*** Bug 101135 has been marked as a duplicate of this bug. ***
Comment 3 Kevin F. Quinn (RETIRED) gentoo-dev 2005-08-02 22:55:03 UTC
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).