All of lore.kernel.org
 help / color / mirror / Atom feed
From: Guillaume Rousse <Guillaume.Rousse@inria.fr>
To: autofs@linux.kernel.org
Subject: Re: autofs segfault at startup on x86_64
Date: Tue, 03 Jan 2006 13:48:06 +0100	[thread overview]
Message-ID: <43BA7286.50101@inria.fr> (raw)
In-Reply-To: <1136287828.2350.10.camel@eagle.themaw.net>

Ian Kent wrote:
> On Tue, 2006-01-03 at 11:49 +0100, Guillaume Rousse wrote:
> 
>>I've been instructed to report this here instead of kernel bugzilla:
>>http://bugzilla.kernel.org/show_bug.cgi?id=5561
>>
> 
> 
> Hi Guillaume,
> 
> Yes, I'll follow up on this.
> 
> Perhaps a simple patch for configure would be a good workaround while I
> check out what's required. It appears you have spent a fair bit of time
> on this already but it would help if you could give me a brief
> description of your understanding of the problem and what you have found
> out so far.
Autofs requires to be compiled with -DLDAP_DEPRECATED on x86_64
platforms when linked against openldap >= 2.3, otherwise it
automatically triggers a segfault in openldap library during
initialisation (more exactly, in ldap_set_option() call from
do_connect() in lookup_ldap.c).

OpenLDAP maintainers suggest to either use this flags automatically
during compilation, or to change autofs code to use newest API.

-- 
No flight ever leaves on time unless you are running late and need the
delay to make the flight
		-- Murphy's Laws for Frequent Flyers n°1

  reply	other threads:[~2006-01-03 12:48 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-01-03 10:49 autofs segfault at startup on x86_64 Guillaume Rousse
2006-01-03 11:30 ` Ian Kent
2006-01-03 12:48   ` Guillaume Rousse [this message]
2006-01-04 16:14     ` Ian Kent

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=43BA7286.50101@inria.fr \
    --to=guillaume.rousse@inria.fr \
    --cc=autofs@linux.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.