If you attempt to emerge =www-client/chromium-6.0.427.0, but don't have net-print/cups installed, it'll eventually error-out because it'll want to include some CUPS-related headers. It seems that it has something to do with (perhaps newly-introduced?) Google Cloud Print-specific code. The ebuild should be adjusted to accommodate this dependency on CUPS, as one would need to manually emerge net-print/cups before attempting to emerge Chromium.
Hello Dean, please attach the full build.log and environment files mentioned at the end of the ebuils. Michael
End comment the output of `emerge --info`.
Actually, it would appear that this has now been resolved since I filed this bug. I just looked at the ebuild for www-client/chromium-4.0.427.0 after syncing Portage just now, and the line ">=net-print/cups-1.3.5" was added to the RDEPEND variable, which was not there yesterday. If that's the case, then I guess this is resolved.
Yes, Bernard has fixed this. Thanks!