Re: [Proftpd-user] Making proftpd 1.3.4 with mod_auth_pam, link error

[TJ S. <tj...@ca...>]

> Steps being followed:
> make distclean
> ./configure --enable-dso 
> --with-shared=mod_rewrite:mod_ldap:mod_facl:mod_auth_pam 
> --with-libraries=/lib64:/lib64/security
> make
> make install
> 
> Failure in the make step: 
> 
> make[1]: Entering directory `/tmp/proftpd-1.3.4/modules'
> /bin/sh ../libtool --mode=compile --tag=CC gcc -DHAVE_CONFIG_H  -DLINUX 
> -I.. -I../include  -O2 -Wall -DPR_SHARED_MODULE -c mod_auth_pam.c
> libtool: compile:  gcc -DHAVE_CONFIG_H -DLINUX -I.. -I../include -O2 -Wall 
> -DPR_SHARED_MODULE -c mod_auth_pam.c  -fPIC -DPIC -o .libs/mod_auth_pam.o
> libtool: compile:  gcc -DHAVE_CONFIG_H -DLINUX -I.. -I../include -O2 -Wall 
> -DPR_SHARED_MODULE -c mod_auth_pam.c -o mod_auth_pam.o >/dev/null 2>&1
> /bin/sh ../libtool --mode=link --tag=CC gcc -o mod_auth_pam.la -rpath 
> /usr/local/libexec -L../lib  -L/lib -L/lib/security -avoid-version 
> -export-dynamic -module mod_auth_pam.lo `cat ../modules/mod_auth_pam.c | 
> grep '$Libraries:' | sed -e 's/^.*\$Libraries: \(.*\)\\$/\1/'`
> libtool: link: gcc -shared  .libs/mod_auth_pam.o -L/tmp/proftpd-1.3.4/lib 
> -L/lib64 -L/lib64/security -lpam    -Wl,-soname -Wl,mod_auth_pam.so -o 
> .libs/mod_auth_pam.so
> /usr/bin/ld: cannot find -lpam
> collect2: ld returned 1 exit status
> make[1]: *** [mod_auth_pam.la] Error 1
> make[1]: Leaving directory `/tmp/proftpd-1.3.4/modules'
> make: *** [modules] Error 2

ProFTPD's configure script automatically tries to detect the presence of 
the PAM libraries, and whatever else is needed to use PAM on that 
platform.  Thus there should be no need to explicitly request that the 
mod_auth_pam module be built; if the configure script detects acceptable 
PAM support, then the mod_auth_pam module is automatically included in the 
build.

The config.log, generated by the configure script, will contain the 
results of various tests that the configure script runs to determine the 
state of PAM support on that platform.

You might also check the /etc/ld.so.conf (and /etc/ld.so.conf.d/* files, 
present) to see whether that /lib64 directory is acceptable to the linker.

Cheers,
TJ

~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~

   Desire does not necessitate obligation.

     -TJ Saunders

~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~