From: Ken Brown <kbrown@cornell.edu>
To: cygwin@cygwin.com, Rainer.Woitok@gmail.com
Subject: Re: How to correctly rebase?
Date: Sun, 18 Oct 2015 12:45:00 -0000 [thread overview]
Message-ID: <5623944A.3090809@cornell.edu> (raw)
In-Reply-To: <22051.32540.675000.621396@woitok.gmail.com>
On 10/18/2015 7:14 AM, Dr Rainer Woitok wrote:
> Ken and Others,
>
> On Friday, 2015-10-16 11:07:58 -0400, Ken Brown wrote:
>
>> On 10/16/2015 8:58 AM, Ken Brown wrote:
>> ...
>>> As Warren and Achim have both suggested, you may just have too many DLLs for
>>> 32-bit Cygwin.
>
> Just to make sure: Are we talking about Windows and Windows application
> DLLs PLUS Cygwin and Cygwin application DLLs? Or are we just talking
> about Cygwin and Cygwin application DLLs?
Just Cygwin and Cygwin application DLLs.
>>> Can you uninstall some unneeded packages?
>
> I'm sure I can. In the course of using Cygwin I've installed plenty of
> packages and have also uninstalled some again. And each package in-
> stalled has also installed all the packages it depends on, while each
> package deinstalled has naturally left all its dependees on my system.
>
> Question: is there some command line tool which lists all dependencies
> for a given package? I could then write a small shell script to find
> out the list of packages which are not required by any other package.
> And if I then find packages in this list which I don't require, too,
> I've found some candidates ...
Install the cygcheck-dep package and use the script /usr/bin/cygcheck-dep.
>>> Or switch to 64-bit
>>> Cygwin?
>
> Well, it's a bit strange: the hardware in fact IS 64 bit, but the Vista
> running on it is 32 bit, because this laptop is a convertible and some
> of the tablet specific drivers, for instance for the stylus, were (at
> least five years ago) only available as 32 bit versions. So the quest-
> ion is: what does 64 bit Cygwin require? Only any Windows on a 64 bit
> hardware or a 64 bit Windows on a 64 bit hardware? I suspect it's the
> latter ...
Yes, I think so.
>>> By the way, I don't think you have yet attached cygcheck output as requested in
>>> http://cygwin.com/problems.html:
>
> You are right. That was mainly because my initial problem wasn't of the
> kind "What's wrong with my Cygwin installation?" but rather of the kind
> "What's wrong with my way to rebase my Cygwin DLLs?". I've appended the
> output below, and I really hope you're right, and somebody will spot
> something there ...
In the future, please follow the instructions, which say to send the cygcheck
output as an *attachment*. This is to avoid bogus hits when people search the
archives.
The only things that jump out at me are the ZoneAlarm warning (which you already
know about) and the fact that you do indeed have a large number of packages
installed.
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-10-18 12:45 UTC|newest]
Thread overview: 27+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-10-14 14:26 Dr Rainer Woitok
2015-10-14 17:27 ` Warren Young
2015-10-14 19:27 ` Achim Gratz
2015-10-14 21:30 ` Warren Young
2015-10-14 22:08 ` Warren Young
2015-10-14 22:37 ` Warren Young
2015-10-15 7:53 ` Achim Gratz
2015-10-15 7:15 ` Achim Gratz
2015-10-15 13:16 ` Dr Rainer Woitok
2015-10-15 20:54 ` Warren Young
2015-10-15 21:10 ` Ken Brown
2015-10-16 12:57 ` Dr Rainer Woitok
2015-10-16 12:58 ` Ken Brown
2015-10-16 15:08 ` Ken Brown
2015-10-16 15:16 ` cyg Simple
2015-10-16 15:29 ` Ken Brown
2015-10-16 15:50 ` Andrey Repin
2015-10-18 11:15 ` Dr Rainer Woitok
2015-10-18 11:59 ` Achim Gratz
2015-10-18 12:45 ` Ken Brown [this message]
2015-10-18 16:20 ` Dr Rainer Woitok
2015-10-19 23:59 ` Warren Young
2015-10-20 16:55 ` Dr Rainer Woitok
2015-10-16 7:21 ` Achim Gratz
2015-10-16 20:11 ` Warren Young
2015-12-18 16:28 ` Achim Gratz
2015-10-14 19:58 ` 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=5623944A.3090809@cornell.edu \
--to=kbrown@cornell.edu \
--cc=Rainer.Woitok@gmail.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).