From: Dr Rainer Woitok <rainer.woitok@gmail.com>
To: cygwin@cygwin.com
Subject: How to correctly rebase?
Date: Wed, 14 Oct 2015 14:26:00 -0000 [thread overview]
Message-ID: <22046.25592.311399.765933@woitok.gmail.com> (raw)
Cygwinners,
Currently I'm a bit at my wit's end :-/
I locally built a product from source (Gdal), and while running the test
programs, I got
python2.7 8800 child_info_fork::abort: unable to remap _gdalconst.dll
to same address as parent (0x260000) - try running rebaseall
Searching a bit, I found
/usr/share/doc/Cygwin/_autorebase.README
telling me to place the list of absolute paths of my personal DLLs into
/var/lib/rebase/user.d/Rainer", to run "rebase-trigger fullrebase" (it
didn't advice to run this from a privileged account, but I found out my-
self), and finally to simply run "setup_x86.exe" in the normal way, that
is, without any other Cygwin processes executing.
After doing so, I rebooted and tested again, but this time I got
python2.7 8136 child_info_fork::abort: address space needed by
'_io.dll' (0x370000) is already occupied
2324 [main] python2.7 9104 child_info_fork::abort: unable to remap
time.dll to same address as parent (0x270000) - try running rebaseall
However, these two libraries are both residing in
/usr/lib/python2.7/lib-dynload/
and have nothing to do with my own Gdal libraries. And running Mercuri-
al or almost any other Python application now fails, asking me to "try
running rebaseall". I then tried to run
rebaseall -v -T /var/lib/rebase/user.d/Rainer
directly from a privileged Ash Shell (again without any other Cygwin ac-
tivity) returning me a fine list of new bases and sizes for all librar-
ies, but Python still refuses to work.
What did I do wrong (to avoid it in the future) but more importantly,
how can I remedy the current situation?
Any quick help appreciated, since Python and Mercurial are vital for me.
Sincerely,
Rainer
PS: Please also reply by personal mail to me, as I am not subscribed to
this mailing list.
--
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
next reply other threads:[~2015-10-14 14:26 UTC|newest]
Thread overview: 27+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-10-14 14:26 Dr Rainer Woitok [this message]
2015-10-14 17:27 ` Warren Young
2015-10-14 19:27 ` Achim Gratz
2015-10-14 21:30 ` Warren Young
2015-10-14 22:08 ` Warren Young
2015-10-14 22:37 ` Warren Young
2015-10-15 7:53 ` Achim Gratz
2015-10-15 7:15 ` Achim Gratz
2015-10-15 13:16 ` Dr Rainer Woitok
2015-10-15 20:54 ` Warren Young
2015-10-15 21:10 ` Ken Brown
2015-10-16 12:57 ` Dr Rainer Woitok
2015-10-16 12:58 ` Ken Brown
2015-10-16 15:08 ` Ken Brown
2015-10-16 15:16 ` cyg Simple
2015-10-16 15:29 ` Ken Brown
2015-10-16 15:50 ` Andrey Repin
2015-10-18 11:15 ` Dr Rainer Woitok
2015-10-18 11:59 ` Achim Gratz
2015-10-18 12:45 ` Ken Brown
2015-10-18 16:20 ` Dr Rainer Woitok
2015-10-19 23:59 ` Warren Young
2015-10-20 16:55 ` Dr Rainer Woitok
2015-10-16 7:21 ` Achim Gratz
2015-10-16 20:11 ` Warren Young
2015-12-18 16:28 ` Achim Gratz
2015-10-14 19:58 ` Achim Gratz
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=22046.25592.311399.765933@woitok.gmail.com \
--to=rainer.woitok@gmail.com \
--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).