Sorry for replying to my own mail. But I finally figured out
what was going wrong: the configure script looks at permission of the mail
spool (/var/mail in our case) in order to decide whether mutt needs to
run setgid mail or not. This procedure only works, if the machine on which
you compile mutt, is also the machine on which you run mutt. Which is
not the case here (I cannot compile/install mutt on the machine where it
is used, because on that machine those directories are not writable).
In our case that directory was neither world nor group writable. Thus,
configure decided that setting setgid mail wouldn't do any good. 

Anyway, the solution to this mess is to temporary make /var/mail
groupwritable on the machine where you compile. Then run

CC='gcc -R/usr/LOCAL/lib' ./configure --prefix=/usr/LOCAL --enable-pop --enable-imap 
--with-ssl=/usr/LOCAL/ssl --with-curses=/usr/LOCAL --with-mailpath=/var/mail 
--enable-external-dotlock

After that "make" runs without errors and "make install" will install the
mutt_dotlock program to do the mailbox locking.
After all that you can remove the group write permission on /var/mail
again.

It would be nice though to have something like a --setgid configure option
that would overwrite the default configure behaviour.

Cheers,
Martin

========================================================================
Martin Siegert
Academic Computing Services                        phone: (604) 291-4691
Simon Fraser University                            fax:   (604) 291-4242
Burnaby, British Columbia                          email: [EMAIL PROTECTED]
Canada  V5A 1S6
========================================================================

On Mon, Jul 08, 2002 at 07:03:14PM -0700, Martin Siegert wrote:
> Hi:
> 
> this is my first attempt to compile mutt, so please bear with me.
> I tried to compile mutt-1.4i under Solaris 2.6.
> Our mail spool has 1775 permissions:
> # ls -ld /var/mail
> drwxrwxr-t   6 root     mail      479232 Jul  8 18:48 /var/mail
> 
> I used the following configure command:
> 
> CC='gcc -R/usr/LOCAL/lib -DUSE_DOTLOCK -DDL_STANDALONE' ./configure 
>--prefix=/usr/LOCAL --enable-pop --enable-imap --with-ssl=/usr/LOCAL/ssl 
>--with-curses=/usr/LOCAL --with-mailpath=/var/mail
> 
> which proceeds without errors. When I run make, however, it fails with
> 
> gcc -R/usr/LOCAL/lib -DUSE_DOTLOCK -DDL_STANDALONE  -Wall -pedantic -g -O2 
>-L/usr/LOCAL/lib  -L/usr/LOCAL/ssl/lib -o mutt  patchlist.o addrbook.o alias.o 
>attach.o base64.o browser.o buffy.o color.o commands.o complete.o compose.o copy.o 
>curs_lib.o curs_main.o date.o edit.o enter.o flags.o init.o filter.o from.o 
>getdomain.o handler.o hash.o hdrline.o headers.o help.o hook.o keymap.o main.o mbox.o 
>menu.o mh.o mx.o pager.o parse.o pattern.o postpone.o query.o recvattach.o recvcmd.o 
>rfc822.o rfc1524.o rfc2047.o rfc2231.o score.o send.o sendlib.o signal.o sort.o 
>status.o system.o thread.o charset.o history.o lib.o muttlib.o editmsg.o utf8.o 
>mbyte.o wcwidth.o url.o ascii.o pgp.o pgpinvoke.o pgpkey.o pgplib.o gnupgparse.o 
>pgpmicalg.o pgppacket.o resize.o dotlock.o pop.o pop_lib.o pop_auth.o account.o 
>mutt_socket.o mutt_tunnel.o mutt_ssl.o md5c.o  -Limap -limap -lncurses -lssl -lcrypto 
>   ./intl/libintl.a   -lsocket -lnsl
> ld: fatal: symbol `main' is multiply defined:
>       (file main.o and file dotlock.o);
> ld: fatal: symbol `ReleaseDate' is multiply defined:
>       (file muttlib.o and file dotlock.o);
> ld: fatal: File processing errors. No output written to mutt
> collect2: ld returned 1 exit status
> make[2]: *** [mutt] Error 1
> make[2]: Leaving directory `/usr/LOCAL/src/mutt-1.4'
> make[1]: *** [all-recursive] Error 1
> make[1]: Leaving directory `/usr/LOCAL/src/mutt-1.4'
> make: *** [all-recursive-am] Error 2
> 
> What is wrong?
> [BTW: the same error occurs when I configure with
> 
> CC='gcc -R/usr/LOCAL/lib' ./configure --prefix=/usr/LOCAL --enable-pop --enable-imap 
>--with-ssl=/usr/LOCAL/ssl --with-curses=/usr/LOCAL --with-mailpath=/var/mail
> 
> then modify config.h to define USE_DOTLOCK and DL_STANDALONE and then run make.
> There does not seem to be a configure option set causes USE_DOTLOCK and
> DL_STANDALONE to be set, is there?]
> 
> Thanks for your help in advance.
> 
> Cheers,
> Martin
> 
> ========================================================================
> Martin Siegert
> Academic Computing Services                        phone: (604) 291-4691
> Simon Fraser University                            fax:   (604) 291-4242
> Burnaby, British Columbia                          email: [EMAIL PROTECTED]
> Canada  V5A 1S6
> ========================================================================

Reply via email to