public inbox for cygwin@cygwin.com
 help / color / mirror / Atom feed
From: Katsumi Yamaoka <yamaoka@jpl.org>
To: cygwin@cygwin.com
Subject: Cygwin 2.6.1 32-bit post install failed by /usr/bin/perl.exe
Date: Mon, 16 Jan 2017 07:29:00 -0000	[thread overview]
Message-ID: <b4mshojsbt1.fsf@jpl.org> (raw)

Hi,

I recently tried newly install Cygwin 2.6.1 on 32-bit Windows 10.

I did:
Stop old cygwin
cd c:\
ren cygwin cygwin.old
Run setup-x86.exe for full install excluding *x86_64* modulues.

However, the post install didn't seem to end.  At that time, ps
on mintty showed a lot of defunct perl processes.  Then I tried
replacing /usr/bin/perl.exe with the one I built from the source
one and a half years ago.

cd /usr/bin
mv perl.exe perl.exe.orig
ln -s /cygdrive/c/cygwin.old/usr/local/bin/perl.exe .

It did the trick!  Now new cygwin is running with no problem!
I don't know what yielded the result.  The file sizes of them
very differ because 5.22.3 was srtipped but 5.22.0 wasn't:

/usr/bin
-rwxr-xr-x 1 yamaoka None 12829 Jan 15 12:54 perl.exe.orig*
-rwxr-xr-x 1 yamaoka None 12829 Jan 15 12:54 perl5.22.3.exe

/cygdrive/c/cygwin.old/usr/local/bin
-rwxr-xr-x 2 yamaoka None 71801 Oct 21  2015 perl.exe*
-rwxr-xr-x 2 yamaoka None 71801 Oct 21  2015 perl5.22.0.exe*

But I cannot believe strip broke it.  cygcheck for them didn't
show meaningful difference.  It's a mystery.

Regards,


--
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:[~2017-01-16  7:29 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-01-16  7:29 Katsumi Yamaoka [this message]
2017-01-16 17:58 ` Achim Gratz
2017-01-18  1:02   ` Katsumi Yamaoka
2017-01-18 18:21     ` 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=b4mshojsbt1.fsf@jpl.org \
    --to=yamaoka@jpl.org \
    --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).