delorie.com/archives/browse.cgi   search  
Mail Archives: cygwin/2003/12/10/11:48:01

Mailing-List: contact cygwin-help AT cygwin DOT com; run by ezmlm
List-Subscribe: <mailto:cygwin-subscribe AT cygwin DOT com>
List-Archive: <http://sources.redhat.com/ml/cygwin/>
List-Post: <mailto:cygwin AT cygwin DOT com>
List-Help: <mailto:cygwin-help AT cygwin DOT com>, <http://sources.redhat.com/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
X-Authentication-Warning: eos.vss.fsi.com: ford owned process doing -bs
Date: Wed, 10 Dec 2003 10:47:39 -0600 (CST)
From: Brian Ford <ford AT vss DOT fsi DOT com>
X-X-Sender: ford AT eos
To: Duncan Murdoch <dmurdoch AT pair DOT com>
cc: cygwin AT cygwin DOT com
Subject: Re: CYGICONV-2.DLL was not found during installation
In-Reply-To: <87cetvkqdcjnhcnf36ieg2nu8d9hi8ief2@4ax.com>
Message-ID: <Pine.GSO.4.58.0312101035320.28297@eos>
References: <5 DOT 2 DOT 1 DOT 1 DOT 2 DOT 20031209234116 DOT 00a45ec0 AT mailhost DOT zen DOT co DOT uk>
<Pine DOT GSO DOT 4 DOT 58 DOT 0312091744500 DOT 28297 AT eos> <87cetvkqdcjnhcnf36ieg2nu8d9hi8ief2 AT 4ax DOT com>
MIME-Version: 1.0

On Wed, 10 Dec 2003, Duncan Murdoch wrote:
> On Tue, 9 Dec 2003 17:47:50 -0600 (CST), Brian Ford <ford AT vss DOT fsi DOT com>
> wrote :
> >Additionally, this probably indicates a dependency bug in some packages
> >setup.hint file.  Although, I don't know a good way to track this down.
> >
> One way to track down such dependencies is to use pedump -i or objdump
> -x on each .exe and .dll in cygwin/bin, then look for the missing DLL
> in the listings.  It's a little complicated to do this, because pedump
> doesn't print the filename it's working on, and I'm not so comfortable
> with putting shell scripts together.
>
> pedump can be found using google.  objdump is in binutils.
>
Um..., thanks, I guess.  Although, this information is not what I
was unclear about.

cygcheck would be the prefered program to use if one were to
take this route.  It does print the filename it is working on.  But, this
seems to be a very round about method, and I did not want to take
the time to put together said shell script.

I think looking in some setup log file would probably be more fruitfull.
I do not know which one or how, and I do not want to take the time to
figure it out.  Thus, I thought another interested party might chime in.

> HOWEVER, this error does not necessarily indicate a bug in the
> setup.hint file.  I recently had the same sort of problem when
> installing rsync, and the setup information there looks fine.  I think
> it's a bug in the Cygwin setup.exe program:  it looks as though if it
> can't find a dependency, it doesn't necessarily abort, it continues
> without it.
>
Maybe, but I'll let a setup expert figure that out.

-- 
Brian Ford
Senior Realtime Software Engineer
VITAL - Visual Simulation Systems
FlightSafety International
Phone: 314-551-8460
Fax:   314-551-8444

--
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/

- Raw text -


  webmaster     delorie software   privacy  
  Copyright © 2019   by DJ Delorie     Updated Jul 2019