[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: [mechglue] Static Linking - Circular Dependency
On Wed, 26 Apr 2006 11:46:58 +0200
Gabor Gombas <firstname.lastname@example.org> wrote:
> On Tue, Apr 25, 2006 at 02:59:07PM -0400, Michael B Allen wrote:
> > To statically link however I modified mechglue/g_initialize.c to call
> > gss_spnego_initialize call immediately after the gss_krb5_initialize
> > call and commented out the gss_dynamic_initialize call. Then I added
> > a libgssapi dependency on libmech_spnego and somehow managed to do
> > things in the right sequence to actually build cleanly. I guess somehow
> > I managed to recreate the libgssapi.la file without rebuilding the whole
> > thing. But now I can't reproduce the process.
> You can modify the individual mechs not to link against libgssapi. That
> is not a problem in the static case and solves the circular dependency.
> AFAIK any program linking to libgssapi then will have to specify it
> twice on the linker command line:
> -lgssapi -lmech_krb5 -lmech_spnego -lgssapi
Do you know from experience that this works? Aside from complicating the
user linking process a litte, libgssapi needs to call gss_krb5_initialize
and gss_spnego_initialize to install their mechanisms.
At least I know it's just a build system issue.