All of lore.kernel.org
 help / color / mirror / Atom feed
From: Steve Dickson <SteveD@redhat.com>
To: Benjamin Coddington <bcodding@uvm.edu>
Cc: linux-nfs@vger.kernel.org
Subject: Re: svcgssd problem against libgssapi_krb5
Date: Tue, 12 Jul 2011 11:49:01 -0400	[thread overview]
Message-ID: <4E1C6CED.3080800@RedHat.com> (raw)
In-Reply-To: <FE208962-EC0E-4880-8814-63E11A847AD4@uvm.edu>


On 07/11/2011 02:46 PM, Benjamin Coddington wrote:
> This problem is caused by including -ltirpc, where libtirpc.la lists -lgssglue as a dependency.  Libtool (2.2.6b) then re-evaluates the order of linked libraries putting libgssglue behind libgssapi_krb5.
> 
> I fixed this by specifying -lgssglue with -Wl, which is ignored by libtool:
> 
> GSSGLUE_CFLAGS="-Wl,-lgssglue" ./configure
Hmm... The question I have is why are the .la even coming into play?
The libs should be dynamically loaded...

steved.

> 
> Ben
> 
> On Jul 11, 2011, at 12:30 PM, Benjamin Coddington wrote:
> 
>> I have a problem building svcgssd from nfs-utils-1.2.3:
>>
>> svcgssd[15145]: DEBUG: serialize_krb5_ctx: lucid version!
>> svcgssd[15145]: ERROR: GSS-API: error in gss_export_lucid_sec_context(): GSS_S_NO_CONTEXT (No context has been established) - (0x00007fff)
>> svcgssd[15145]: ERROR: failed serializing krb5 context for kernel
>> svcgssd[15145]: WARNING: handle_nullreq: serialize_context_for_kernel failed
>>
>> I found that the svcgssd I built ran differently than the one that works from a major distro.
>>
>> My broken one does this:
>>
>> gssint_mechglue_initialize_library () at g_initialize.c:135
>> 135	{
>> (gdb) bt
>> #0  gssint_mechglue_initialize_library () at g_initialize.c:135
>> #1  0x00007ffff79a9f75 in gss_indicate_mechs (minorStatus=0x7fffffffe50c, mechSet_out=0x7fffffffe500) at g_initialize.c:220
>> #2  0x00000000004021ae in gssd_check_mechs () at gss_util.c:241
>> #3  0x0000000000402777 in main (argc=3, argv=<value optimized out>) at svcgssd.c:239
>>
>>
>> But if I remove -lgssapi_krb5, svcgssd works fine, and behaves like the one from the distro:
>>
>> gss_initialize () at g_initialize.c:148
>> 148	{
>> (gdb) bt
>> #0  gss_initialize () at g_initialize.c:148
>> #1  0x00007ffff6e82f6e in gss_indicate_mechs (minor_status=0x7fffffffe50c, mech_set=0x7fffffffe500) at g_indicate_mechs.c:54
>> #2  0x000000000040216e in gssd_check_mechs () at gss_util.c:241
>> #3  0x0000000000402737 in main (argc=3, argv=<value optimized out>) at svcgssd.c:239
>>
>>
>> Ben--
>> To unsubscribe from this list: send the line "unsubscribe linux-nfs" in
>> the body of a message to majordomo@vger.kernel.org
>> More majordomo info at  http://vger.kernel.org/majordomo-info.html
> 
> --
> To unsubscribe from this list: send the line "unsubscribe linux-nfs" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at  http://vger.kernel.org/majordomo-info.html

  reply	other threads:[~2011-07-12 15:49 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-07-11 16:30 svcgssd problem against libgssapi_krb5 Benjamin Coddington
2011-07-11 18:46 ` Benjamin Coddington
2011-07-12 15:49   ` Steve Dickson [this message]
2011-07-12 19:02     ` Benjamin Coddington

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=4E1C6CED.3080800@RedHat.com \
    --to=steved@redhat.com \
    --cc=bcodding@uvm.edu \
    --cc=linux-nfs@vger.kernel.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.