Author: wyoung
Date: Thu Aug 7 07:10:25 2008
New Revision: 2334
URL: http://svn.gna.org/viewcvs/mysqlpp?rev=2334&view=rev
Log:
Typo fix
Modified:
trunk/README-Linux.txt
Modified: trunk/README-Linux.txt
URL:
http://svn.gna.org/viewcvs/mysqlpp/trunk/README-Linux.txt?rev=2334&r1=2333&r2=2334&view=diff
==============================================================================
--- trunk/README-Linux.txt (original)
+++ trunk/README-Linux.txt Thu Aug 7 07:10:25 2008
@@ -2,15 +2,15 @@
is concerned. See README-Unix.txt for most of what you need to know
to build and use MySQL++.
-The biggest Linux-specific hurdle is dealing with the dynamic linker,
-ld.so. This program is called by the operating system when loading
-an executable to run. It locates any shared libraries the executable
-uses and links them up so the program will run. If ld.so it can't
-find libmysqlpp, a program using MySQL++ won't run. It always looks
-in /lib and /usr/lib for shared libraries, but by default, MySQL++
-installs in /usr/local/lib when you install from source. You can
-either change the installation directory, or you can clue ld.so in
-to the nonstandard location.
+The biggest Linux-specific hurdle is dealing with the dynamic
+linker, ld.so. This program is called by the operating system when
+loading an executable to run. It locates any shared libraries the
+executable uses and links them up so the program will run. If ld.so
+can't find libmysqlpp, a program using MySQL++ won't run. It always
+looks in /lib and /usr/lib for shared libraries, but by default,
+MySQL++ installs in /usr/local/lib when you install from source.
+You can either change the installation directory, or you can clue
+ld.so in to the nonstandard location.
The first thing ld.so looks at when trying to find a library is the
LD_LIBRARY_PATH environment variable. This works like the shell's
_______________________________________________
Mysqlpp-commits mailing list
[email protected]
https://mail.gna.org/listinfo/mysqlpp-commits
