On Tuesday 06 Jul 2010, Edward Ned Harvey wrote:
> I have tried everything I can think of, and I can't seem to get svn to
> build with the zlib that comes with it.  It's always linking against
> /usr/lib64/zlib.
>
>
>
> ./configure --prefix=/scratch/eharvey/svn
> --with-zlib=/scratch/eharvey/subversion-1.6.12/zlib --enable-static
>
>

Have you tried setting LD_FLAGS before running configure? I'd keep 
the --with-zlib option as well. For example

LD_FLAGS=-L`pwd`/zlib
export LD_FLAGS
./configure ...

>
> After build:
>
> ldd `which svn` | grep libz
>
>         libz.so.1 => /usr/lib64/libz.so.1 (0x00000034a6900000)
>
>
>
> Perhaps I should set something like INCLUDE_PATH or LD_LIBRARY_PATH before
> building it?  Also, if I enable-static, shouldn't it be internal, shouldn't
> ldd show me nothing?
>

I have a vague memory that enable-static is to do with building static 
libraries rathern than a static binary. ldd on a static binary should show 
the message 'not a dynamic executable' or something like that. I've used a 
slightly different configure line to do that. On my machine I had trouble 
with the built os provided openssl so had to build my own.

./configure --prefix=/someplace --with-neon=`pwd/neon --with-ssl 
--disable-shared --enable-all-static --with-openssl=`pwd`/openssl

oh, and on a 64bit machine (or it might be unique to opensuse) I've found I 
had to add -fPIC to the CFLAGS options before running configure.

CFLAGS=-fPIC
export CFLAGS

>
>
> Here's the reason why I care:
>
>
>
> The default zlib compression is 5.  I edited deflate.c to change this to 1.
> I would like to know how much difference there is.
>
>
>
> Thanks...


Campbell
-- 

__________________________________________________________________________________
Sword Ciboodle is the trading name of ciboodle Limited (a company 
registered in Scotland with registered number SC143434 and whose 
registered office is at India of Inchinnan, Renfrewshire, UK, 
PA4 9LH) which is part of the Sword Group of companies.

This email (and any attachments) is intended for the named
recipient(s) and is private and confidential. If it is not for you, 
please inform us and then delete it. If you are not the intended 
recipient(s), the use, disclosure, copying or distribution of any 
information contained within this email is prohibited. Messages to 
and from us may be monitored. If the content is not about the 
business of the Sword Group then the message is neither from nor 
sanctioned by us.

Internet communications are not secure. You should scan this
message and any attachments for viruses. Under no circumstances
do we accept liability for any loss or damage which may result from
your receipt of this email or any attachment.
__________________________________________________________________________________

Reply via email to