-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA256 On 21/08/15 08:31, 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....
Because we try to avoid flame wars and needless name-calling/swearing when looking for and providing support to people. Also because we kind of expect the original poster to respond to queries in a thread that they started. > 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. This is kind of dangerous. It would be safer to create/use a binary package. - From a running Gentoo system (including a stage3) you can create a binary package of an installed program by running quickpkg <category>/<package> This will place it in /usr/portage/packages by default (see PKGDIR in `man make.conf`). This is better than just randomly copying files from another system. There are also online hosts available that provide some packages (see my post in your previous thread). > 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. Emerge's '--keep-going' option may be of use to you here... > 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. So what you're saying is that you did an '--emptytree' build for which there were a number of failures; *one* of which was a segfault; some of which may not be valid; after arbitrarily copying some files from a stage3 of unknown age. Don't get me wrong, providing feedback and letting others know is good, but unless there's a baseline and/or more is known about what is going on (see Alan McKinnon's comment about others not getting this and something about your environment potentially causing this), we can't do much with it. More information about your environment, such as an `emerge --info` and relevant flags/settings for a specific package that is failing would go a fair way to giving us the information we need (and have asked for) to be able to help you. - -- wraeth <[email protected]> GnuPG Key: B2D9F759 -----BEGIN PGP SIGNATURE----- Version: GnuPG v2 iF4EAREIAAYFAlXWfM0ACgkQXcRKerLZ91k95wD/U7JAoA8RcjlJZfhEVTaHZZ/a wUdEi3bSFFQfaNVcZW4A/icPoS+XgpMIRAEnxbilUJwbWZoMsEpkLFK4YtdxjFbH =alwZ -----END PGP SIGNATURE-----
