public inbox for cygwin@cygwin.com
 help / color / mirror / Atom feed
From: Tatsuro MATSUOKA <tmacchant2@yahoo.co.jp>
To: cygwin@cygwin.com
Subject: Re: make command fails on cygwin-x86  (cyggmp-10.dll: Loaded to different address)
Date: Wed, 16 Mar 2016 13:50:00 -0000	[thread overview]
Message-ID: <56214.11925.qm@web101111.mail.kks.yahoo.co.jp> (raw)
In-Reply-To: <838158214.20160316145133@yandex.ru>

----- Original Message -----

> From: Andrey Repin 
> To: Tatsuro MATSUOKA ; cygwin
> Cc: 
> Date: 2016/3/16, Wed 20:51
> Subject: Re: make command fails on cygwin-x86  (cyggmp-10.dll: Loaded to different address)
> 
>G reetings, Tatsuro MATSUOKA!
> 
>>>  rebase-trigger full
>>>  setup to the last 
> 
>>>  rebase-trigger full ?
> 
>>  I started up ash from Windows command prompt and tried to start 
> 
>>  $ rebase-trigger full 
>>  but
>>  ash: 1: rebase-trigger: not found
> 
> Then your installation is sorely out of date.
> 
> $ which rebase-trigger
> /usr/bin/rebase-trigger
> 
> $ rebase-trigger --help
> 
> rebase-trigger [-h | --help | [ full[rebase] | peflags ]]
> 
> Commands:
> ------------------------------------
> 
> full
> fullrebase
>         Perform a full rebase the next time autorebase is run.
> 
> peflags
>         Set some flags on executables necessary to run on a Terminal
>         Server.  This is only needed for 32bit executables that have
>         been created with old toolchains.
> 
I have forgotten ./ before  rebase-trigger in ash. 
"./" is needed if it executed from windows cmd


> 
>>>  setup to the last ?
> 
>>  What should I do for "setup to the last?
> 
> As Achim said, just close all running Cygwin processes, then run setup and let
> it do its magic.
The last step of setup seem to be autorebase then setup command is the easiest way
to use "rebase". Am I right?

After rebase sometime one needs to restart PC. Right?

> Also, if you have 64-bit OS and don't have specific needs for x86 Cygwin, 
> I'd
> recommend scraping your current Cygwin suite and install 64-bit one.
> It gets A LOT easier on memory layout.

I know.

I have both Cygwin32 and Cygwin64 for the purpose to distribute the cvs version 
of gnuplot for windows. 

http://www.tatsuromatsuoka.com/gnuplot/Eng/cygbin/



For usual use, I of course uses Cygwin64 on 64 bit windows.

Thank you for your detailed explanations.

Tatsuro

--
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:[~2016-03-16 13:50 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-03-16  0:22 Tatsuro MATSUOKA
2016-03-16  0:50 ` Andrey Repin
2016-03-16  1:46   ` Tatsuro MATSUOKA
2016-03-16  2:38     ` Tatsuro MATSUOKA
2016-03-16  9:42     ` Achim Gratz
2016-03-16 12:05     ` Andrey Repin
2016-03-16 13:50       ` Tatsuro MATSUOKA [this message]
2016-03-16 14:00         ` Achim Gratz
2016-03-16 19:54           ` Tatsuro MATSUOKA
2016-03-16 20:13             ` Achim Gratz
2016-03-16 23:38               ` Tatsuro MATSUOKA
2016-03-17 13:05               ` Andrey Repin
2016-03-18  0:15                 ` Tatsuro MATSUOKA

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=56214.11925.qm@web101111.mail.kks.yahoo.co.jp \
    --to=tmacchant2@yahoo.co.jp \
    --cc=cygwin@cygwin.com \
    --cc=matsuoka@nuce.nagoya-u.ac.jp \
    /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).