Re: [EXT] Re: building subversion --with-zlib=.... seems to have no effect

[Daniel Shahaf <d....@daniel.shahaf.name>]

Hiran CHAUDHURI wrote on Thu, 31 Aug 2017 12:01 +0000:
> From: Daniel Shahaf [mailto:d.s@daniel.shahaf.name] 
> >Hiran CHAUDHURI wrote on Mon, 14 Aug 2017 14:25 +0000:
> >> I am building subversion from source but always see the output files 
> >> depend on the system-supplied zlib which is way older than the one I want to use.
> >
> >I gather you build 1.9.5.
> 
> Confirmed. That is the version I build, based on Apache httpd 2.4.27 and APR 1.6.2.

1.9.5 has a known security issue (https://subversion.apache.org/security/ -> CVE-2017-9800);
you should use 1.9.7 instead.

> It seems this helps to set the run path in the executables and
> libraries, but I am still trying to figure out whether Subversion was
> compiled using the correct libraries.

'svn --version --verbose' prints the build-time and run-time versions of zlib.

RE: [EXT] Re: building subversion --with-zlib=.... seems to have no effect

[Hiran CHAUDHURI <hi...@amadeus.com>]

From: Daniel Shahaf [mailto:d.s@daniel.shahaf.name] 
>> >I gather you build 1.9.5.
>> 
>> Confirmed. That is the version I build, based on Apache httpd 2.4.27 and APR 1.6.2.
>
>1.9.5 has a known security issue (https://subversion.apache.org/security/ -> CVE-2017-9800); you should use 1.9.7 instead.

Thank you for pointing out. I will make use of that new version.

>> It seems this helps to set the run path in the executables and 
>> libraries, but I am still trying to figure out whether Subversion was 
>> compiled using the correct libraries.
>
>'svn --version --verbose' prints the build-time and run-time versions of zlib.

With my currently compiled version I get this output. So this indicates that svn was compiled with the correct library, and my tweaks meanwhile to modify the run path were successful as well.

* linked dependencies:
  - APR 1.6.2 (compiled with 1.6.2)
  - APR-Util 1.6.0 (compiled with 1.6.0)
  - Expat 2.2.1 (compiled with 2.2.1)
  - SQLite 3.19.3 (compiled with 3.19.3)
  - Utf8proc 1.1.5 (compiled with 1.1.5)
  - ZLib 1.2.11 (compiled with 1.2.11)

While it might be more comfortable to have the run path being set automatically when specifying a specific zlib version it seems my problem is resolved.
:-)

Hiran