pauls at utdallas.edu
Thu Sep 1 21:36:20 PDT 2005
--On Tuesday, August 30, 2005 8:08 AM -0400 Robert Fitzpatrick
<lists at webtent.net> wrote:
>> > Victor referred me to the archives after finding out I have linked
>> > Postfix with a broken GNU getopt(), but I have not been able to come up
>> > with the solution. My current getopt package is gengetopt-2.11, should
>> > I resort to an earlier version and re-compile Postfix?
>> Look at the definition of GETOPT in src/util/sys_defs.h, this expects the
>> GNU getopt on Linux, and the standard GETOPT on BSD and other systems.
>> Problems happen when you link with a GNU getopt on a non GNU libc (i.e.
>> Linux) system.
>> If you really must link Postfix with libraries that slurp-up GNU getopt,
>> "fix" the definition of GETOPT() in sys/util/sys_defs.h. Perhaps there
>> should be a CCARGS override for this...
> I'll have to say I have no idea what these guys are talking about on the
> Postfix list, it must be some port I've installed that has linked in a
> way they suggest. I have not done anything except install very common
> ports on this FreeBSD mail server with no special linking or compile
> options, etc. All ran smooth until the latest portupgrade of Postfix and
> other related packages - amavisd-new, SpamAssassin, etc. Can someone
> here perhaps suggest how I might track down this problem?
make rmconfig, then run install again - this time don't select SPF. That
should solve your problem. The problem isn't with gnu getopt. It's with
Paul Schmehl (pauls at utdallas.edu)
Adjunct Information Security Officer
University of Texas at Dallas
AVIEN Founding Member
More information about the freebsd-ports