Date: 05 Oct 2002 11:45:30 -0400 From: Lowell Gilbert <freebsd-questions-local@be-well.no-ip.com> To: freebsd-questions@freebsd.org, ns@sundive.homeunix.net Subject: Re: failure installing procmail from ports Message-ID: <44elb451ph.fsf@be-well.ilk.org> In-Reply-To: <20021004080938.GM96239@sundive.homeunix.net> References: <20021004080938.GM96239@sundive.homeunix.net>
index | next in thread | previous in thread | raw e-mail
Nigel Soon <ns@sundive.homeunix.net> writes:
> Your system appears to not (correctly) support at least one of:
> const, volatile, function prototypes, and enum types. Future
> versions of procmail will probably require support for all of them,
> so you should either upgrade your compiler to one that's compliant
> with the ISO C standard (the standard's over 10 years old, for
> goodness sake), or send email to <bug@procmail.org> explaining why
> you need procmail to continue to support K&R C.
Procmail builds fine for me, and looking over the autoconf script, I
don't see any obvious way you could fail this particular check.
What do you get when you type 'cc -v'?
> /usr/include/string.h:54: warning: conflicting types for built-in function `memcmp'
Does that file use the ANSI definition? In -STABLE, it's:
int memcmp __P((const void *, const void *, size_t));
To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-questions" in the body of the message
help
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?44elb451ph.fsf>