On Wednesday 22 June 2005 11:10, Matthias Andree wrote: > Is this portable to non-GNU makes? > If it is not, does OpenVPN require GNU make? I don't think it does.
I'm afraid it's non-portable. Damn. > Is there a broken-out C program that fails to link at run-time if the > workaround is required? This would be tested from configure.{in|ac} and > set DLOPEN_PAM appropriately. If /lib/security/pam_unix.so is missing symbols then the workaround is required. We could try to link a program with /lib/security/pam_unix.so and if the linking fails (because symbols are missing) then the workaround is needed. Here's an example: [nomis80@poste10-153 ~]$ gcc main.c /lib/security/pam_unix.so [nomis80@poste10-153 ~]$ gcc main.c /lib/security/pam_smb_auth.so /lib/security/pam_smb_auth.so: undefined reference to `pam_get_item' /lib/security/pam_smb_auth.so: undefined reference to `pam_set_item' /lib/security/pam_smb_auth.so: undefined reference to `pam_get_user' collect2: ld returned 1 exit status main.c contains this: int main() { return 0; } On my system, pam_unix.so is not missing symbols while pam_smb_auth.so is. I tried to find a way to check this using autoconf but I'm not very good with it. Maybe you can do it in a few minutes... ;)