[Mailman-Users] Configure options not known
minxmertzmomo at gmail.com
Wed Dec 21 22:02:59 EST 2016
On Fri, Dec 9, 2016 at 6:41 PM, Mark Sapiro <mark at msapiro.net> wrote:
> On 12/09/2016 02:27 PM, Matt Morgan wrote:
> > Thanks. --prefix is the standard, but there's nothing in /var apart from
> > mailman's crontab. What's an example of a file that I could 'locate' to
> > figure out what mailman is using instead of /var? Or is there another
> > way to determine what it is?
> Where are the archives/, data/, lists/, locks/, logs/, qfiles/ and
> spam/ directories. If they are in the same directory as the bin/, cron/,
> icons/, mail/, Mailman/, messages/, pythonlib/, scripts/ and tests/
> directories, then you don't need --with-var-prefix at all because it is
> the same as $prefix. If different, then the containing directory is what
> you need for --with-var-prefix.
> If the bin/, cron/, icons/, mail/, Mailman/, messages/, pythonlib/,
> scripts/ and tests/ directories are all in /usr/local/mailman, you don't
> need --prefix because that's the default.
> Finally, if the cgi-bin/ directory is in $prefix, you don't need
> --exec-prefix. Otherwise, --exec-prefix is the path that contains the
> cgi-bin/ directory.
(snipping a lot of that)
configure and make install seemed to work. I got a CGI error and corrected
it, just like you said would happen.
Unfortunately, local delivery is failing for all (as far as I can tell)
list addresses. What have I done? Any advice welcome.
More information about the Mailman-Users