Date: Thu, 30 Jan 2014 15:27:31 -0800 From: Tim Gustafson <tjg@ucsc.edu> To: freebsd-ports-bugs@freebsd.org Subject: Error Building Subversion on 9.2 Message-ID: <CAPyBAS5TrVRSMqjU2jF07XLUN-uuN7Yu-CXNgjT0oopk5JSvtQ@mail.gmail.com>
next in thread | raw e-mail | index | archive | help
I'm getting the following error while building Subversion 1.8.5 with the mod_dav_svn option enabled on FreeBSD 9.2 via ports: ========== cd subversion/svnserve && /usr/local/bin/libtool --tag=CC --silent --mode=link cc -O2 -pipe -fpic -DPIC -fno-strict-aliasing -L/usr/local/lib -L/usr/local/lib/db42 -L/usr/local/lib -rpath /usr/local/lib -o svnserve cyrus_auth.lo log-escape.lo serve.lo svnserve.lo winservice.lo ../../subversion/libsvn_repos/libsvn_repos-1.la ../../subversion/libsvn_fs/libsvn_fs-1.la ../../subversion/libsvn_delta/libsvn_delta-1.la ../../subversion/libsvn_subr/libsvn_subr-1.la ../../subversion/libsvn_ra_svn/libsvn_ra_svn-1.la -L/usr/local/lib -laprutil-1 -L/usr/local/lib -lapr-1 libtool: link: you must specify an output file libtool: link: Try `libtool --help --mode=link' for more information. *** [subversion/mod_dav_svn/mod_dav_svn.la] Error code 1 1 error ===> Compilation failed unexpectedly. Try to set MAKE_JOBS_UNSAFE=yes and rebuild before reporting the failure to the maintainer. *** [do-build] Error code 1 Stop in /usr/ports/devel/subversion. *** [build] Error code 1 Stop in /usr/ports/devel/subversion. ========== If I turn off MOD_DAV_SVN, the problem goes away (but of course, I need mod_dav_svn to be built). This is an attempt to re-build a port that I've had installed for ages on a system that I recently upgraded from 9.2-beta to 9.2-release. I rebuilt all my other ports (via portmaster -a -f -D) and this was the only port to have an error. For the purposes of getting all the ports rebuilt, I turned off MOD_DAV_SVN and the portmaster command finished without incident. But now I can't re-start Apache because of the missing mod_dav_svn module. FWIW, I attempted to re-build subversion on a different 9.2-release machine and received the exact same error. Has there been some change to libtool to require a new command-line argument, or is something else wonky? -- Tim Gustafson tjg@ucsc.edu 831-459-5354 Baskin Engineering, Room 313A
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?CAPyBAS5TrVRSMqjU2jF07XLUN-uuN7Yu-CXNgjT0oopk5JSvtQ>