From: Corinna Vinschen <corinna-cygwin@cygwin.com>
To: cygwin@cygwin.com
Subject: Re: Cygwin DLL V2.3.0 on XP 64-bit professional not working at all
Date: Fri, 13 Nov 2015 09:11:00 -0000 [thread overview]
Message-ID: <20151113091058.GJ17435@calimero.vinschen.de> (raw)
In-Reply-To: <56456791.3090600@georg-rehfeld.de>
[-- Attachment #1: Type: text/plain, Size: 2371 bytes --]
On Nov 13 05:31, Georg Rehfeld wrote:
> Am 12.11.2015 um 13:33, Corinna Vinschen wrote:
> >On Nov 12 11:53, Corinna Vinschen wrote:
> >>On Nov 12 02:27, Georg Rehfeld wrote:
> >>>Package: 0/Perpetual
> >>> 0p_000_autorebase.dash exit code -1073741819
> >>>Package: _/base-cygwin
> >>
> >>Thanks for the report. I could reproduce the problem on 64 bit XP and
> >>64 bit Server 2003 and applied a patch. I will upload a fixed 2.3.1
> >>probably this weekend.
> >
> >I just uploaded a developer snapshot to https://cygwin.com/snapshots/
> >Maybe you'd like to give it a try. Installing only the cygwin1.dll from
> >http://cygwin.com/snapshots/x86/cygwin1-20151112.dll.xz is sufficent
> >(but keep a backup of your current cygwin1.dll, just in case).
> >
> >Thanks,
> >Corinna
>
> Thanks Corinna for the immediate fix. Essentially it seems to work.
>
> *** What I did (possibly I've done something wrong) and the outcome:
>
> 1. downloaded/extracted the new cygwin1.dll and noted, that it is only
> 2.6MB; saved the old one (3.3MB) and copied the new one over the old
> one in my restored Cygwin. Did a short test: everything fine.
>
> 2. started the Setup 32bit, updated 40 packages or so. Obviously the
> cygwin1.dll was in the update (was again 3.3MB) ... so same/similar
> post install errors as before.
Ideally you would have set the cygwin package to "keep" before starting
the installation :)
> 3. copied the snapshot DLL again and redid the setup. This time 0
> packages to update, but the post install ran smoothly (needed
> considerable time) except for this message:
> -----
> Package: _/Unknown package
> xinit.sh exit code 3
> -----
>
> I consider this harmless, because my X install was not OK from the
> beginning and I don't need it really (have to uninstall soon).
>
> I can start bash as usual (from within TotalCommander). All other
> commands/scripts I tested seem to work smoothly.
>
> So IMHO the patch was successful.
>
> Many thanks again, Georg
You're welcome. If I get positive reply from Mario Roy in terms of
the flock problem, I create a 2.3.1 bugfix release ASAP.
Thanks,
Corinna
--
Corinna Vinschen Please, send mails regarding Cygwin to
Cygwin Maintainer cygwin AT cygwin DOT com
Red Hat
[-- Attachment #2: Type: application/pgp-signature, Size: 819 bytes --]
prev parent reply other threads:[~2015-11-13 9:11 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-11-12 1:27 Georg Rehfeld
2015-11-12 1:48 ` Helmut Karlowski
2015-11-12 4:04 ` Georg Rehfeld
2015-11-12 10:53 ` Corinna Vinschen
2015-11-12 12:33 ` Corinna Vinschen
2015-11-13 4:31 ` Georg Rehfeld
2015-11-13 9:11 ` Corinna Vinschen [this message]
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=20151113091058.GJ17435@calimero.vinschen.de \
--to=corinna-cygwin@cygwin.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).