From dc90c358c270bc391102b5e051b71f0d96655af2 Mon Sep 17 00:00:00 2001 From: simonmar Date: Thu, 31 May 2001 09:18:34 +0000 Subject: [PATCH] [project @ 2001-05-31 09:18:34 by simonmar] Clarify where we look for libraries named on the command line (-lfoo), and mention LD_LIBRARY_PATH. The implementation is still wrong, however. --- ghc/docs/users_guide/ghci.sgml | 25 ++++++++++++++++++++----- 1 file changed, 20 insertions(+), 5 deletions(-) diff --git a/ghc/docs/users_guide/ghci.sgml b/ghc/docs/users_guide/ghci.sgml index e645723..0747b80 100644 --- a/ghc/docs/users_guide/ghci.sgml +++ b/ghc/docs/users_guide/ghci.sgml @@ -597,16 +597,31 @@ $ ghci -lm On systems with .so-style shared libraries, the actual library loaded will the - liblib.so. If - no such library exists on the standard library search path, - including paths given using - -Lpath, then - ghci will signal an error. + liblib.so. GHCi + searches the following places for libraries, in this order: + + + + Paths specified using the + -Lpath + command-line option, + + + the standard library search path for your system, + which on some systems may be overriden by setting the + LD_LIBRARY_PATH environment variable. + + On systems with .dll-style shared libraries, the actual library loaded will be lib.dll. Again, GHCi will signal an error if it can't find the library. + + GHCi can also load plain object files + (.o or .obj depending on + your platform) from the command-line. Just add the name the + object file to the command line. -- 1.7.10.4