X-Spam-Check-By: sourceware.org
From: root <fedyarov AT mail DOT ru>
Reply-To: fedyarov AT mail DOT ru
To: cygwin AT cygwin DOT com
Subject: Re: Possible Cygwin1.dll problem
Date: Wed, 8 Nov 2006 22:54:29 +0300
User-Agent: KMail/1.8
References: <454F437C DOT 2040708 AT mail DOT ru> <200611081110 DOT 41848 DOT fedyarov AT mail DOT ru> <Pine DOT GSO DOT 4 DOT 63 DOT 0611080917040 DOT 23129 AT access1 DOT cims DOT nyu DOT edu>
In-Reply-To: <Pine.GSO.4.63.0611080917040.23129@access1.cims.nyu.edu>
MIME-Version: 1.0
Content-Type: text/plain;   charset="utf-8"
Content-Transfer-Encoding: 7bit
Content-Disposition: inline
Message-Id: <200611082254.29637.fedyarov@mail.ru>
Mailing-List: contact cygwin-help AT cygwin DOT com; run by ezmlm
List-Subscribe: <mailto:cygwin-subscribe AT cygwin DOT com>
List-Archive: <http://sourceware.org/ml/cygwin/>
List-Post: <mailto:cygwin AT cygwin DOT com>
List-Help: <mailto:cygwin-help AT cygwin DOT com>, <http://sourceware.org/ml/#faqs>
Sender: cygwin-owner AT cygwin DOT com
Mail-Followup-To: cygwin AT cygwin DOT com
Delivered-To: mailing list cygwin AT cygwin DOT com

Hi dear Igor,
Thank you for your patience!

Everithink works fine now that I've followed you advice - after using 
setup.exe. I thought it will start downloading and installing again, but 
actually it just told me "there's nothing to install" and created necessary 
mount points and setups. I'm only curious where those mount points are 
defined? Is there some /etc/fstab-like file or are they in registry keys?

I just moved files from c:\bin and c:\usr\bin to c:\cygwin\bin and from c:
\usr\lib to c:\cygwin\lib, then corrected Path environment var. It's all 
right now!

The only thing remaining semi-working thing is using files containing 
parentheses in their names as '%f' or '%p' in Midnight Commander bindings. 
Windows programs consider e.g. 'asteroids\(1\).doc' (real name 
'asteroids(1).doc') as incorrect name since backslash is reserved for path 
delimitation. That's not a big problem as for me, but it may be annoying for 
some people who may often use filenames with parentheses.

One final question. Am I right that Cygwin port of ncurses can't report mouse 
events and pdcurses has still no mouse support at all? Maybe I'll take a look 
at the source to add it some day.

Thank you for tactfulness,

Bye,
Ruslan

> > Hi dear Igor Peshansky,
> >
> > I have one simple question. When anyone of you runs 'bash' or any Cygwin
> > shell and changes to a CD or floppy (with 'cd /cygdrive/e' or whatever)
> > does command 'ls /tmp' give you any error refusing to work?
>
> No, it does not.  All of my Cygwin applications work just fine.
>
> > Please don't advise to reinstall it all not even bothering to take a
> > look. Just check it, it's not very hard.
>
> I did not advise you to reinstall it all.  I advised you to let setup.exe
> do its job.  There is more to Cygwin installation than simply untarring
> the package tarballs.
>
> > If it's so, you probably have some bugs in your main cygwin1.dll,
> > concerning automounting of '/'. If not, I'm sorry, that's my strange way
> > of installation.
>
> Indeed.  It is your strange (and broken, I might add) way of installation.
> It *is* possible to install Cygwin by hand, BUT you need to perform all of
> the requisite actions in the right order.  Perusing the sources of
> setup.exe might be educational.  Many people (including me) are working on
> decoupling setup's logic from the UI so that a command-line installer (or
> even an installation library that can be compiled on Linux) could be
> produced, but the work is hard and slow.  Contributions in this area are
> most welcome.
>
> > I cannot agree with you, Igor, about having to install via setup.exe.
> > Your POSIX/ANSI LIBC library should work not only with Cygwin packages
> > but also with other third party programs regardless of whether they use
> > any installer or distributed as an archive.
>
> The Cygwin packages *will* work with 3-rd party apps that use it properly,
> no matter how *those apps* are distributed.  However, Cygwin requires
> certain steps to get it to work properly -- just untarring is not enough.
> There also are some <http://cygwin.com/acronyms/#3PP>s (the examples of
> which you kindly provide below) that distribute their own Cygwin
> components improperly, and thus break existing Cygwin installations.
>
> > E.g. I've tried Infra Recorder (http://infrarecorder.sourceforge.net/)
> > and CDRTools Front-End (cdrtfe, http://home.arcor.de/kerberos002/). They
> > are both under GPL, use cygwin1.dll and have their own installer. Do
> > they need your setup.exe? It's funny.
>
> The tools themselves don't need to use setup.exe.  However, the Cygwin
> components they distribute end up in the wrong places, and break either
> existing or subsequent Cygwin installations.  An example was mentioned no
> further than today: <http://cygwin.com/ml/cygwin/2006-11/msg00180.html>.
>
> > I'm also surprised that you still haven't cdrtools and dvdrwtools
> > packages in your Cygwin release lists. One can find cdrtools compiled
> > with Cygwin at http://www.geoshock.com/cdrtools/ and dvdrwtools compiled
> > with MinGW (which is apparently compatible) at
> > http://fy.chalmers.se/%7Eappro/linux/DVD+RW/tools/win32/. Are you guys
> > CD/DVD phobic? These are important packages.
>
> Perhaps they are.  But the way to get packages into the Cygwin
> distribution is clearly outlined in <http://cygwin.com/setup.html>.
> Anyone can become a maintainer for the package (having pre-compiled
> binaries will make her job somewhat easier, but there will likely be some
> effort involved in bringing the packaging to conform with the accepted
> guidelines).
>
> I believe CDRtools was proposed and rejected -- search the cygwin-apps
> archives for details.
>
> > From my experience having multiple instances of Cygwin1.dll is a problem
> > only when they have different versions.
>
> Perhaps.  However, redundancy leads to inconsistency, and having two
> Cygwin1.dll's on your machine will eventually cause the versions to
> diverge.
>
> > When they do I have a message telling me to delete old ones.
>
> Not always.  See the thread I referred to above.
>
> > I don't have such a message on my system and everything works (or
> > doesn't) the same, still I have multiple instances of Cygwin1.dll of the
> > same version. Cygwin packages are not the only ones who use this
> > library, I don't want to copy it to every third party program folder.
>
> You don't have to -- just put Cygwin's /bin in your PATH.  However, you do
> need the mounts for Cygwin to even know where /bin is.
>
> > It would be nice to add mpg123 (used by Midnight Commander) to your
> > packages list, there're no patent limitations about decoding mp3: Debian
> > Linux has both mpg123 and mpg321 in their most open distributions.
>
> Again, see <http://cygwin.com/setup.html>.
>
> > By the way, it would be great to make a note in your setup.hint files
> > telling where some libraries reside when it's not apparent. I've spent
> > some time trying to find libintl* libraries. How could I know they're in
> > gettext folder?
>
> "cygcheck -p libintl".  FWIW, if you used setup.exe (or even setup.ini),
> this would not even come up as a problem.


--
Unsubscribe info:      http://cygwin.com/ml/#unsubscribe-simple
Problem reports:       http://cygwin.com/problems.html
Documentation:         http://cygwin.com/docs.html
FAQ:                   http://cygwin.com/faq/