> > Some other things to kill : > > > > We might want to #undef the printf() macro. Using a #ifdef inside a > > printf() (which is a macro onder all glibc versions I've seen) causes a > > compile error. > > > > This is fixed in the next glibc version. > > This sounds line a Linux thing :-). We don't use GLibC. Yes and no. No for a 'linux thing', Yes for 'we don't use Glibc'. Glibc has the #define printf(...) fprintf(stdout, ....), but it affects all platforms with gcc 3.x. It simply hates #defines in macro's, so it's an issue for all platforms which use gcc. The #undef just makes sure you don't get the errors. > > > o The FreeBSD modules live in /usr/lib/, not /lib/security/. > > > > Bad change IMHO. All in /usr/lib clutters the lib dir. Most distribs / > > installs put separate things in seperate libs in /usr/lib. I personaly > > like that, some of you might not. > > It is "FreeBSD Standard", and anything else would surprise FreeBSD admins. /lib/security is a defacto Solaris (is it ?) and Linux standard. Most programs expect them in /lib/security. > > > o The FreeBSD modules are mosly written from scratch and very > > > different from the Linux ones. I have not included them here. > > > I can send a copy if you are interested. > > > > I certainly am. > > Under serparate cover, I'll send you my Work-in-Progress directory. > > > > o For the manual pages, we have done a general s/Linux-PAM/PAM/. > > > Most of the diffs are trivial, so I have not included them. > > > By choice, FreeBSD uses the -mdoc macros. We recommend these > > > highly :-). > > > > Does -mdoc give you the choice to build without docs ? > > er, -mdoc is a macro set like -man, -me, -ms and so on. > Its up to the Makefiles and configuration options whether > or not you actually build the docs. Ah, that clears things up.. I usually hack the docs out on this platform. A daily job :) > M Igmar
