Thomas Dickey <[EMAIL PROTECTED]> writes: > agree - I was not thinking of the search list (though I'm aware of it). > > The description I read did not mention it, either...
Mac OS's approach to dynamic libraries is ... somewhat unusual. AFAICT, the way things work there is that each library hard-codes a (single) canonical installation location, which the static linker then embeds in any executables (or other dynamic libraries) that link to it. The runtime linker then proceeds to search for each required library in, in order, DYLD_LIBRARY_PATH, the hardcoded per-library path, and DYLD_FALLBACK_LIBRARY_PATH. (It's actually slightly more complicated than that because there's also the concept of frameworks, but I don't believe it concerns ncurses.) -- Aaron M. Ucko, KB1CJC (amu at alum.mit.edu, ucko at debian.org) Finger [EMAIL PROTECTED] (NOT a valid e-mail address) for more info. -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]