On Thu, 12 Oct 2006 10:58:18 +0200 Bo Ørsted Andresen <[EMAIL PROTECTED]> wrote: > It really would help if we knew what version you were running. Try > this: > > # emerge -u portage
owl ~ # emerge -pu portage These are the packages that would be merged, in order: Calculating dependencies... done! > # emerge -u python owl ~ # emerge -pu python These are the packages that would be merged, in order: Calculating dependencies... done! [ebuild U ] dev-libs/openssl-0.9.8d [0.9.7j] USE="-sse2%" [ebuild U ] sys-libs/ncurses-5.5-r3 [5.5-r2] USE="gpm* -trace%" [ebuild U ] dev-lang/python-2.4.3-r4 [2.4.3-r1] USE="-tk%" (Emerged python with -u) > # python-updater owl ~ # python-updater * Can't determine any previous Python version(s). > # revdep-rebuild owl ~ # revdep-rebuild -p Configuring search environment for revdep-rebuild Checking reverse dependencies... Packages containing binaries and libraries broken by a package update will be emerged. Collecting system binaries and libraries... done. (/root/.revdep-rebuild.1_files) Collecting complete LD_LIBRARY_PATH... done. (/root/.revdep-rebuild.2_ldpath) Checking dynamic linking consistency... done. (/root/.revdep-rebuild.3_rebuild) Assigning files to ebuilds... Nothing to rebuild Evaluating package order... done. (/root/.revdep-rebuild.5_order) Dynamic linking on your system is consistent... All done. > If after that you still see the above behaviour: > > # emerge --debug -S netrw &> debug.log > # gzip debug.log > > Then attach debug.log.gz and post that together with the output of: > > # emerge --info owl ~ # emerge -S netrw Searching... [ Results for search key : netrw ] [ Applications found : 0 ] There is no netrw in portage tree. XD But thanks guys, it will help me in some way, now emerge -S netrw does not Segmentation Fault. Seems to solved. -- Wagner Vaz Blog: http://wagnervaz.wordpress.com Linux User: #372744 GPG Key: B4D1B312 | Keyserver: subkeys.pgp.net
signature.asc
Description: PGP signature
