Date: Sat, 25 Jun 2005 11:45:09 +0200 From: =?ISO-8859-1?Q?=22Jos=E9_M=2E_Fandi=F1o=22?= <fandino@ng.fadesa.es> To: FreeBSD-gnats-submit@FreeBSD.org Subject: ports/82634: heimdal port conflict with base heimdal Message-ID: <42BD27A5.2020200@ng.fadesa.es> Resent-Message-ID: <200506250950.j5P9oFBP005661@freefall.freebsd.org>
next in thread | raw e-mail | index | archive | help
>Number: 82634 >Category: ports >Synopsis: heimdal port conflict with base heimdal >Confidential: no >Severity: non-critical >Priority: low >Responsible: freebsd-ports-bugs >State: open >Quarter: >Keywords: >Date-Required: >Class: sw-bug >Submitter-Id: current-users >Arrival-Date: Sat Jun 25 09:50:15 GMT 2005 >Closed-Date: >Last-Modified: >Originator: Jose M. Fandino >Release: FreeBSD 5.4-RELEASE-p2 i386 >Organization: none >Environment: System: FreeBSD damocles.olimpus 5.4-RELEASE-p2 FreeBSD 5.4-RELEASE-p2 #0: Sat Jun 18 14:23:54 CEST 2005 root@damocles.olimpus:/usr/local/obj/usr/local/src/sys/DAMOCLES i386 When the heimdal port is installed with ldap support and you try to use the ldap backend the library search path takes the heimdal base libraries firts, this causes the heimdal port programs and utilities to use system libraries instead the ldap enabled ones. Perhaps the real problem is how to resolve the cases where the same program is present in the base system and in the port collection. A detailled explanation can be found here: http://lists.freebsd.org/pipermail/freebsd-ports/2005-June/023760.html and a proposed solution can be: http://lists.freebsd.org/pipermail/freebsd-ports/2005-June/023907.html >Description: >How-To-Repeat: >Fix: >Release-Note: >Audit-Trail: >Unformatted:
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?42BD27A5.2020200>