Lev Serebryakov <lev_at_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?
Why do you want to build --enable-all-static?
--
Philip Martin
WANdisco
Received on 2015-10-19 11:19:37 CEST