Randy <nya_ma...@yahoo.com> writes: > I see. Then my problem is not knowing how to tell the build to use the > zlib I built.
If zlib is a shared library there are various ways: you set RPATH in the ELF libraries that use zlib, probably using -rpath while linking; or you set the LD_LIBRARY_PATH environment variable; or you modify the system ld.so.conf and run ldconfig. However you don't appear to have a shared library. > When I build svn and point to the location of my zlib > prefix (see command in original post), svn still looks for > "/lib64/libz.so.1". Also I noticed that "libz.so.1" doesn't exist in > my zlib prefix location (/tmp-build/zlib) You appear to be using a static zlib. What about serf? It also uses zlib. Are you linking serf against the system zlib or your own zlib? Something is linking against a shared zlib. Trying to use two different zlib is probably a bad idea. It may work, or it may give you errors that are hard to track down. > The location is "tmp" because I am not trying to replace zlib on this > system, I'm  trying to package zlib with my build of subversion. If zlib is static you don't package it, it gets included when you link to the static library. > This > way subversion is deploy-able to different machines and less reliant > on local libraries. As you have discovered, it can be hard to do that. You have to ensure that you link everything to the right libraries and that involves understanding shared library dependencies. You may find it easier to build binaries for each OS using the system libraries as far as possible. -- Philip Martin | Subversion Committer WANdisco | Non-Stop Data