2009/10/5 Diego Elio “Flameeyes” <[email protected]>:
> Hi,
Hello,
> I'm a Gentoo Linux developer and I recently got my hands on a token that
> works with opensc, so I started looking into improving our support for
> it in PAM (I'm the maintainer of the PAM packages).
>
> Looking at pam_pkcs11 I found that the build system is slightly
> sub-optimal, in the sense that it builds, by default, static objects for
> plugins (like the PAM module itself),
According to gcc(1):
-shared
Produce a shared object which can then be linked with other objects
to form an executable. Not all systems support this option. For
predictable results, you must also specify the same set of options
that were used to generate code (-fpic, -fPIC, or model suboptions)
when you specify this option.[1]
"Not all systems support this option".
If you do not want the static libs (and I guess nobody will use them)
you should use:
./configure --disable-static
I don't know if you can configure configure.in to use --disable-static
by default.
> and uses a custom override rule
> for install to avoid installing the static version.
Fixed in revision 376.
> It also install the examples in the datadir instead of the docdir (which
> is what you would probably want, even the manual on the site refers
> to /usr/share/doc).
Fixed in revision 373.
> The attached patch fixes both problems, and at the same time defines a
> pamdir variable that can be used to select a different location for the
> PAM module (not all systems use the same path).
Thanks for the patch.
Please, can you split the patch in independent patches next time, so
we can discuss/apply them independently?
Bye
--
Dr. Ludovic Rousseau
_______________________________________________
opensc-devel mailing list
[email protected]
http://www.opensc-project.org/mailman/listinfo/opensc-devel
