I am trying to install spamass-milter however when I emerge it spamass-milter fails. <snip> checking for mi_stop in -lmilter... no configure: error: Cannot find libmilter </snip> Reproducible: Always Steps to Reproduce: 1. emerge spamass-milter Actual Results: <snip> checking for mi_stop in -lmilter... no configure: error: Cannot find libmilter </snip> Expected Results: compiled spamass-milter ^[]1;^G^[]2;Started emerge on: Aug 03, 2004 08:05:42^G^[]1;^G^[]2; *** emerge spamass-milter^G^[]1;^G^[]2; >>> emerge (1 of 1) m ail-filter/spamass-milter-0.2.0 to /^G^[]1;^G^[]2; === (1 of 1) Cleaning (mail-filter/spamass-milter-0.2.0::/usr/portage/mail-fil ter/spamass-milter/spamass-milter-0.2.0.ebuild)^G^[]1;^G^[]2; === (1 of 1) Compiling/Merging (mail-filter/spamass-milter-0.2.0::/ usr/portage/mail-filter/spamass-milter/spamass-milter-0.2.0.ebuild)^G>>> Unpacking source... >>> Unpacking spamass-milter-0.2.0.tar.gz to /var/tmp/portage/spamass-milter-0.2.0/work >>> Source unpacked. configure: WARNING: If you wanted to set the --build type, don't use --host. If a cross compiler is detected then cross compile mode will be used. checking for a BSD-compatible install... /bin/install -c checking whether build environment is sane... yes checking for gawk... gawk checking whether make sets ${MAKE}... yes checking for i586-pc-linux-gnu-g++... g++ checking for C++ compiler default output... a.out checking whether the C++ compiler works... yes checking whether we are cross compiling... no checking for suffix of executables... checking for suffix of object files... o checking whether we are using the GNU C++ compiler... yes checking whether g++ accepts -g... yes checking for style of include used by make... GNU checking dependency style of g++... none checking for i586-pc-linux-gnu-gcc... gcc checking whether we are using the GNU C compiler... yes checking whether gcc accepts -g... yes checking dependency style of gcc... none checking for C compiler warning flags... -Wall checking how to run the C++ preprocessor... g++ -E configure: Scanning for include-file directories: checking /usr/include... checking /usr/local/include... no checking /sw/local/include... no checking /usr/gnu/include... no checking /opt/gnu/include... no checking /sw/gnu/include... no checking /sw/include... no checking /usr/freeware/include... no checking /usr/pkg/include... no checking /opt/sfw/include... no configure: Scanning for library directories: checking /usr/local/lib... yes checking /usr/local/lib32... no checking /usr/local/lib64... no checking /usr/local/lib/64... no checking /sw/local/lib... no checking /sw/local/lib32... no checking /sw/local/lib64... no checking /sw/local/lib/64... no checking /sw/lib... no checking /sw/lib32... no checking /sw/lib64... no checking /sw/lib/64... no checking /usr/gnu/lib... no checking /usr/gnu/lib32... no checking /usr/gnu/lib64... no checking /usr/gnu/lib/64... no checking /opt/gnu/lib... no checking /opt/gnu/lib32... no checking /opt/gnu/lib64... no checking /opt/gnu/lib/64... no checking /sw/gnu/lib... no checking /sw/gnu/lib32... no checking /sw/gnu/lib64... no checking /sw/gnu/lib/64... no checking /usr/freeware/lib... no checking /usr/freeware/lib32... no checking /usr/freeware/lib64... no checking /usr/freeware/lib/64... no checking /usr/pkg/lib... no checking /usr/pkg/lib32... no checking /usr/pkg/lib64... no checking /usr/pkg/lib/64... no checking /usr/pkg/lib64... no checking /usr/pkg/lib/64... no checking /opt/sfw/lib... no checking /opt/sfw/lib32... no checking /opt/sfw/lib64... no checking /opt/sfw/lib/64... no checking for spamc... /usr/bin/spamc checking for nroff... nroff checking for mdoc nroff macros... yes checking build system type... i586-pc-linux-gnu checking host system type... i586-pc-linux-gnu checking for the pthreads library -lpthreads... no checking whether pthreads work without any flags... no checking whether pthreads work with -Kthread... no checking whether pthreads work with -kthread... no checking for the pthreads library -llthread... no checking whether pthreads work with -pthread... yes checking for joinable pthread attribute... PTHREAD_CREATE_JOINABLE checking if more special flags are required for pthreads... no checking for cc_r... gcc checking for ANSI C header files... yes checking for sys/wait.h that is POSIX.1 compatible... yes checking for sys/types.h... yes checking for sys/stat.h... yes checking for stdlib.h... yes checking for string.h... yes checking for memory.h... yes checking for strings.h... yes checking for inttypes.h... yes checking for stdint.h... yes checking for unistd.h... yes checking fcntl.h usability... yes checking fcntl.h presence... yes checking for fcntl.h... yes checking syslog.h usability... yes checking syslog.h presence... yes checking for syslog.h... yes checking sys/select.h usability... yes checking sys/select.h presence... yes checking for sys/select.h... yes checking for gcc option to accept ANSI C... none needed checking for an ANSI C-conforming const... yes checking for pid_t... yes checking for size_t... yes checking if we must define _GNU_SOURCE... no checking poll.h usability... yes checking poll.h presence... yes checking for poll.h... yes checking if malloc debugging is wanted... no checking for vsyslog... yes checking for vasprintf... yes checking for vsnprintf... yes checking for library containing gethostbyname... none required checking for library containing connect... none required checking for library containing inet_aton... none required checking for strsep... yes checking whether strsep is declared... yes checking for mi_stop in -lmilter... no checking for library containing strlcpy... no checking for mi_stop in -lmilter... no configure: error: Cannot find libmilter !!! ERROR: mail-filter/spamass-milter-0.2.0 failed. !!! Function econf, Line 362, Exitcode 1 !!! econf failed Calculating dependencies ^H^H ...done! >>> emerge (1 of 1) mail-filter/spamass-milter-0.2.0 to / >>> md5 src_uri ;-) spamass-milter-0.2.0.tar.gz ^[]1;^G^[]2; *** terminating.^G^[]1;^G^[]2;xterm^G ~
Just a guess, did you compile sendmail with the milter USE flag?
As stated in that topic in the forums, recompiling sendmail with the milter USE flag fixes this problem. Closing this bug.
