public inbox for cygwin@cygwin.com
 help / color / mirror / Atom feed
From: Ken Brown <kbrown@cornell.edu>
To: cygwin@cygwin.com
Subject: Re: bzr problem
Date: Fri, 12 Jul 2013 00:59:00 -0000	[thread overview]
Message-ID: <51DF39CE.8050405@cornell.edu> (raw)
In-Reply-To: <b4m4nc1emxb.fsf@jpl.org>

On 7/11/2013 12:32 AM, Katsumi Yamaoka wrote:
> Hi,
>
> Recently /usr/bin/bzr doesn't work well.  For the Emacs trunk,
> those two commands achieve the purpose even if issuing a warning:
>
> $ bzr update
> $ bzr commit -m "Bla bla"
>
> Usually a warning is like:
> 0 [main] python2.7 1264 child_info_fork::abort: address space needed by 'math.dll' (0x800000) is already occupied
>
> But it is sometimes:
> 1 [main] python2.7 5784 child_info_fork::abort: unable to remap _ARC4.dll to same address as parent (0xBE0000) - try running rebaseall
>
> Rebaseall doesn't help.  Reinstalling bzr+python doesn't, either.

Did you run rebaseall *after* reinstalling bzr and python?  Reinstalling 
undoes the rebasing.  If that still doesn't help, try looking at the 
output of 'rebase -is' to see if it shows DLL collisions (marked with an 
asterisk).  You might also try moving /etc/rebase.db.i386 out of the way 
and the running rebaseall again, so that it can start with a clean slate.

Ken


--
Problem reports:       http://cygwin.com/problems.html
FAQ:                   http://cygwin.com/faq/
Documentation:         http://cygwin.com/docs.html
Unsubscribe info:      http://cygwin.com/ml/#unsubscribe-simple

  reply	other threads:[~2013-07-11 23:04 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-07-11  7:28 Katsumi Yamaoka
2013-07-12  0:59 ` Ken Brown [this message]
2013-07-12  3:17   ` Katsumi Yamaoka
2013-07-12  3:48   ` Katsumi Yamaoka
2013-07-12 19:23 ` Achim Gratz
2013-07-16  5:10   ` Katsumi Yamaoka
2013-07-16  7:05     ` Achim Gratz
2013-07-16 11:35       ` Katsumi Yamaoka
2013-07-16 18:47         ` Achim Gratz
2013-07-18  9:00           ` Katsumi Yamaoka

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=51DF39CE.8050405@cornell.edu \
    --to=kbrown@cornell.edu \
    --cc=cygwin@cygwin.com \
    /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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).