Re[10]: subversion broken with apache2 now in ports
l...@freebsd.org
Tuesday, August 3, 2004, 12:09:11 AM, you wrote:
SM> IMHO, if svn were compiled with an rpath it should be resolved quite
SM> nicely.
I've wrote, that it is not solve problem: if I add
-rpath ${LOCALBASE}/lib/apache2
to LDFLAGS, `libtool' denies to install mod_dav_svn into
`${PREFIX}/libexec/apache2', so, subversion COULD NOT BE INSTALLED in such situation!
--
Best regards,
Lev mailto:l...@FreeBSD.org
_______________________________________________
freebs...@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-ports
To unsubscribe, send any mail to "freebsd-port...@freebsd.org"
l...@freebsd.org
Monday, August 2, 2004, 11:47:16 PM, you wrote:
CL> As you said previously, error appeared "around apache2-2.0.49!" to be
CL> more precise: apache-2.0.49_2, when I introduced apache2 RCng startup
CL> script. Previous script used apachectl to start apache2, new one start
CL> directly httpd.
CL> I forgot to add (I committed yesterday this missing part):
CL> if test -f /usr/local/sbin/envvars; then
CL> . /usr/local/sbin/envvars
CL> fi
CL> which sets LD_LIBRABRY_PATH. No more change between 2.0.49 and 2.0.50.
CL> All previous behaviour was done at run time.
Here are problem with this solution: `svn' command-line client and `svnserve' stand-alone server uses libapr TOO. If user builds subversion wiht apache2 module and then disables apache2 for some reason, this LD_LIBRARY_PATH will not be set, and user will not be able to use subversion even with local repository, because `svn' will stop to work!
And even worse: `make install' for subversion could try to create repository for user (depending on WITH_XXX options). And if apache2 was build as dependincy for subversion, it will not run yet, and subversion installation will fail with strange error: `svnadmin could not be run'.
CL> To answer you previous question about what may imply a move from
CL> ${PREFIX}/lib/apache2 to ${PREFIX}/lib. AFAIK, no port should be
CL> affected. But I'm a little bit (too much?) reticent to make apr/apache2
CL> ports conflict.
CL> It's a dilemna, and I don't know which choice is the best.
I think, that this conflict is better, than current situation.
cle...@freebsd.org
Content-Type: text/plain; charset=US-ASCII
Content-Disposition: inline
Content-Transfer-Encoding: 7bit
On Wed, 4 Aug 2004 23:47:32 +0400
Lev Serebryakov <l...@FreeBSD.org> wrote:
Hi Lev,
> What do you think about using `INSTALLS_SHLIB=yes' and
> `LDCONFIG_DIRS=%%PREFIX%%/lib/apache2' in apache2 port (of course,
> when it is not builded with `devel/apr' libapr)?
> IMHO, it will help even if apavche2 disable
> (/usr/local/etc/rc.d/apache.sh was not run on startup).
Same problem, if you reboot your system with apache2 disabled, ldconfig
-m ${PREFIX}/lib/apache2 is not run. So you surely can't rebuild the
port.
Yesterday, I tested a small patch which adds a pseudo apr standalone
mode for apache2, it installs libapr in ${PREFIX}/lib (but keeps headers
in ${PREFIX}/include/apache2). This is not a viable solution.
The only solution is to split apache2 port, even if I dislike this
solution. So, I'll work on an devel/apr-apache2 port ASAP.
clem
--Signature=_Wed__4_Aug_2004_23_06_42_+0200_EfuRR06mvlagrF7z
Content-Type: application/pgp-signature
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.2.4 (FreeBSD)
iD8DBQFBEU/jsRhfjwcjuh0RAmywAJ9LIa4o+s5itb+T7GZIadpg/eiV0ACZAS3B
iX2wvc+CEgiC6WBbJTXvbdQ=
=gSq8
-----END PGP SIGNATURE-----
--Signature=_Wed__4_Aug_2004_23_06_42_+0200_EfuRR06mvlagrF7z--