i saw a similar problem on bug 59887 and posted, but it was already resolved and marked as an amd64 only problem. furthermore, the solution was switching to gcc-3.4 and that is not a great option for production machines.. Reproducible: Always Steps to Reproduce: 1. emerge -uD world (catches mozilla) 2. 3.
i tried again and it fixed itself.. wtf?
I can't reproduce this bug anymore, and it already fixed itself, closing it.
Sorry for the noise, reopening to leave it up to the mozilla herd under advice from a dev
It appears there's nothing to do here. If you find the problem again on recent versions in portage, please re-open