[svn.haxx.se] · SVN Dev · SVN Users · SVN Org · TSVN Dev · TSVN Users · Subclipse Dev · Subclipse Users · this month's index

RE: Subversion Build Issues - 1.10.6

From: Sanad Majid <sanad.majid_at_LumaCyte.com>
Date: Thu, 25 Jun 2020 14:53:03 +0000

Hi Daniel,

Thank you for your response. Could you please give some more details as I am just a beginner in this.

1. I have installed libssl-dev, but how to add libssl-dev to libserf-dev's Depends?

root_at_LCNAS:~# apt-get install libssl-dev

Reading package lists... Done

Building dependency tree

Reading state information... Done

Recommended packages:


The following NEW packages will be installed:


0 upgraded, 1 newly installed, 0 to remove and 64 not upgraded.

Need to get 1,110 kB of archives.

After this operation, 5,104 kB of additional disk space will be used.

Get:1 http://security.debian.org jessie/updates/main armel libssl-dev armel 1.0.1t-1+deb8u12 [1,110 kB]

Fetched 1,110 kB in 0s (1,255 kB/s)

debconf: delaying package configuration, since apt-utils is not installed

Selecting previously unselected package libssl-dev:armel.

(Reading database ... 25150 files and directories currently installed.)

Preparing to unpack .../libssl-dev_1.0.1t-1+deb8u12_armel.deb ...

Unpacking libssl-dev:armel (1.0.1t-1+deb8u12) ...

Setting up libssl-dev:armel (1.0.1t-1+deb8u12) ...


2. Which package do I need to install to fix apxs issues? I have the latest version of apache2.

root_at_LCNAS:~# apt-get install apache2

Reading package lists... Done

Building dependency tree

Reading state information... Done

apache2 is already the newest version (2.4.25-3+deb9u6.netgear2).

0 upgraded, 0 newly installed, 0 to remove and 64 not upgraded.


root_at_LCNAS:~# apt-file search bin/apxs

apache2-dev: /usr/bin/apxs

apache2-dev: /usr/bin/apxs2


root_at_LCNAS:~/subversion-1.10.6# ./configure --with-lz4=internal --with-utf8proc=internal --with-apxs=/usr/bin/apxs

configure: Configuring Subversion 1.10.6

configure: creating config.nice

checking for gcc... gcc

checking whether the C compiler works... yes

checking for C compiler default output file name... a.out

checking for suffix of executables...

checking whether we are cross compiling... no

checking for suffix of object files... o

checking whether we are using the GNU C compiler... yes

checking whether gcc accepts -g... yes

checking for gcc option to accept ISO C89... none needed

checking if gcc accepts -std=c90... yes

checking if gcc accepts -w... yes

checking if gcc accepts -Werror=unknown-warning-option... no

checking for g++... g++

checking whether we are using the GNU C++ compiler... yes

checking whether g++ accepts -g... yes

checking if g++ accepts -std=c++98... yes

checking if g++ accepts -w... yes

checking if g++ accepts -Werror=unknown-warning-option... no

checking how to run the C preprocessor... gcc -E

checking for a sed that does not truncate output... /bin/sed

checking build system type... armv7l-unknown-linux-gnueabi

checking host system type... armv7l-unknown-linux-gnueabi

checking target system type... armv7l-unknown-linux-gnueabi

checking for grep that handles long lines and -e... /bin/grep

checking for egrep... /bin/grep -E

checking whether ln -s works... yes

checking for a BSD-compatible install... /usr/bin/install -c

configure: Apache Portable Runtime (APR) library configuration

checking for APR... yes

checking APR version... 1.5.1

configure: Apache Portable Runtime Utility (APRUTIL) library configuration

checking for APR-util... yes

checking APRUTIL version... 1.5.4

checking for pkg-config... no

checking for ANSI C header files... yes

checking for sys/types.h... yes

checking for sys/stat.h... yes

checking for stdlib.h... yes

checking for string.h... yes

checking for memory.h... yes

checking for strings.h... yes

checking for inttypes.h... yes

checking for stdint.h... yes

checking for unistd.h... yes

configure: serf library configuration via pkg-config

checking was serf enabled... no

An appropriate version of serf could not be found, so libsvn_ra_serf

will not be built. If you want to build libsvn_ra_serf, please

install serf 1.3.4 or newer.

configure: looking for apr_memcache as part of apr-util

checking apr_memcache.h usability... yes

checking apr_memcache.h presence... yes

checking for apr_memcache.h... yes

checking for apr_memcache_create in -laprutil-1... yes

checking for Apache module support via DSO through APXS... ./configure: line 5869: /usr/bin/apxs: No such file or directory

configure: error: no - APXS refers to an old version of Apache

                      Unable to locate /mod_dav.h


3. Not able to install 'libutf8proc-dev'

root_at_LCNAS:~# apt-get install libutf8proc-dev

Reading package lists... Done

Building dependency tree

Reading state information... Done

E: Unable to locate package libutf8proc-dev


4. < Do you already have libsvn*.so files installed on your system? > Yes. Subversion was working till there was a firmware upgrade in NAS. It was configured by another person, but he left the company.

root_at_LCNAS:/usr/lib/apache2/modules# ls

httpd.exp mod_cgi.so mod_parp.so

libphp5.so mod_charset_lite.so mod_privsep.so

mod_access_compat.so mod_csrf.so mod_proxy_ajp.so

mod_actions.so mod_data.so mod_proxy_balancer.so

mod_alias.so mod_dav_fs.so mod_proxy_connect.so

mod_allowmethods.so mod_dav_lock.so mod_proxy_express.so

mod_asis.so mod_dav.so mod_proxy_fcgi.so

mod_auth_basic.so mod_dav_svn.so mod_proxy_fdpass.so

mod_auth_digest.so mod_dbd.so mod_proxy_ftp.so

mod_auth_form.so mod_deflate.so mod_proxy_hcheck.so

mod_authn_alias.so mod_dialup.so mod_proxy_html.so

mod_authn_anon.so mod_dir.so mod_proxy_http.so

mod_authn_core.so mod_disk_cache.so mod_proxy_scgi.so

mod_authn_dbd.so mod_dumpio.so mod_proxy.so

mod_authn_dbm.so mod_echo.so mod_proxy_wstunnel.so

mod_authn_default.so mod_env.so mod_ratelimit.so

mod_authn_file.so mod_expires.so mod_reflector.so

mod_authn_privsep.so mod_ext_filter.so mod_remoteip.so

mod_authn_socache.so mod_file_cache.so mod_reqtimeout.so

mod_authnz_external.so mod_filter.so mod_request.so

mod_authnz_fcgi.so mod_headers.so mod_rewrite.so

mod_authnz_ldap.so mod_heartbeat.so mod_sed.so

mod_auth_token.so mod_heartmonitor.so mod_session_cookie.so

mod_authz_core.so mod_ident.so mod_session_crypto.so

mod_authz_dbd.so mod_imagemap.so mod_session_dbd.so

mod_authz_dbm.so mod_include.so mod_session.so

mod_authz_default.so mod_info.so mod_setenvif.so

mod_authz_groupfile.so mod_lbmethod_bybusyness.so mod_slotmem_plain.so

mod_authz_host.so mod_lbmethod_byrequests.so mod_slotmem_shm.so

mod_authz_owner.so mod_lbmethod_bytraffic.so mod_socache_dbm.so

mod_authz_svn.so mod_lbmethod_heartbeat.so mod_socache_memcache.so

mod_authz_unixgroup.so mod_ldap.so mod_socache_shmcb.so

mod_authz_user.so mod_log_debug.so mod_speling.so

mod_autoindex.so mod_log_forensic.so mod_ssl.so

mod_bucketeer.so mod_lua.so mod_status.so

mod_buffer.so mod_macro.so mod_substitute.so

mod_cache_disk.so mod_mem_cache.so mod_suexec.so

mod_cache.so mod_mime_magic.so mod_unique_id.so

mod_cache_socache.so mod_mime.so mod_userdir.so

mod_case_filter_in.so mod_mpm_event.so mod_usertrack.so

mod_case_filter.so mod_mpm_prefork.so mod_vhost_alias.so

mod_cern_meta.so mod_mpm_worker.so mod_xml2enc.so

mod_cgid.so mod_negotiation.so



Sanad MM

-----Original Message-----
From: Daniel Shahaf <d.s_at_daniel.shahaf.name>
Sent: Thursday, 25 June, 2020 7:09 AM
To: Nathan Hartman <hartman.nathan_at_gmail.com>
Cc: Sanad Majid <sanad.majid_at_LumaCyte.com>; users_at_subversion.apache.org
Subject: Re: Subversion Build Issues - 1.10.6

WARNING: This message originated from an external sender.

CAUTION: This email originated from outside of the organization. Do not click links or open attachments unless you recognize the sender and know the content is safe.

Nathan Hartman wrote on Wed, 24 Jun 2020 22:16 -0400:

> On Wed, Jun 24, 2020 at 9:13 AM Sanad Majid <sanad.majid_at_lumacyte.com<mailto:sanad.majid_at_lumacyte.com>>

> wrote:


> > I am trying to build Subverion 1.10.6 on our NAS (Netgear ReadyNAS

> > 104), but got following issues. Could anyone help me to resolve this

> > issue? Logs are given below.

> >

> (snip)


> > Q1. How to resolve serf issue?

> >

> > Q2. I couldn’t locate apxs script, but mod_dav_svn.so is present in

> > /usr/lib/apache2/modules. (for trying ./configure

> > --with-apxs=/usr/local/apache2/bin/apxs)

> >

> > Q3. How to resolve UTF8PROC Issues?

> >

> Have you tried:


> ./configure --with-serf=/path/to/serf --with-lz4=internal

> --with-utf8proc=internal


> That should help with Q1 and Q3. Not sure about Q2. There might be

> some other option(s) needed for configure, but let's try these first.

For Q1, you might be running into the bug that was fixed in version 1.3.9-3 of the libserf-dev Debian package:


    serf (1.3.9-3) unstable; urgency=medium

      * Add libssl-dev to libserf-dev's Depends, otherwise pkg-config can't

        provide information about serf.

     -- James McCoy <jamessan_at_debian.org<mailto:jamessan_at_debian.org>> Wed, 07 Jun 2017 23:09:48 -0400

Passing an argument to the --with-serf option will bypass pkg-config and sidestep the bug insofar as configure's detection of libserf is concerned, but you might want to install libssl-dev anyway if you'd like to be able to connect to repositories over https://.

For Q2, you might need to install the relevant package:


    % apt-file search bin/apxs

    apache2-dev: /usr/bin/apxs

    apache2-dev: /usr/bin/apxs2

The relevant configure option is --with-apxs, but you will likely not need to specify it explicitly once the package is installed.

For Q3, an alternative solution is to install libutf8proc-dev.

And if these guesses are correct, then for future reference see «apt-get build-dep subversion».

Do you already have libsvn*.so files installed on your system? On Debian derivatives there may be linker errors (at the end of the build) due to confusion between the installed libsvn*.so and the ones being built.


Received on 2020-06-25 16:53:11 CEST

This is an archived mail posted to the Subversion Users mailing list.

This site is subject to the Apache Privacy Policy and the Apache Public Forum Archive Policy.