[bug-mailutils] Re: Compiling mailutils 2.0 on solaris

[Maarten Thibaut]

Hi,

It seems that this error was already fixed in CVS for version 1.2, but
it has cropped up again in 2.0. Regression bug?

Also, when compiling the latest 2.0.90-20090410 I get this error:

/bin/bash ../libtool --tag=CC   --mode=compile gcc -DHAVE_CONFIG_H -I.
-I.. -I. -I../include -I../lib -I../lib -I.. -I../include -I../mailbox
-I../libmu_argp -I../libmu_cfg   -DSYSCONFDIR=\"/var/tmp/mailutils/etc\"
-DSITE_VIRTUAL_PWDDIR=\"/var/tmp/mailutils/etc/domain\"
-DSITE_CRAM_MD5_PWD=\"/var/tmp/mailutils/etc/cram-md5.pwd\" -g -O2 -MT
pam.lo -MD -MP -MF .deps/pam.Tpo -c -o pam.lo pam.c
libtool: compile:  gcc -DHAVE_CONFIG_H -I. -I.. -I. -I../include
-I../lib -I../lib -I.. -I../include -I../mailbox -I../libmu_argp
-I../libmu_cfg -DSYSCONFDIR=\"/var/tmp/mailutils/etc\"
-DSITE_VIRTUAL_PWDDIR=\"/var/tmp/mailutils/etc/domain\"
-DSITE_CRAM_MD5_PWD=\"/var/tmp/mailutils/etc/cram-md5.pwd\" -g -O2 -MT
pam.lo -MD -MP -MF .deps/pam.Tpo -c pam.c  -fPIC -DPIC -o .libs/pam.o
pam.c: In function `mu_pam_conv':
pam.c:97: error: `PAM_AUTHTOK_RECOVER_ERR' undeclared (first use in this
function)
pam.c:97: error: (Each undeclared identifier is reported only once
pam.c:97: error: for each function it appears in.)

These kinds of problems are usually quite rare on GNU software. What is
the stability and code quality of this project? We are mainly interested
in maidag as a procmail replacement because of its LMTP capability.

--
maarten


On 6/22/09 11:49 PM, Maarten Thibaut wrote:
> Hi,
>
> I'm getting this error when compiling mailutils 2.0 on Solaris 10:
>
> libtool: link: gcc -g -O2 -o .libs/aclck aclck.o 
> ../lib/.libs/libmuaux.a ../mailbox/.libs/libmailutils.so -lsocket -lnsl
> -lcrypt -lresolv -lpthread -R/var/tmp/mailutils/lib
> Undefined                       first referenced
>  symbol                             in file
> asprintf                            ../mailbox/.libs/libmailutils.so
> ld: fatal: Symbol referencing errors. No output written to .libs/aclck
>
> Is this a known error, and what is the fix?
>
> thanks!
> maarten
>