Subject: Re: CVS commit: src/lib/libpam/modules
To: None <source-changes@netbsd.org>
From: Christos Zoulas <christos@zoulas.com>
List: source-changes
Date: 12/29/2004 22:31:09
In article <20041229215728.6334B2356B@thoreau.thistledown.com.au>,
Simon Burge <simonb@wasabisystems.com> wrote:
>Luke Mewburn wrote:
>
>> Module Name:	src
>> Committed By:	lukem
>> Date:		Wed Dec 29 15:04:06 UTC 2004
>> 
>> Modified Files:
>> 
>> 	src/lib/libpam/modules: Makefile mod.mk
>> 	src/lib/libpam/modules/pam_krb5: Makefile
>> 	src/lib/libpam/modules/pam_ksu: Makefile
>> 	src/lib/libpam/modules/pam_lastlog: Makefile
>> 	src/lib/libpam/modules/pam_nologin: Makefile
>> 	src/lib/libpam/modules/pam_radius: Makefile
>> 	src/lib/libpam/modules/pam_ssh: Makefile
>> 	src/lib/libpam/modules/pam_unix: Makefile
>> 
>> Log Message:
>> 
>> Use LIBDPLIBS to provide the list of libraries for the modules to depend
>> upon, because:
>>  * it's MUCH quicker; no need to calculate the OBJDIRS of every library
>>    we might require in every subdir.
>>    (make obj drops from 21s to 3s on my system.)
>>  * it's more robust when building to a fresh DESTDIR.
>
>With this change, libpam/modules/Makefile tries to install
>lib.a and fails.  Just removing the
>
>    .include <bsd.lib.mk>
>
>gets things building and installing again with no other obvious
>problems.  OK if I commit that change?
>

Please.

christos