Date: Thu, 14 Jun 2007 03:11:14 -0700 From: David Southwell <david@vizion2000.net> To: Undisclosed.Recipients: ; Cc: ports@freebsd.org, Scot Hetzel <swhetzel@gmail.com> Subject: Re: subversion -- compile file - requires lgssapi_krb5 __SOLVED Message-ID: <200706140311.14759.david@vizion2000.net> In-Reply-To: <790a9fff0706131049ub81b224r8508fd0c5e7faba6@mail.gmail.com> References: <200706130701.38988.david@vizion2000.net> <200706131010.50425.david@vizion2000.net> <790a9fff0706131049ub81b224r8508fd0c5e7faba6@mail.gmail.com>
next in thread | previous in thread | raw e-mail | index | archive | help
On Wednesday 13 June 2007 10:49:31 Scot Hetzel wrote:
> On 6/13/07, David Southwell <david@vizion2000.net> wrote:
> > here is what I have:
> >
> > [root@dns1 /usr/bin]# ls -l /usr/lib/libgss*
> > -r--r--r-- 1 root wheel 141960 Feb 27 10:24 /usr/lib/libgssapi.a
> > lrwxr-xr-x 1 root wheel 14 Mar 23 07:59 /usr/lib/libgssapi.so ->
> > libgssapi.so.8
> > -r--r--r-- 1 root wheel 63056 Mar 23 07:59 /usr/lib/libgssapi.so.8
> > -r--r--r-- 1 root wheel 146556 Feb 27 10:24 /usr/lib/libgssapi_p.a
> >
> > I have a hazy recolection that, at some time, there was a conflict
> > between kerberos and something else.
>
> Heimdal and MIT Kerberos 5?
That sounds familiar
>
> On -CURRENT, src/kerberos5/lib/libgssapi/Makefile builds
> libgssapi_krb5*, but on RELENG_6 it only builds libgssapi.*.
Ok I am working with this and commenting as I go.
I am on 6.1 :
# uname -a
FreeBSD dns1.vizion2000.net 6.1-RELEASE FreeBSD 6.1-RELEASE #0: Sun May 7
04:15:57 UTC 2006 root@bloom.cse.buffalo.edu:/usr/obj/usr/src/sys/SMP
amd64
>
> Have a look at the configure script and try to determine why it is
> choosing the wrong version of Kerberos 5 for your system.
>
I presume you mean the subversion configure script?
Only one reference to kerberos found in the port files:
[root@dns1 /usr/ports/devel/subversion]# fgrep -R kerberos ./*
./work/subversion-1.4.3/INSTALL: "--with-libs=/usr/kerberos" for OpenSSL
to be found. The zlib library
[root@dns1 /usr/ports/devel/subversion]#
In INSTALL:
On Unix systems, if you are building neon as part of the Subversion
build process (as described in section I.4 above), you can pass flags
to Subversion's "./configure", and they will be passed on to neon's
"./configure". You need OpenSSL installed on your system, and you
must add "--with-ssl" as a "./configure" parameter. If your OpenSSL
installation is hard for Neon to find, you may need to use
"--with-libs=/path/to/lib" in addition. In particular, on Red Hat
(but not Fedora Core) it is necessary to specify
"--with-libs=/usr/kerberos" for OpenSSL to be found.
Section 1.4
We recommend that you keep the neon installation out of the
Subversion working copy. This is because most developers have
multiple working copies of Subversion, and it is easier to use a
single instance of the Neon library for all instances. To do
this, just unzip/untar Neon, and build and install it according
to its own standard installation instructions. Then follow the
steps below to use the installed Neon when building
Subversion's configuration mechanism should auto-detect the
installed Neon.
CONCLUSION:
I wonder if neon packaged with subversion does not test for the correct
version?
What happenes if in /usr/ports/www/neon > make deinstall followed by a clean
reconfigure & make and then attempt a new install of subversion???
OK Success that works!!! :-)
I will pass the results to the maintainer via a PR
Thanks for getting me onto the right track.
david
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?200706140311.14759.david>