subversion-users mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Bert Huijben" <b...@qqmail.nl>
Subject RE: subversion 1.9.2 could not be built "all-static" on FreeBSD 10+
Date Mon, 19 Oct 2015 11:30:23 GMT


> -----Original Message-----
> From: Bert Huijben [mailto:bert@qqmail.nl]
> Sent: maandag 19 oktober 2015 13:22
> To: 'Philip Martin' <philip.martin@wandisco.com>; 'Lev Serebryakov'
> <lev@FreeBSD.org>
> Cc: 'Daniel Shahaf' <d.s@daniel.shahaf.name>;
> users@subversion.apache.org
> Subject: RE: subversion 1.9.2 could not be built "all-static" on FreeBSD
10+
> 
> 
> 
> > -----Original Message-----
> > From: Philip Martin [mailto:philip.martin@wandisco.com]
> > Sent: maandag 19 oktober 2015 11:19
> > To: Lev Serebryakov <lev@FreeBSD.org>
> > Cc: Daniel Shahaf <d.s@daniel.shahaf.name>;
> users@subversion.apache.org
> > Subject: Re: subversion 1.9.2 could not be built "all-static" on FreeBSD
> 10+
> >
> > Lev Serebryakov <lev@FreeBSD.org> writes:
> >
> > > Hello Daniel,
> > >
> > > Sunday, October 18, 2015, 11:08:45 AM, you wrote:
> > >
> > >>>  I could not build subversion 1.9.2 with "--enable-all-static" on
> FreeBSD.
> > >>> "configure" script forms wron arguments to ${CC} in this case and
> fails to
> > >>> find any library.
> > >>>
> > >>>  Here is couple of lines from config.log for 1.9.2:
> > >>>
> > >>> configure:6130: checking for sqlite3_close in -lsqlite3
> > >>> configure:6155: cc -o conftest -Werror=unknown-warning-option -O2
> > >>> -pipe -fpic -DPIC -fstack-protector -fno-strict-aliasing
> > >>> -I/usr/local/include -fstack-protector -L/usr/local/lib
> > >>> -L/usr/local/lib -L/usr/local/lib -R/usr/local/lib -L/usr/local/lib
> > >>> -R/usr/local/lib -L/usr/local/lib conftest.c -lsqlite3 >&5
> > >>> cc: error: unknown argument: '-R/usr/local/lib'
> > >>> cc: error: unknown argument: '-R/usr/local/lib'
> > >>> configure:6155: $? = 1
> > >
> > >> I assume you're building the 1.9.2 tarball, correct?  Does the
problem
> > >   Yep.
> > >
> > >> also occur if you build from a checkout of the 1.9.2 tag?  (You'll
need
> > >> to run autogen.sh before configure.)
> > >   Yes. Here is version of tools used by autogen.sh:
> > >
> > > buildcheck: autoconf version 2.69 (ok)
> > > buildcheck: autoheader version 2.69 (ok)
> > > buildcheck: libtool version 2.4.6 (ok)
> > >
> > >  And after that same error if "--enable-all-static" is passed.
> >
> > On my FreeBSD 10.1 install I get further than that when I try to build
> > the 1.9.x branch, but linking svn fails due unresolved SSL symbols.  I
> > can fix it by changing LIBS in Makefile to add -lssl -lcrypto.
> >
> > Subversion configure script does not add the -R so I suppose on of the
> > dependencies must be telling Subversion to add it.  What does your
> > configure line look like?  Have you build any of the dependencies
> > yourself?
> 
> I think I found these flags in /usr/local/libdata/pkgconfig/serf-1.pc
> 
> [[
> SERF_MAJOR_VERSION=1
> prefix=/usr/local
> exec_prefix=${prefix}
> libdir=/usr/local/lib
> includedir=${prefix}/include/serf-1
> 
> Name: serf
> Description: HTTP client library
> Version: 1.3.8
> Requires.private:
> Libs: -L${libdir} -lserf-${SERF_MAJOR_VERSION}
> Libs.private: -L/usr/local/lib -R/usr/local/lib -laprutil-1  -ldb-5.3
-lgdbm
> -lexpat -L/usr/local/lib -R/usr/local/lib -lapr-1 -lcrypt  -lpthread  -lz
> -L/usr/lib -lssl -lcrypto
> Cflags: -I${includedir}
> ]]

And now including dev@serf, as I think this should be fixed there:

It looks like serf gets these flags from:
$ apr-1-config --link-libtool

Which is invoked from SConstruct

[[
    ### there is probably a better way to run/capture output.
    ### env.ParseConfig() may be handy for getting this stuff into the build
    apr_libs = os.popen(env.subst('$APR --link-libtool
--libs')).read().strip()
    if apr_major < 2:
      apu_libs = os.popen(env.subst('$APU --link-libtool
--libs')).read().strip()
    else:
      apu_libs = ''
]]

And at this point I don't know what this is supposed to do.

	Bert



Mime
View raw message