In that case, either invoke configure so that it compiles and links
against a single version of Kerberos (instead of compiling against one
and attempting to link against another as it is doing now), or edit the
Makefile after running configure to achieve the same effect, or, in the
worst case, remove one of the two versions of Kerberos from your system.
Unfortunately, I don't have access to a FreeBSD system to try things out
on, but, no, cosign should work just fine under FreeBSD. I recommend
using Google to find out how other people have solved this problem for
other software packages and then trying the same thing with cosign.
Mark Montague
ITS Web/Database Team
The University of Michigan
[email protected]
On February 25, 2010 16:01 , "Simon Chang" <[email protected]>
wrote:
> Well...
>
> Two things:
>
> 1) I tried piping krb5-config output into Cosign configure. No dice.
> Same errors.
>
> 2) The platform I am using is FreeBSD 7.2-release. According to
> FreeBSD's Handbook, a minimal installation of Heimdal is put in place
> whenever the base system is installed. There seems to be some
> disagreement as to whether an automated "make buildworld" (using a
> special flag to prevent Kerberos installation) would eliminate the
> built-in Heimdal.
>
> 3) To answer Mark's earlier question, no, we have not used the MIT
> Kerberos 1.7.1 for anything else, but the compilation went without any
> problems.
>
> So that's where everything stands. Have you guys heard of any problems
> with this version of FreeBSD?
>
> SC
>
> -----Original Message-----
> From: Russ Allbery [mailto:[email protected]]
> Sent: Thursday, February 25, 2010 2:26 PM
> To: Simon Chang
> Cc: Mark Montague; [email protected]
> Subject: Re: [Cosign-discuss] Cosign.conf and Active Directory
> configuration
>
> "Simon Chang"<[email protected]> writes:
>
>
>> OK...
>>
>
>> So, if it is the case that krb5-config and the libraries got confused,
>>
>
>> what should I do?
>>
>
>> I think Mark suggested that I run "krb5-config -cflags" and pipe the
>> output into the configure program for Cosign. Would that work?
>>
> Well, under normal circumstances you don't want to have two different
> Kerberos implementations installed at the same time. So the easiest way
> is to delete the one that you're not using (MIT or Heimdal) and build
> Cosign against the one you actually want to use.
>
> Anything else is more complicated and involves ensuring that the Cosign
> configure process runs the krb5-config script corresponding to the
> libraries that you want to link against.
>
>
------------------------------------------------------------------------------
Download Intel® Parallel Studio Eval
Try the new software tools for yourself. Speed compiling, find bugs
proactively, and fine-tune applications for parallel performance.
See why Intel Parallel Studio got high marks during beta.
http://p.sf.net/sfu/intel-sw-dev
_______________________________________________
Cosign-discuss mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/cosign-discuss
