LIBRARY_PATH problems

[Kris Thielemans]

Hi,

it seems I forgot to mention one other thing (sorry about this, I hate
incomplete postings myself).

This is NOT a problem to do with inodes etc. Proof:

gcc -L//d/ll -lX11

(and other variations like using NT style 'd:\ll') works without any
problem. In fact, I would be terribly surprised if it is a general cygwin
problem. My whole cygwin stuff is on d:, and so lots of its environment
variables point to d:. Everything works cleanly. This all points to a gcc
problem specific to LIBRARY_PATH to me (ok, I didn't try other gcc variables
except GCC_EXEC_PREFIX and C_INCLUDE_PATH, but these 2 work).

Kris

> -----Original Message-----
> From: Kevin F. Quinn [ mailto:kevq-ml@banana.demon.co.uk ]
> Sent: 19 May 1998 11:46
> To: Kris Thielemans
> Cc: Gnuwin
> Subject: RE: LIBRARY_PATH problems
>
>
> Kris Thielemans wrote:
>
> > New tests:
> > 3)
> > - I make a directory /ll, and put libX11.a in there
> > - I make sure there is no ll directory on any other drive,
> certainly not on
> > d: - I set LIBRARY_PATH=//d/ll (or /home/ll) - gcc -v -lX11
> does find the
> > X11 library, and the -v option tells you it found it in /ll (=c:\ll)
> >
> > 4)
> > - I remove the c:\ll, and make a d:\ll, put libX11.a
> > - keep LIBRARY_PATH=//d/ll
> > - gcc -lX11 does not find the library
>
> Would mounting D:\ onto /d (say) solve the problem?  Then you
> wouldn't have
> to use any drive specifications, which are presumably (I'm guessing,
> from what Earnie said earlier) causing inode conflicts and hence
> all sorts
> of weird side-effects.
>
> Kev.
>
> --
> Kevin F. Quinn
> Email: mailto:kevq@banana.demon.co.uk
> Web: http://www.banana.demon.co.uk/
>
> DH/DSS PGP Key ID BF2270F3, F'print CF8E7A81E372B57AA793
> 2AC7E016EB00BF2270F3
> RSA PGP Key ID 22DEFDE5, F'print 92DB91B153F10711 4272B2940D7C7D77
>

-
For help on using this list (especially unsubscribing), send a message to
"gnu-win32-request@cygnus.com" with one line of text: "help".