building static library libpam

[Sudarshan Soma]

Thanks  Thorsten.

I was doing crosscompilation for ppc architecture.
I use the following options for crosscompiling with configure,

 CC=/opt/ELDK41/usr/bin/ppc_6xx-gcc  --disable-selinux
--host=ppc-linux-gnu -target=ppc-linux-gnu --build=i686-linux-gnu
--includedir=/opt/ELDK41/ppc_6xx/usr/include/security/

I find the following problems with this:

-- It directly didnt build .so , I manually created .so with all the
.o's formed. With this
the libpam looks like linked statically to pam_unix.so module,
although i didnt mention static flag anywhere.

when i do  /opt/ELDK41/usr/bin/ppc_6xx-nm on pam_unix.so, it gives
pam_get_item defined, but
pam_modutil_getlogin and similar modutil functions undefined.

/opt/ELDK41/usr/bin/ppc_6xx-nm .libs/pam_unix.so |grep modutil
         U pam_modutil_getlogin

Can anyone please let me know if i am  missing somehting here.

Thanks and Best Regards,
Pavan

On Sun, Mar 1, 2009 at 8:02 PM, Thorsten Kukuk <kukuk at suse.de> wrote:
> On Sun, Mar 01, Sudarshan Soma wrote:
>
>> Hi All,
>>
>> I have downloaded the latest PAM library and modules ,Linux-PAM-1.0.3.
>> Can any one please let me know how can i build libpam.a(static library
>> that i would link it to the pam modules)
>
> You should never link shared modules against static libraries.
> On i586 this may work, but on x86-64 for example this is strictly
> forbidden.
>
> Else read the README, there it is explained.
>
>  Thorsten
>
> --
> Thorsten Kukuk, Project Manager/Release Manager SLES
> SUSE LINUX Products GmbH, Maxfeldstr. 5, D-90409 Nuernberg
> GF: Markus Rex, HRB 16746 (AG Nuernberg)
>
> _______________________________________________
> Pam-list mailing list
> Pam-list at redhat.com
> https://www.redhat.com/mailman/listinfo/pam-list
>