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
Message-ID:	<79218202D4B9D4118A290002A508E13B79C383@PNZEXCHANGE>
From:	Ross Smith <rosss AT pharos DOT co DOT nz>
To:	"'Dan Browning'" <dbml AT kavod DOT com>, cygwin AT cygwin DOT com
Subject:	RE: ./config -luser32 error, but libuser32.a is in the usr/lib/w3
	2api directory
Date:	Thu, 21 Mar 2002 14:26:09 +1200
MIME-Version:	1.0
X-Mailer:	Internet Mail Service (5.5.2653.19)

> From: Dan Browning [mailto:dbml AT kavod DOT com]
> 
> At 08:56 PM 3/20/2002 -0500, you wrote:
> >At 08:52 PM 3/20/2002, Dan Browning wrote:
> > >
> > >The "c:\cygwin\usr\lib\w32api" DOES actually exist in 
> windows, but I 
> > could not access that directory within the cygwin shell:
> > >
> > >$ cd /usr/lib/w32api
> > >bash: cd: /usr/lib/w32api: No such file or directory
> > >
> > >However, if I copy "c:\cygwin\usr\lib\w32api" to 
> c:\cygwin\lib, then 
> > everything works (like what Luke said).
> > >
> > >So what I think we're dealing with here is, "why can't 
> cygwin see the 
> > c:\cygwin\usr\lib\w32api directory"?
> >
> >
> >Sounds like a permissions problem to me.  What does ls -l 
> /usr/lib/w32api
> >show?
> 
> <I'll try to remember to do reply all instead of reply next time>
> 
> $ ls -l /usr/lib/w32api
> ls: /usr/lib/w32api: No such file or directory
> 
> Perhaps it has something to do with the /usr/lib -> /lib 
> mounting?  http://cygwin.com/faq/faq.html#SEC61

It looks as though the w32api directory has been put under the real
/usr/lib (== c:\cygwin\usr\lib) instead of under the mounted
directory (/usr/lib == c:\cygwin\lib) (which is where it is on my
system). When the mount point is set up, this renders invisible
anything actually existing under the mount-point directory.

Whether this would have been caused by a setup bug or pilot error
I couldn't guess.

--
Unsubscribe info:      http://cygwin.com/ml/#unsubscribe-simple
Bug reporting:         http://cygwin.com/bugs.html
Documentation:         http://cygwin.com/docs.html
FAQ:                   http://cygwin.com/faq/

- Raw text -