From: Alexander Clark <aclark@wayfm.com>
To: "gentoo-user@lists.gentoo.org" <gentoo-user@lists.gentoo.org>
Subject: Re: [gentoo-user] troubles with emerge --sync
Date: Thu, 19 Nov 2009 17:03:05 -0700 [thread overview]
Message-ID: <1F0A5BEE-D3A6-4CF4-B8CD-86F8C77B76E5@wayfm.com> (raw)
In-Reply-To: <594DAC8C-5D3B-4A88-A831-76237841A4B8@wayfm.com>
So I managed to fix the other wonkiness on my system (viz, gcc and
emacs not emerging). Turns out, I had been sloppy in putting together
my make.conf and used march=prescott when I should have been using
march=pentium4. Fixed it, ran emerge -uDNe world. Things emerge now.
Unfortunately, the original problem with emerge --sync has not been
resolved:
rsync error: sibling process crashed (code 15) at main.c(1505)
[generator=3.0.6]
>>> Retrying...
and from dmesg:
grsec: signal 4 sent to /usr/bin/rsync[rsync:32164] uid/euid:0/0 gid/
egid:0/0, parent /usr/bin/rsync[rsync:32163] uid/euid:0/0 gid/egid:0/0
Still getting this error. I took a look at the core dump using gdb:
(no debugging symbols found)
Core was generated by `rsync --recursive --links --safe-links --perms
--times --compress --force --who'.
Program terminated with signal 4, Illegal instruction.
> Use my mirror and see if things are better.
Alan, thanks for letting me try this. Unfortunately, same result. I
actually set up my own as well. All the other boxen in the rack are
able to sync to it, but not this one.
I've tried re-emerging portage and rsync to no avail.
I'm running out of ideas...
Alexander Clark
next prev parent reply other threads:[~2009-11-20 0:04 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-11-11 19:01 [gentoo-user] troubles with emerge --sync Alexander Clark
2009-11-11 19:03 ` Marcus Wanner
2009-11-11 19:13 ` Alan McKinnon
2009-11-11 19:52 ` Alex Bennee
2009-11-11 21:10 ` Alexander Clark
2009-11-11 23:04 ` Marcus Wanner
2009-11-12 9:57 ` Alan McKinnon
2009-11-12 11:05 ` Nelis Botha
2009-11-12 11:22 ` Alan McKinnon
2009-11-20 0:03 ` Alexander Clark [this message]
2009-11-30 1:27 ` daid kahl
2009-12-03 23:41 ` [gentoo-user][SOLVED] " Alexander Clark
2009-12-04 23:20 ` daid kahl
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=1F0A5BEE-D3A6-4CF4-B8CD-86F8C77B76E5@wayfm.com \
--to=aclark@wayfm.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