in the past, these flags did more. today, they do one thing -- force gcc-config to be run. but the current logic should already take care of that. can you try building stages with this change: should_we_gcc_config() { # we always want to run gcc-config if we're bootstrapping, otherwise # we might get stuck with the c-only stage1 compiler - use_if_iuse bootstrap && return 0 - use build && return 0 # if the current config is invalid, we definitely want a new one
I'll test this change during this weekend and will report back.
Jorge said things seemed to work for him http://sources.gentoo.org/eclass/toolchain.eclass?r1=1.567&r2=1.568
