FWIW, same issue using the 1.5.1 distro too (to be expected if its a
config problem at my end I guess).
On 28 Jul 2008, at 07:23, Russell Hind wrote:
> Hi Mark and Jeremy,
> This is a on a new Mac Mini, it came with 10.5.2 so I upgraded using
> the 10.5.4 combo updated and then installed any more updates.
> Enabled personal web sharing to get apache running and then added
> LoadModule dav_svn_module libexec/apache2/mod_dav_svn.so to get the
> standard installed subversion running and a <Location /svn>
> This has been running fine.
> I've then installed your 1.5.0 distro and changed the LoadModule
> line to
> LoadModule dav_svn_module /opt/subversion/lib/svn-apache/
> And ran the apache test config (apachectl -t) just to check and got
> the aforementioned error. I've never played with library paths
> etc. Should I need to after running your installed? How do I check
> The only thing I've changed (but won't affect apache) is in my
> own .profile I've added an
> export PATH=/opt/subversion/bin:$PATH
> so that for my user, svn-1.5.0 is the default. I see your installed
> puts symlinks in /usr/local/bin, but on my 10.5.4 systems, the
> default path is:
> So the standard install of svn in /usr/bin gets picked up first.
> How would you recommend changing this because it seems the installer
> (for 10.5 anyway, don't think 10.4 came with svn) isn't setting this
> up correctly. Perhaps its a similar problem for apache too?
> On 26 Jul 2008, at 15:04, Mark Phippard wrote:
>> On Sat, Jul 26, 2008 at 4:05 AM, Jeremy Whitlock <jcscoobyrs_at_gmail.com
>> > wrote:
>>>> httpd: Syntax error on line 484 of /private/etc/apache2/httpd.conf:
>>>> Syntax error on line 2 of /private/etc/apache2/other/
>>>> Cannot load /opt/subversion/lib/svn-apache/mod_dav_svn.so into
>>>> dlopen(/opt/subversion/lib/svn-apache/mod_dav_svn.so, 10):
>>>> Symbol not found: _svn_atomic__init_once
>>>> Referenced from: /opt/subversion/lib/libsvn_fs_base-1.0.dylib
>>>> Expected in: flat namespace
>>> I maintain that package and I run Subversion 1.5.0 with the built-in
>>> Apache without any issues at all. The only thing I can think of is
>>> that maybe your PATH or DYLD_LIBRARY_PATH is picking up the Leopard
>>> libs instead of the ones shipped with the binary. I've not ran into
>>> this and you're the first to report it. Is there any chance you're
>>> using SASL? I do know that the SASL support wasn't shipped with the
>>> 1.5.0 binary but is included in the 1.5.1. Any information you can
>>> give me would be very beneficial.
>> SASL is only used by svnserve so would not be a factor here. I think
>> the problem is likely the library path as you indicated. It looks
>> like an older version of a library is being loaded and a new symbol
>> not being found.
To unsubscribe, e-mail: users-unsubscribe_at_subversion.tigris.org
For additional commands, e-mail: users-help_at_subversion.tigris.org
Received on 2008-07-28 09:09:52 CEST