Re: another silly question
On Thu, Apr 21, 2005 at 22:04:31 -0400, Derek Martin wrote:
> Are there any possibilities for building mutt withouth dotlock
> support? I don't have root access so make install bombs trying to
> change mutt_dotlock's permissions...
I think both myself and RedHat/Fedora have had problems with this. If I
disable dotlock, I think I recall mutt tries to be setgid mail. Which
doesn't work if I have no priviliges.
RedHat/Fedora have a patch for this which removes part of
configure/configure.in by brute force. It's not a general
recommendation, but it works for this situation. I'm attaching a recent
version (modified by me) which changes only configure.in. Let me know
if it works for you. ;-)
Moritz
diff -U1 -rN mutt-1.5.8/PATCHES mutt-1.5.8-nosetgid/PATCHES
--- mutt-1.5.8/PATCHES 2005-02-12 21:55:51.000000000 +0100
+++ mutt-1.5.8-nosetgid/PATCHES 2005-02-14 09:55:04.000000000 +0100
@@ -0,0 +1 @@
+1.5.8-nosetgid.configure_in-1mb
diff -U1 -rN mutt-1.5.8/configure.in mutt-1.5.8-nosetgid/configure.in
--- mutt-1.5.8/configure.in 2005-02-12 21:57:16.000000000 +0100
+++ mutt-1.5.8-nosetgid/configure.in 2005-02-14 09:54:18.000000000 +0100
@@ -425,21 +425,2 @@
AC_DEFINE(USE_DOTLOCK,1,[ Define to use dotlocking for
mailboxes. ])
- else
-
- AC_CACHE_CHECK(if $mutt_cv_mailpath is group writable,
mutt_cv_groupwrite, [AC_TRY_RUN([#include <sys/types.h>
-#include <sys/stat.h>
-
-int main (int argc, char **argv)
-{
- struct stat s;
-
- stat ("$mutt_cv_mailpath", &s);
- if (s.st_mode & S_IWGRP) exit (0);
- exit (1);
-}], mutt_cv_groupwrite=yes, mutt_cv_groupwrite=no, mutt_cv_groupwrite=no)])
-
- if test $mutt_cv_groupwrite = yes; then
- AC_DEFINE(USE_DOTLOCK,1,[ Define to use dotlocking for
mailboxes. ])
- AC_DEFINE(USE_SETGID,1,[ Define if mutt should run
setgid "mail". ])
- mutt_cv_setgid=yes
- fi
fi