Re: Tru64 and C2

At 5:18 PM -0600 12/3/07, J Springer wrote:

>  Randall Gellens wrote:
>
>>  Hmmm.  I think I see the problem.  There is some confusion in the 
>> script with "no" and "no_" for pam, and only for pam.  Problem ...
>>  ...snip...
>>  ... confirmation, if you don't mind, could you run the attached 
>> ./configure script (after another 'make realclean') and send me 
>> the output?
>
>  Holler when you're ready for me to run another test.
>
>  I have one [dumb] question, if configure fails and a Makefile isn't 
> created, shouldn't 'make realclean' fail?  Or do I need to copy the 
> Makefile.in to Makefile first?

If ./configure fails, then there is no Makefile, and hence 'make 
realclea' will fail.  That's fine, as there shouldn't be a config.h 
or any of the other files created by ./configure.  I get in the habit 
of recommending 'make realclean' just to be sure that the stuff isn't 
there.  So, no need to copy a Makefile.

>  ./configure --enable-temp-drop-dir=/usr/poptmp --enable-log-login 
> --enable-server-mode --enable-standalone --enable-specialauth
>
>  "use_pam is no_"
>  checking for dlopen in -ldl... no
>  checking for pam_authenticate in -lpam... no
>  Can't use PAM: can't find libpam

OK, that confirms what I found the first time.  The second 
./configure I sent does indeed fix what I found the first time, which 
is why pam was enabled by default when it should be off by default.

At 6:21 PM -0600 12/3/07, Vic Summerour wrote:

>  At 03:47 PM 12/2/2007 -0800, Randall Gellens wrote:
>>  At 4:10 PM -0600 12/2/07, Vic Summerour wrote:
>>
>>>   I have used qpopper with Tru64, Digital Unix, OSF/1 for years. 
>>> Sometime in the ...
>>>  ...snip...
>>>   ./configure --enable-specialauth --without-pam
>>
>>  Was --enable-specialauth needed?  If you left it off, what happened?
>
>  With ./configure only, the following occurs:
>
>  ./configure
>   .
>   .
>   .
>  checking for pam_authenticate in -lpam... no
>  Can't use PAM: can't find libpam

This is fixed by the first change to ./configure.

>  With ./configure --without-pam, it will configure and compile 
> correctly.  Attempts to retrieve pop mail results in an invalid 
> password message:
>
>  With ./configure --enable-specialauth --without-pam, it will 
> configure correctly, compile, and work.

I believe this is because TRUE64 uses getprpwnam() instead of 
getspnam(), and ./configure was only checking for the later when 
deciding if specialauth should be enabled by default.  I've added a 
check for the former, so hopefully a default ./configure will now 
correctly check passwords on True64.  If you could verify this for 
me, I'd be very grateful.  I'm attaching a new ./configure.  Please 
be sure to do a 'make realclean' beforehand.