From: Wagner Vaz <wagvaz@gmail.com>
To: gentoo-user@lists.gentoo.org
Subject: Re: [gentoo-user] Segmentation fault on Emerge -S
Date: Thu, 12 Oct 2006 15:38:15 -0300 [thread overview]
Message-ID: <20061012153815.1b086816@owl.gotdns.org> (raw)
In-Reply-To: <200610121058.21689.bo.andresen@zlin.dk>
[-- Attachment #1: Type: text/plain, Size: 2156 bytes --]
On Thu, 12 Oct 2006 10:58:18 +0200
Bo Ørsted Andresen <bo.andresen@zlin.dk> 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
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 189 bytes --]
prev parent reply other threads:[~2006-10-12 18:48 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-10-12 7:59 [gentoo-user] Segmentation fault on Emerge -S Wagner Vaz
2006-10-12 8:35 ` Alan McKinnon
2006-10-12 8:58 ` Bo Ørsted Andresen
2006-10-12 18:38 ` Wagner Vaz [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20061012153815.1b086816@owl.gotdns.org \
--to=wagvaz@gmail.com \
--cc=gentoo-user@lists.gentoo.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox