I have used qpopper with Tru64, Digital Unix, OSF/1 for
years. Sometime in the not so distant past but I can't remember when
or the details of why, I have had to configure with the following:
./configure --enable-specialauth --without-pam
Currently with Tru64 V5.1A with PK6, I have successfully compiled and
run 4.1a4 with the following compiler:
alpha> cc -V
Compaq C V6.4-014 on Compaq Tru64 UNIX V5.1A (Rev. 1885)
Compiler Driver V6.4-215 (sys) cc Driver
Unfortunately, 4.1a5 will not successfully compile based on the same
configure. It stop with the error:
cc -c -I.. -I.. -I. \
-I../mmangle -I../common \
-g -DHAVE_CONFIG_H -DOSF1 -DUNIX main.c -o main.o
cc: Error: main.c, line 150: Missing type specifier or type
qualifier. (missingtype)
socklen_t ai_addrlen;
--------^
make[1]: *** [main.o] Error 1
make[1]: Leaving directory `/dsk1/vic/qpopper/qpopper4.1a5/popper'
make: *** [popper_server] Error 2
This appears to be associated with 4.1a4 to 4.1a5 enhancements
associated with ipv6 support. Since Tru 5.1A supports ipv6 even
though it is not being used, I tried to configure with:
./configure --enable-specialauth --without-pam --enable-ipv6
but that made no difference. By defining INET6 in config.h, 4.1a5
will successfully compile and run.
Vic Summerour
At 09:57 AM 12/1/2007 -0800, Randall Gellens wrote:
At 5:17 PM -0600 11/30/07, J Bacher wrote:
Does qpopper no longer support Tru64 5.1 enhanced security?
It's been awhile since I've been asked to upgrade qpopper on
Tru64 and previous versions (at least up to 4.0.4) supported
enhanced security with the --enable-specialauth configuration option.
The --enable-specialauth option is still there, although ./configure
figures out if it is needed for many platforms. Are you having a
problem with Tru64?
--
Randall Gellens
Opinions are personal; facts are suspect; I speak for myself only
-------------- Randomly-selected tag: ---------------
When we remember we are all mad, the mysteries disappear and
life stands explained. --Mark Twain
