I found a workaround. What happens is that it balks on the bison package; ylwrap isn't built correctly. However, to build the latest bison, you need to have a working c++ compiler, and when bootstrapping, you normally start with a stripped-down c compiler (iirc). The workaround is to chroot /var/tmp/catalyst/tmp/default/stage2*, then "emerge gcc bison", remove all except for the "unpack" file in the /var/tmp/catalyst/tmp/.autoresume-stage2*/, and re-try building the stage tarball you were on (for me, this is stage2). Kinda sloppy, but it seems to be working for me. -Jon
Todd Williams wrote: > Jon Hood <[EMAIL PROTECTED]> writes: > >> >> For the past few days, I've been trying to get binutils to build with >> catalyst. Has anyone else been running into this problem? > > > I've been having the same problem (identical error message). I've > tried to work > around the problem by using both catalyst v1&2 as well as masking out > binutils-2.16.1 in favor of an older version- all attempts result in > the same > failure. > > The 2.16.1 ebuild of binutils builds fine under most circumstances > including my > stage1 builds, but consistently dies during my stage2 builds. I first > noticed > this problem with a snapshot from late March. My previous snapshot > from Jan 27 > has the same version of binutils and builds just fine, so I suspect > the problem > was introduced elsewhere in the portage tree. > > Anyway, if anyone has suggestions for a solution it would be much > appreciated. > > -- > Todd > > > [EMAIL PROTECTED] mailing list > -- [EMAIL PROTECTED] mailing list
