From: Ken Brown <kbrown@cornell.edu>
To: cygwin@cygwin.com
Subject: Re: Cannot fork process for: g++: cygPocoFoundation.32.dll: Loaded to different address
Date: Sun, 08 Nov 2015 16:05:00 -0000 [thread overview]
Message-ID: <563F72D7.5070908@cornell.edu> (raw)
In-Reply-To: <563F661D.50503@orange.fr>
On 11/8/2015 10:11 AM, Francis ANDRE wrote:
> reinstalled poco-1.6.1 and the problem reappears...thsu, following your
> advises
>
> $ find stage/tools -name "*.dll" > dlls
> $ cat dlls
> stage/tools/lib/CYGWIN/i686/cygPocoCppParser.32.dll
> stage/tools/lib/CYGWIN/i686/cygPocoCppParser.dll
> stage/tools/lib/CYGWIN/i686/cygPocoCppParserd.32.dll
> stage/tools/lib/CYGWIN/i686/cygPocoCppParserd.dll
> stage/tools/lib/CYGWIN/i686/cygPocoFoundation.32.dll
> stage/tools/lib/CYGWIN/i686/cygPocoFoundation.dll
> stage/tools/lib/CYGWIN/i686/cygPocoFoundationd.32.dll
> stage/tools/lib/CYGWIN/i686/cygPocoFoundationd.dll
> stage/tools/lib/CYGWIN/i686/cygPocoJSON.32.dll
> stage/tools/lib/CYGWIN/i686/cygPocoJSON.dll
> stage/tools/lib/CYGWIN/i686/cygPocoJSONd.32.dll
> stage/tools/lib/CYGWIN/i686/cygPocoJSONd.dll
> stage/tools/lib/CYGWIN/i686/cygPocoNet.32.dll
> stage/tools/lib/CYGWIN/i686/cygPocoNet.dll
> stage/tools/lib/CYGWIN/i686/cygPocoNetd.32.dll
> stage/tools/lib/CYGWIN/i686/cygPocoNetd.dll
> stage/tools/lib/CYGWIN/i686/cygPocoUtil.32.dll
> stage/tools/lib/CYGWIN/i686/cygPocoUtil.dll
> stage/tools/lib/CYGWIN/i686/cygPocoUtild.32.dll
> stage/tools/lib/CYGWIN/i686/cygPocoUtild.dll
> stage/tools/lib/CYGWIN/i686/cygPocoXML.32.dll
> stage/tools/lib/CYGWIN/i686/cygPocoXML.dll
> stage/tools/lib/CYGWIN/i686/cygPocoXMLd.32.dll
> stage/tools/lib/CYGWIN/i686/cygPocoXMLd.dll
>
>
> $rebase -T dlls
> usage: rebase [-b BaseAddress] [-o Offset] [-48dOsvV] [-T [FileList |
> -]] Files...
> rebase -i [-48Os] [-T [FileList | -]] Files...
> rebase --help or --usage for full help text
>
> $rebase stage/tools/lib/CYGWIN/i686/cygPocoXML.32.dll
> usage: rebase [-b BaseAddress] [-o Offset] [-48dOsvV] [-T [FileList |
> -]] Files...
> rebase -i [-48Os] [-T [FileList | -]] Files...
> rebase --help or --usage for full help text
>
> Any ideas of what's wrong?
$ rebase --help
[...]
-O, --oblivious Do not change any files already in the database
and do not record any changes to the database.
(Implies -s).
[...]
One of the options -b, -s or -i is mandatory.
[...]
If you use -O as Achim suggested in https://www.cygwin.com/ml/cygwin/2015-11/msg00141.html, that implies -s, so you should be OK.
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
next prev parent reply other threads:[~2015-11-08 16:05 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-11-07 6:39 Francis ANDRE
2015-11-07 7:12 ` Marco Atzeri
2015-11-07 8:13 ` David Stacey
2015-11-07 21:02 ` David Stacey
2015-11-07 21:18 ` Marco Atzeri
2015-11-07 22:42 ` Achim Gratz
2015-11-08 15:11 ` Francis ANDRE
2015-11-08 16:05 ` Ken Brown [this message]
2015-11-09 15:23 ` Francis ANDRE
2015-11-09 16:44 ` Francis ANDRE
2015-11-09 17:10 ` Ken Brown
2015-11-09 23:13 ` Building Poco for Cygwin (was: Re: Cannot fork process for: g++: cygPocoFoundation.32.dll: Loaded to different address) David Stacey
2015-11-09 16:46 ` Cannot fork process for: g++: cygPocoFoundation.32.dll: Loaded to different address Ken Brown
2015-11-07 9:04 ` Francis ANDRE
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=563F72D7.5070908@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).