public inbox for cygwin@cygwin.com
 help / color / mirror / Atom feed
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: Mon, 09 Nov 2015 17:10:00 -0000	[thread overview]
Message-ID: <5640D389.5020609@cornell.edu> (raw)
In-Reply-To: <5640CD6F.4030003@orange.fr>

On 11/9/2015 11:44 AM, Francis ANDRE wrote:
>      rebase -O -T list
>> That's works effectively but why it does not work without the -O option?
> Hold on, the story is not closed
>
> when doing the following steps at the console, it works
> find . -name "*.dll" > dlls
> rebase -O -T dlls
> PATH=/cygdrive/z/git/poco-1.6.2/stage/tools/PocoDoc/bin/CYGWIN/i686:/cygdrive/z/git/poco-1.6.2/stage/tools/lib/CYGWIN/i686:/cygdrive/z/git/poco-1.6.2/stage/tools/PocoDoc/bin/CYGWIN/i686:/cygdrive/z/git/poco-1.6.2/stage/tools/lib/CYGWIN/i686:/cygdrive/z/git/poco-1.6.2/release/script:/usr/local/bin:/usr/bin:/cygdrive/c/ProgramData/Oracle/Java/javapath:/cygdrive/c/Python33:/cygdrive/c/Windows/system32:/cygdrive/c/Windows:/cygdrive/c/Windows/System32/Wbem:/cygdrive/c/Windows/System32/WindowsPowerShell/v1.0:/cygdrive/c/Program
> Files/Microsoft SQL Server/110/Tools/Binn:/cygdrive/c/Program Files
> (x86)/Subversion/bin:/cygdrive/c/Program Files (x86)/Dr.
> Memory/bin:/cygdrive/c/Program Files
> (x86)/Skype/Phone:/cygdrive/c/Windows/system32/config/systemprofile/.dnx/bin:/cygdrive/c/Program
> Files/Microsoft DNX/Dnvm:/cygdrive/c/Program Files (x86)/Windows
> Kits/10/Windows Performance Toolkit:/cygdrive/c/Program Files
> (x86)/Git/bin:/cygdrive/z/git/win-flex-bison/bin/Release:/cygdrive/c/ASF/apache-maven-3.2.1/bin:/cygdrive/c/Program
> Files/Java/jdk1.7.0_51/bin:/cygdrive/c/ASF/apache-ant-1.9.3/bin
> PocoDoc --config=/cygdrive/z/git/poco-1.6.2/PocoDoc/cfg/mkdoc-poco.xml
> --config=/cygdrive/z/git/poco-1.6.2/stage/docbuild/PocoDoc.ini
>
>
> but when running the equivalent steps in a bash script, it does not work
> as show below

You didn't do the equivalent steps in your script.  You rebased the DLLs 
one at a time instead of all at once.  With the -O option, rebase 
doesn't record the changes to the rebase database, so there's nothing to 
prevent the new DLLs from colliding with one another.

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:[~2015-11-09 17:10 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
2015-11-09 15:23             ` Francis ANDRE
2015-11-09 16:44               ` Francis ANDRE
2015-11-09 17:10                 ` Ken Brown [this message]
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=5640D389.5020609@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).