-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
On Mon 17 Jun 2013 07:54:58 AM EDT, Stephen Gallagher wrote:
Upstream considers the "definitive" build to be the one we use for
Fedora, since we're certain that it matches the Filesystem
Hierarchy Standard. SSSD will *never* work with just "./configure"
with no flags because we always need to be able to specify where
the nsswitch and PAM modules need to live because they're different
on different platforms, even different architectures of the same
OS. In Fedora, they need to be in /lib and /lib/security for i686
vs. /lib64 and/lib64/security on x86_64. There's no way to cleanly
autodetect this, so it must always be specified manually.
Thinking about this a little further, it might make sense to just
default --with-nsslibdir to /lib and --with-pamlibdir to
/lib/security. If I remember correctly, Debian always uses /lib for
the primary arch. I'm not sure how OpenSUSE does it, but maybe Steve
can enlighten me.
I suspect that just defaulting to /lib would work for a
reasonably-significant number of cases (especially given that the
recommended way to build for Fedora is with either the contrib macros
or 'make rpms').
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.13 (GNU/Linux)
Comment: Using GnuPG with Thunderbird -
http://www.enigmail.net/
iEYEARECAAYFAlG++f8ACgkQeiVVYja6o6P2kACfWRPzj5JlRETNswfCxQaYnh2W
PdYAnR6TAyveNjUyYKRmNJSrSVyam5Kd
=E5jD
-----END PGP SIGNATURE-----