On Thursday, August 20, 2015 6:31:48 PM Alan Grimes wrote: > Fernando Rodriguez wrote: > > The ncurses ebuild is indeed broken, I ran into the same problem before. > > > > But you received good advice on your last thread (build libtinfo on another > > system and copy it or just try symlinking it to ncurses), if you'd followed it > > you would a got your system back up in a few minutes. > > ppl seem to be antsy to hear what I actually did, so I'll respond.... > > 1. I got my grubby mitts on a stage 3 tarball, I always keep one on hand > for this reason. =\ > > > 2. I grepped everything in /bin and /lib for tinfo and copied over from > the tarball where necessary.
You can not blindly mix and match files like that, this is likely what broke your compiler (if you copied only some gcc related files)! You where advised to copy the bash binary, or libtinfo.so (from another system), or symlink it to libncurses.so. All good advice but you chose to do something dumb. Now you may need to unpack a whole stage3, start over, and wait another 3 days. > 3. Started --emptytree world. > > 4. waited. > > 5. kicked it each time it stopped, > > 6. kicked it some more. > > 7. kicked it a few more times. > > 8, got to the end of the list about two and a half days later (which is > par for my machine.) > > 9. published the results. > > 10. rebooted. > > -- Fernando Rodriguez
