> > Do you mean LD_LIBRARY_PATH or DYLD_LIBARARY_PATH, or even
> > DYLD_FALLBACK_LIBARAY_PATH, all of which on the Mac do something
> > slightly different...
>
> Oh dear, I meant just LIBRARY_PATH, of which the gcc manpage says
>
> LIBRARY_PATH
> The value of LIBRARY_PATH is a colon-separated list of directories,
> much like PATH. When configured as a native compiler, GCC tries
> the directories thus specified when searching for special linker
> files, if it can't find them using GCC_EXEC_PREFIX. Linking using
> GCC also uses these directories when searching for ordinary
> libraries for the -l option (but directories specified with -L come
> first).
>
> ...which sounds about right, but uncomfortably vague.
Yes, perhaps it a whole different library path variable that only GCC uses
or knows about. I wouldn't put it past them...
> Where are you getting all those environment variables from? It sounds
> like a document I should read....
MacOSX for UNIX Geeks by O'Reilly.
I'm sure there is a technote on it, but I'm afraid I find the Apple
technotes somewhat impenatrable so have fallen back onto crass
commercialism and bought the O'Reilly book.
|