From: Guillaume Rousse <Guillaume.Rousse@inria.fr>
To: autofs@linux.kernel.org
Subject: Re: broken hesiod check
Date: Wed, 23 Aug 2006 16:46:20 +0200 [thread overview]
Message-ID: <44EC6A3C.2010309@inria.fr> (raw)
In-Reply-To: <44EC6677.1070609@inria.fr>
Guillaume Rousse wrote:
> The hesiod check macros breaks configure script by changing LIBS value
> inconditionally, wich is evil.
I forget to precise it had also the unpleasant effect of making all
following checks (sasl, ldap) fails because -lhesiod is systematically
added to the linking attempt.
--
Guillaume Rousse
Projet Estime, INRIA
Domaine de Voluceau
Rocquencourt - B.P. 105
78153 Le Chesnay Cedex - France
prev parent reply other threads:[~2006-08-23 14:46 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-08-23 14:30 broken hesiod check Guillaume Rousse
2006-08-23 14:46 ` Guillaume Rousse [this message]
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=44EC6A3C.2010309@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.