Re: Installing mutt 1.5.14 problem
=- Przemyslaw Gawronski wrote on Sun 18.Mar'07 at 8:30:50 +0100 -= I've compiled mutt 1.5.14 (--prefix=$HOME --with-imap) and that went with no problems. But I can't install it as a regular user but only as root :( If I configure it with --prefix=$HOME I would expect to be able to install it in my home directory or am I thinking wrong? It was discussed on mutt-dev (see its archives) to fix installation for certain conditions, maybe it applies to you, too, and just hasn't been implemented yet. Typically the problem is that mutt_dotlock needs chgrp mail + chmod sgid, which fails for non-root. After you configured, edit your Makefile and prepend ':' in front of those 2 cmds for mutt_dotlock. -- © Rado S. -- You must provide YOUR effort for your goal! EVERY effort counts: at least to show your attitude. You're responsible for ALL you do: you get what you give.
Re: Installing mutt 1.5.14 problem
Second thing to this install is a problem with doc's directory, after hitting F1 key I get this error: /doc/mutt/manual.txt: Nie ma takiego pliku ani katalogu The comment is in polish, that there is no such file or directory. Przemek -- AIKIDO TANREN DOJO - Poland - Warsaw - Mokotow - Ursynow - Natolin info: http://www.tanren.pl/ phone: +4850151 email: [EMAIL PROTECTED]
Re: Installing mutt 1.5.14 problem
On Sun, Mar 18, 2007 at 08:30:50AM +0100, Przemyslaw Gawronski wrote: Hi I've compiled mutt 1.5.14 (--prefix=$HOME --with-imap) and that went with no problems. But I can't install it as a regular user but only as root :( If I configure it with --prefix=$HOME I would expect to be able to install it in my home directory or am I thinking wrong? yes, but maybe you need to specify too the prefix for config. files or something similar. What is complaining make install about? -- Javier Rojas GPG Key ID: 0xA1C57061 pgpCylienp7XK.pgp Description: PGP signature
Re: Installing mutt 1.5.14 problem
yes, but maybe you need to specify too the prefix for config. files or something similar. What is complaining make install about? ./configure --prefix=$HOME/tmpmutt --enable-imap I get: cat instdoc.sh instdoc /bin/sh: instdoc: Brak dostępu I suspect it's trying to access /usr/local/doc but it should go to /home/gawron/tmpmutt (since the user name is gawron). Przemek -- AIKIDO TANREN DOJO - Poland - Warsaw - Mokotow - Ursynow - Natolin info: http://www.tanren.pl/ phone: +4850151 email: [EMAIL PROTECTED]
Re: Installing mutt 1.5.14 problem
On Sun, Mar 18, 2007 at 02:40:57PM +0100, Przemyslaw Gawronski wrote: yes, but maybe you need to specify too the prefix for config. files or something similar. What is complaining make install about? ./configure --prefix=$HOME/tmpmutt --enable-imap please have a look to the output of ./configure --help, and see what other prefix flags are around there. If there are some more, change them too to point to some place within your $HOME. I would check that, but... I can't open Mutt's main page. nmap says the 80 port of www.mutt.org isn't open. -- Javier Rojas GPG Key ID: 0xA1C57061 pgpLq1Y4WbnuI.pgp Description: PGP signature
Re: installing mutt from source - hints
* David Thorburn-Gundlach [EMAIL PROTECTED] [2002-05-29]: Fergit RPMs (though our RPM team is starting to build them now) and just build your own from source like a real man. Heck, surf over to http://mutt.justpickone.org/mutt-build-cocktail/ and see how a *real* mess of a mutt is made :-) http://mutt.justpickone.org/mutt-build-cocktail/mutt-1.4i.patched-05.tar 12.9MB? ohmygod.. Seriously, though, building the source from scratch is pretty simple if you keep it stock. exactly. and here's what I do to install mutt: http://www.math.fu-berlin.de/~guckes/mutt/install.html yes, pretty simple. :-) Sven -- Sven Guckes http://www.math.fu-berlin.de/~guckes/mutt/setup.html Mutt setup from scratch, Sven's sample setup; attribution, limit, list vs subscribe, histories, mailcap, POP, hooks, use of external pagers, troubleshooting, adding header lines, from Mozilla to Mutt.
Re: installing mutt from source - hints
Sven -- ...and then Sven Guckes said... % % * David Thorburn-Gundlach [EMAIL PROTECTED] [2002-05-29]: % Fergit RPMs (though our RPM team is starting to build them now) and % just build your own from source like a real man. Heck, surf over to %http://mutt.justpickone.org/mutt-build-cocktail/ % and see how a *real* mess of a mutt is made :-) % % http://mutt.justpickone.org/mutt-build-cocktail/mutt-1.4i.patched-05.tar % 12.9MB? ohmygod.. Now, be fair... That's a completely-patched source tree that hasn't been compressed; even the stock mutt tarball is nearly 9M when unzipped. With this version, I'll be compressing the tarballs that go into the Clean directory and I expect they'll be under 3M. % % Seriously, though, building the source from % scratch is pretty simple if you keep it stock. % % exactly. and here's what I do to install mutt: % http://www.math.fu-berlin.de/~guckes/mutt/install.html % yes, pretty simple. :-) My no-patch version looks about like that, except that I store all of the configure stuff in a separate script because I'm lazy. % % Sven % % -- % Sven Guckes http://www.math.fu-berlin.de/~guckes/mutt/setup.html % Mutt setup from scratch, Sven's sample setup; attribution, limit, list % vs subscribe, histories, mailcap, POP, hooks, use of external pagers, % troubleshooting, adding header lines, from Mozilla to Mutt. HAND :-D -- David T-G * It's easier to fight for one's principles (play) [EMAIL PROTECTED] * than to live up to them. -- fortune cookie (work) [EMAIL PROTECTED] http://www.justpickone.org/davidtg/Shpx gur Pbzzhavpngvbaf Qrprapl Npg! msg28393/pgp0.pgp Description: PGP signature
Re: Installing Mutt - Can't fix mutt_dotlock's permissions
Vincent Lefevre wrote: When installing Mutt in my home directory, I get the following error: [...] This is normal, but anyway, mutt_dotlock is already installed in /usr/bin. In fact, I just want to install the mutt binary. The problem is that Mutt has installed a mutt_dotlock with incorrect permissions in my home directory. They are incorrect only if your mails are delivered into /var/spool/mail/. mutt_dotlock will work perfectly if, for instance, procmail puts them directly somewhere where you have sufficient rights (~/Mail/). -- Cedric
Re: Installing Mutt 1.3.19
On Tue, 24 Jul 2001, Nelson D. Guerrero wrote: Hello everyone. I`ve been forced to downgrade from mutt 1.3.19 to mutt 1.2.5 since I installed Slackware 8.0, I keep getting the following error with ncurses: look at the config.log file, which shows the error messages. Perhaps sl80's got some additional library dependency for ncurses. -- T.E.Dickey [EMAIL PROTECTED] http://dickey.his.com ftp://dickey.his.com
Re: Installing Mutt 1.3.19
* On Tue Jul 24, Thomas E. Dickey wrote in [mutt-users]:
- On Tue, 24 Jul 2001, Nelson D. Guerrero wrote:
-
- Hello everyone.
-
- I`ve been forced to downgrade from mutt 1.3.19 to mutt 1.2.5 since I
- installed Slackware 8.0, I keep getting the following error with
- ncurses:
-
- look at the config.log file, which shows the error messages. Perhaps
- sl80's got some additional library dependency for ncurses.
-
- --
- T.E.Dickey [EMAIL PROTECTED]
- http://dickey.his.com
- ftp://dickey.his.com
-
I did`nt find anything in my config.log, but then again, I`m fairly
ignorant on these kind of things. I was wondering if someone could check
it out. Attached is the config.log, sorry if it bothers anybody, this is
the first and last time I attached an unrequested file.
---
Nelson D. Guerrero Email: [EMAIL PROTECTED]
Soporte TecnicoWWW : http://www.tcn.com.do
Telecable Nacional Tel : (809) 542 - 6612 ext. 4018
Divisiòn de Internet
This file contains any messages produced by compilers while
running configure, to aid debugging if configure makes a mistake.
It was created by configure, which was
generated by GNU Autoconf 2.50. Invocation command line was
$ ./configure --enable-locales-fix --without-wc-funcs --with-curses-dir=/usr/lib
## -- ##
## Platform. ##
## -- ##
hostname = guerro
uname -m = i686
uname -r = 2.4.5
uname -s = Linux
uname -v = #1 Tue Jul 17 15:51:22 AST 2001
/usr/bin/uname -p = unknown
/bin/uname -X = unknown
/bin/arch = i686
/usr/bin/arch -k = unknown
/usr/convex/getsysinfo = unknown
hostinfo = unknown
/bin/machine = unknown
/usr/bin/oslevel = unknown
/bin/universe = unknown
PATH = /usr/local/bin:/usr/bin:/bin:/usr/X11R6/bin:/usr/games:.:/opt/gnome/bin
## ##
## Core tests. ##
## ##
configure:960: PATH=.;.; conftest.sh
./configure: conftest.sh: command not found
configure:963: $? = 127
configure:1015: checking for a BSD compatible install
configure:1064: result: /usr/bin/ginstall -c
configure:1075: checking whether build environment is sane
configure:1118: result: yes
configure:1139: checking whether make sets ${MAKE}
configure:1159: result: yes
configure:1187: checking for working aclocal
configure:1194: result: found
configure:1202: checking for working autoconf
configure:1209: result: found
configure:1217: checking for working automake
configure:1224: result: found
configure:1232: checking for working autoheader
configure:1239: result: found
configure:1247: checking for working makeinfo
configure:1254: result: found
configure:1270: checking build system type
configure:1288: result: i686-pc-linux-gnu
configure:1295: checking host system type
configure:1309: result: i686-pc-linux-gnu
configure:1316: checking for prefix
configure:1323: result: /usr/local
configure:1369: checking for gcc
configure:1384: found /usr/bin/gcc
configure:1392: result: gcc
configure:1636: checking for C compiler default output
configure:1639: gccconftest.c 5
configure:1642: $? = 0
configure:1665: result: a.out
configure:1670: checking whether the C compiler works
configure:1676: ./a.out
configure:1679: $? = 0
configure:1694: result: yes
configure:1701: checking whether we are cross compiling
configure:1703: result: no
configure:1706: checking for executable suffix
configure:1708: gcc -o conftestconftest.c 5
configure:1711: $? = 0
configure:1733: result:
configure:1739: checking for object suffix
configure:1757: gcc -c conftest.c 5
configure:1760: $? = 0
configure:1779: result: o
configure:1783: checking whether we are using the GNU C compiler
configure:1804: gcc -c conftest.c 5
configure:1807: $? = 0
configure:1810: test -s conftest.o
configure:1813: $? = 0
configure:1825: result: yes
configure:1831: checking whether gcc accepts -g
configure:1849: gcc -c -g conftest.c 5
configure:1852: $? = 0
configure:1855: test -s conftest.o
configure:1858: $? = 0
configure:1868: result: yes
configure:1895: gcc -c -g -O2 conftest.c 5
conftest.c:2: parse error before `me'
configure:1898: $? = 1
configure: failed program was:
#ifndef __cplusplus
choke me
#endif
configure:1993: checking for strerror in -lcposix
configure:2020: gcc -o conftest -g -O2 conftest.c -lcposix 5
/usr/i386-slackware-linux/bin/ld: cannot find -lcposix
collect2: ld returned 1 exit status
configure:2023: $? = 1
configure: failed program was:
#line 2001 configure
#include confdefs.h
/* Override any gcc2 internal prototype to avoid an error. */
#ifdef __cplusplus
extern C
#endif
/* We use char because int might match the return type of a gcc2
builtin and then its argument prototype would still apply. */
char strerror ();
int
main ()
{
strerror ();
;
return 0;
}
configure:2040: result: no
configure:2046: checking for gcc option to accept ANSI C
configure:2105: gcc -c -g -O2
Re: Installing Mutt 1.3.19
I did`nt find anything in my config.log, but then again, I`m fairly ignorant on these kind of things. I was wondering if someone could check it out. Attached is the config.log, sorry if it bothers anybody, this is the first and last time I attached an unrequested file. It was created by configure, which was generated by GNU Autoconf 2.50. Invocation command line was Uninstall autoconf 2.50 and install autoconf-2.13. (Or install autoconf 2.13 in a location in your path that has precedence over the location of 2.50). Unpack a fresh copy of the mutt archive and run the included prepare script. You can specify the same cmd line options you would use with configure.
Re: Installing Mutt 1.3.19
* On Tue Jul 24, Lars Hecking wrote in [mutt-users]: - - I did`nt find anything in my config.log, but then again, I`m fairly - ignorant on these kind of things. I was wondering if someone could check - it out. Attached is the config.log, sorry if it bothers anybody, this is - the first and last time I attached an unrequested file. - - It was created by configure, which was - generated by GNU Autoconf 2.50. Invocation command line was - - Uninstall autoconf 2.50 and install autoconf-2.13. - - (Or install autoconf 2.13 in a location in your path that has precedence - over the location of 2.50). - - Unpack a fresh copy of the mutt archive and run the included prepare script. - You can specify the same cmd line options you would use with configure. - Lars, Thanks a lot, as you can see it worked: [nelsong:~]$ mutt -v Mutt 1.3.19i (2001-06-07) System: Linux 2.4.5 [using ncurses 5.2] Is that problem with autoconf 2.50 in general or just the one that`s shipping with slackware? --- Nelson D. Guerrero Email: [EMAIL PROTECTED] Soporte TecnicoWWW : http://www.tcn.com.do Telecable Nacional Tel : (809) 542 - 6612 ext. 4018 Divisiòn de Internet
Re: Installing Mutt 1.3.19
Thanks a lot, as you can see it worked: [nelsong:~]$ mutt -v Mutt 1.3.19i (2001-06-07) System: Linux 2.4.5 [using ncurses 5.2] Is that problem with autoconf 2.50 in general or just the one that`s shipping with slackware? autoconf 2.5x is not fully backwards compatible. I have not yet had the time to find out what exactly goes wrong, and whether it is possible to rewrite configure.in to work with both versions.
Re: installing mutt
On Sun, Jan 09, 2000 at 10:05:26AM -0800, --A. Santoyo-- wrote: hello I'm having trouble getting mutt to run. when I run the mutt command at the prompt I get an error that says /var/spool/mail/root is not a mail folder. what can I do about this. Any other tips to get a) Never, ever read mail as root. Are you insane? mutt used to have a MIME bug which could arbitrary commands to be executed. As root (in your case) -- all I can say is "rm -Rf /" :) Create an alias for mail to root: in /etc/aliases or /etc/mail/aliases: root: some_other_user_but_not_root and run "newaliases" afterwards. b) About that bit with the mail-folder: Can you read it with elm? with pine? with mail? -- Ralf Hildebrandt [EMAIL PROTECTED] www.stahl.bau.tu-bs.de/~hildeb There is no reason for any individual to have a computer in their home. --Ken Olson, President of DEC, World Future Society Convention, 1977
Re: installing mutt
On Sun, Jan 09, 2000 at 10:05:26AM -0800, --A. Santoyo-- wrote: hello I'm having trouble getting mutt to run. when I run the mutt command at the prompt I get an error that says /var/spool/mail/root is not a mail folder. what can I do about this. Any other tips to get this app going would be very usefull. This probably means that the file is not present (i.e. not yet created). You should probably send some mail to the relevant user (`root' in this; however I support the advice not to do anything as root when possible). Marius Gedminas -- To err is human, but to really foul things up requires a computer.
Re: installing mutt without root privilege
Sergei DUZHIN writes: Thanks a lot! Now it works - as you can see from my mail header. Sergei Man, please trim your replies next time. [227 quoted lines deleted]
Re: installing mutt without root privilege
Thanks a lot!
Now it works - as you can see from my mail header.
Sergei
On Tue, Oct 05, 1999 at 10:40:05AM +0530, Raju K V wrote:
hi,
Looks like these undefined variables and defined in libcurses.so.1. Try
removing -lncurses and replacing it with -lcurses in LIBS variable of
your makefile.
HTH,
Raju
On Tue, Oct 05, 1999 at 12:22:07PM +0900, Sergei Duzhin [[EMAIL PROTECTED]] wrote:
From [EMAIL PROTECTED] Mon Oct 4 19:42 JST 1999
can you send me the entire 'make install' output or that last 20 lines
or so?
Here it is:
Script started on Tue Oct 05 12:18:44 1999
pross85{duzhin}1: gmake install
Making install in doc
gmake[1]: Entering directory `/auto/stdfsv1-f1/home3/duzhin/tmp/mutt-1.0pre3/doc'
gmake html
gmake[2]: Entering directory `/auto/stdfsv1-f1/home3/duzhin/tmp/mutt-1.0pre3/doc'
sgml2html manual
gmake[2]: sgml2html: Command not found
gmake[2]: *** [manual.html] Error 127
gmake[2]: Leaving directory `/auto/stdfsv1-f1/home3/duzhin/tmp/mutt-1.0pre3/doc'
gmake[1]: [try-html] Error 2 (ignored)
gmake manual.txt
gmake[2]: Entering directory `/auto/stdfsv1-f1/home3/duzhin/tmp/mutt-1.0pre3/doc'
sgml2txt -c latin manual
gmake[2]: sgml2txt: Command not found
gmake[2]: *** [manual.txt] Error 127
gmake[2]: Leaving directory `/auto/stdfsv1-f1/home3/duzhin/tmp/mutt-1.0pre3/doc'
gmake[1]: [try-txt] Error 2 (ignored)
../mkinstalldirs /home/professor/duzhin/bin/man/man1
/usr/local/bin/install -c -m 644 mutt.man
/home/professor/duzhin/bin/man/man1/mutt.1
/usr/local/bin/install -c -m 644 dotlock.man
/home/professor/duzhin/bin/man/man1/mutt_dotlock.1
../mkinstalldirs /home/professor/duzhin/bin/doc/mutt
for f in manual.txt ; do /usr/local/bin/install -c -m 644 $f
/home/professor/duzhin/bin/doc/mutt ; done
for f in PGP-Notes.txt applying-patches.txt devel-notes.txt manual.txt ; do
/usr/local/bin/install -c -m 644 ./$f /home/professor/duzhin/bin/doc/mutt ; done
for f in COPYRIGHT GPL INSTALL ChangeLog README NEWS TODO README.SECURITY ; do
/usr/local/bin/install -c -m 644 ../$f /home/professor/duzhin/bin/doc/mutt ; done
if [ -f manual.html ] ; then \
gmake install-html ; \
fi
gmake[1]: Leaving directory `/auto/stdfsv1-f1/home3/duzhin/tmp/mutt-1.0pre3/doc'
Making install in intl
gmake[1]: Entering directory `/auto/stdfsv1-f1/home3/duzhin/tmp/mutt-1.0pre3/intl'
if test "mutt" = "gettext" \
test '' = 'intl-compat.o'; then \
if test -r ./mkinstalldirs; then \
./mkinstalldirs /home/professor/duzhin/bin/lib
/home/professor/duzhin/bin/include; \
else \
../mkinstalldirs /home/professor/duzhin/bin/lib
/home/professor/duzhin/bin/include; \
fi; \
/usr/local/bin/install -c -m 644 intlh.inst
/home/professor/duzhin/bin/include/libintl.h; \
/usr/local/bin/install -c -m 644 libintl.a
/home/professor/duzhin/bin/lib/libintl.a; \
else \
: ; \
fi
if test "mutt" = "gettext"; then \
if test -r ./mkinstalldirs; then \
./mkinstalldirs /home/professor/duzhin/bin/share/gettext/intl; \
else \
../mkinstalldirs /home/professor/duzhin/bin/share/gettext/intl; \
fi; \
/usr/local/bin/install -c -m 644 VERSION
/home/professor/duzhin/bin/share/gettext/intl/VERSION; \
dists="ChangeLog Makefile.in linux-msg.sed po2tbl.sed.in xopen-msg.sed gettext.h
gettextP.h hash-string.h libgettext.h loadinfo.h bindtextdom.c dcgettext.c dgettext.c
gettext.c finddomain.c loadmsgcat.c localealias.c textdomain.c l10nflist.c
explodename.c intl-compat.c cat-compat.c"; \
for file in $dists; do \
/usr/local/bin/install -c -m 644 ./$file
/home/professor/duzhin/bin/share/gettext/intl/$file; \
done; \
else \
: ; \
fi
gmake[1]: Leaving directory `/auto/stdfsv1-f1/home3/duzhin/tmp/mutt-1.0pre3/intl'
Making install in m4
gmake[1]: Entering directory `/auto/stdfsv1-f1/home3/duzhin/tmp/mutt-1.0pre3/m4'
gmake[2]: Entering directory `/auto/stdfsv1-f1/home3/duzhin/tmp/mutt-1.0pre3/m4'
gmake[2]: Nothing to be done for `install-exec-am'.
gmake[2]: Nothing to be done for `install-data-am'.
gmake[2]: Leaving directory `/auto/stdfsv1-f1/home3/duzhin/tmp/mutt-1.0pre3/m4'
gmake[1]: Leaving directory `/auto/stdfsv1-f1/home3/duzhin/tmp/mutt-1.0pre3/m4'
Making install in po
gmake[1]: Entering directory `/auto/stdfsv1-f1/home3/duzhin/tmp/mutt-1.0pre3/po'
PATH=../src:$PATH : --default-domain=mutt --directory=.. \
--add-comments --keyword=_ --keyword=N_ \
--files-from=./POTFILES.in \
test ! -f mutt.po \
|| ( rm -f ./mutt.pot \
mv mutt.po ./mutt.pot )
if test -r ".././mkinstalldirs"; then \
.././mkinstalldirs /home/professor/duzhin/bin/lib; \
else \
/bin/sh ../mkinstalldirs /home/professor/duzhin/bin/lib; \
fi
installing de.mo as /home/professor/duzhin/bin/lib/locale/de/LC_MESSAGES/mutt.mo
installing ru.mo as /home/professor/duzhin/bin/lib/locale/ru/LC_MESSAGES/mutt.mo
installing it.mo as
Re: installing mutt without root privilege
Quoth Don Blaheta [EMAIL PROTECTED]:
$ ./configure --prefix=/final/location
$ make
$ make DESTDIR=/temporary/location install
Way cool, this is **exactly** the sort of thing I was looking for. It
works pretty well, but the DESTDIR seems not to propagate low enough;
a whole bunch of stuff does get correctly installed into my temp
location, but eventually it tries to install mutt into /cs/bin.
Interesting. I just tried it myself and I didn't have this problem.
Are you perhaps using an old version of make? The last 3 lines of my
Makefile read:
# Tell versions [3.59,3.63) of GNU make to not export all variables.
# Otherwise a system limit (for SysV at least) may be exceeded.
.NOEXPORT:
(Those lines come from /usr/share/automake/footer.am and are inserted
by automake.)
You could try removing those lines, or try the following trivial
Makefile ("make VAR=bar") with and without .NOEXPORT, or try a newer
version of make, of course.
VAR = foo
outer:
@$(MAKE) inner
inner:
@echo VAR=$(VAR)
.NOEXPORT:
I did have a different problem installing as non-root, with this line
in the Makefile:
chgrp mail $(DESTDIR)$(bindir)/mutt_dotlock \
Anyway, fortunately I do have the root password for every machine I
use ...
Edmund
Re: installing mutt without root privilege
Ok, I've been having similar problems (I maintain the local copy of mutt, but don't have root; I need to use a special program "cscp" to copy files into the public hierarchy), so I configured with "--prefix=./subdir". When I make install, I get a bunch of errors: ^ I don't know whether this is in the autoconf manual, but you should never use a relative path for --prefix.
Re: installing mutt without root privilege
I think what you'll have to do is configure mutt with --prefix set to
the actual path you will eventually install to. Then, you'll have to
recreate the actions that 'make install' would have performed ('make -n
install' would probably be helpful here), using your 'cscp' program.
Telling a package's installation script to install stuff in a location
different from where it will eventually be installed is a standard
problem: all Debian packages are built this way, I think. So you
almost certainly don't have to study the output of make -n install and
do your own program. In the case of mutt, I think what you have to do
is something like:
$ ./configure --prefix=/final/location
$ make
$ make DESTDIR=/temporary/location install
This is from glancing at the Makefile; I haven't tried it. If it
doesn't work you could look at Debian's source package diff; the same
problem will have been solved there.
By the way, can anyone say if this use of DESTDIR is reasonably
standard? It would be nice of all/most packages had the same way of
doing this ...
Edmund
Re: installing mutt without root privilege
On Mon, Oct 04, 1999 at 03:57:46PM -0500, David DeSimone wrote:
I think what you'll have to do is configure mutt with --prefix set to
the actual path you will eventually install to. Then, you'll have to
recreate the actions that 'make install' would have performed ('make -n
install' would probably be helpful here), using your 'cscp' program.
What I've done is configured with --prefix set to the final install
path, as you said, done the 'make', then edited the Makefile and changed
the line
prefix = path to final installation
to
prefix = path to initial installation
Then I run 'make -n install' to see if I have to create any directories,
then run 'make install'.
This was actually for mswordview-0.5.14; I hadn't figured this out the
last time I installed mutt. I am assuming that the Makefile for mutt is
similarly structured.
--
Gary Johnson
Hewlett-Packard Company
Spokane, Washington
[EMAIL PROTECTED]
Re: installing mutt without root privilege
On Thu, Oct 07, 1999 at 09:35:55AM +0100, Edmund GRIMLEY EVANS wrote: $ ./configure --prefix=/final/location $ make $ make DESTDIR=/temporary/location install The DESTDIR support isn't set up for the contrib directory yet, so the stuff that gets installed out of there normally will fail. By the way, can anyone say if this use of DESTDIR is reasonably standard? It's not universal, but it's pretty common. -- Manoj Kasichainula - manojk at io dot com - http://www.io.com/~manojk/ "Some people have entirely too much free time on their hands." - Gene Spafford (spaf)
Re: installing mutt without root privilege
Quoth Edmund GRIMLEY EVANS: In the case of mutt, I think what you have to do is something like: $ ./configure --prefix=/final/location $ make $ make DESTDIR=/temporary/location install Way cool, this is **exactly** the sort of thing I was looking for. It works pretty well, but the DESTDIR seems not to propagate low enough; a whole bunch of stuff does get correctly installed into my temp location, but eventually it tries to install mutt into /cs/bin. It's the install-binPROGRAMS that is trying to install it, and it does include the DESTDIR variable, so I'm guessing that make doesn't propagate its variables into recursive calls of itself. I fixed the problem by changing the Makefile target install-am to be install-am: all-am @$(MAKE) $(AM_MAKEFLAGS) DESTDIR=$(DESTDIR) \ ^^ install-exec-am install-data-am and adding a DESTDIR=$(DESTDIR) inside the recursive call in the all-recursive (etc) target as follows: all-recursive install-data-recursive install-exec-recursive \ installdirs-recursive install-recursive uninstall-recursive \ check-recursive installcheck-recursive info-recursive dvi-recursive: [...] if test "$$dot_seen" = "no"; then \ $(MAKE) $(AM_MAKEFLAGS) DESTDIR=$(DESTDIR) "$$target-am" || exit 1; \ ^^ fi; test -z "$$fail" With those fixes, the install seems to have proceeded correctly. The same fixes can be applied to Makefile.in (with similar success), but I have no idea where to put them in Makefile.am to make it work Anyway, this seems to have highlighted my main problem, which is that in the makefile in the po/ subdirectory, we have localedir = $(datadir)/locale gnulocaledir = $(prefix)/share/locale The former will resolve to /cs/share/mutt/locale, which is correct (since I have control over the /cs/share/mutt tree), but the second resolves to /cs/share/locale, which I _don't_ have control over. How can I tell mutt to use $(localedir) instead of $(gnulocaledir)? Ok, I can analyse this a little further. It picks $(gnulocaledir) because the CATALOGS list uses the .gmo suffix instead of the .mo suffix. (But then installs the .mo file into that directory.) This, in turn, appears to be because $CATOBJEXT is ".gmo" in the configure file. Why? I dunno But I do know that it's not possible for me to install stuff into /cs/share/locale, and I'm not sure how to tell that to configure. (Check that---it's _possible_, I think, but I'd have to jump through a bunch of hoops with our sysadmin. Is it really worth it?) Once again, I'm on an Ultra10 running Solaris 2.7; my config line is now: configure --enable-pop --enable-buffy-size --with-included-gettext \ --prefix="/cs" --datadir="/cs/share/mutt" \ --sysconfdir="/cs/share/mutt" --with-docdir="/cs/share/mutt/doc" -- -=-Don [EMAIL PROTECTED]=-=-http://www.cs.brown.edu/~dpb/-=- The mome rath isn't born that could outgrabe me. -- Nicol Williamson
Re: installing mutt without root privilege
Quoth Andreas Kahari: In [EMAIL PROTECTED] Mikko Hänninen writes: But you probably didn't have a directory called doc under ./subdir, did you? In that case I think that configure falls back into the default, /usr/local/doc, regardless of whether that exists or not. I didn't, but creating it didn't affect things. I guess the path in "--prefix=path" has to be absolute, not relative. I used "--prefix=/home/andreas/stow", and docs and bins and everything got installed under my "stow" directory in my home directory. No problems. That didn't help either. make install still wants to be installing stuff to /usr/local/doc/mutt . -- -=-Don [EMAIL PROTECTED]=-=-http://www.cs.brown.edu/~dpb/-=- Few women admit their age. Few men act it.
Re: installing mutt without root privilege
Quoth David DeSimone:
Don Blaheta [EMAIL PROTECTED] wrote:
Ok, I've been having similar problems (I maintain the local copy of
mutt, but don't have root; I need to use a special program "cscp" to
copy files into the public hierarchy), so I configured with
"--prefix=./subdir".
The problem you'll run into here is that Mutt gets built in a directory,
then when it's moved to the installed directory by your 'cscp' program,
it will continue looking for support files from the origina directory
where you configured it.
Aha. Should've realised that. *d'oh*
I think what you'll have to do is configure mutt with --prefix set to
the actual path you will eventually install to. Then, you'll have to
recreate the actions that 'make install' would have performed ('make -n
install' would probably be helpful here), using your 'cscp' program.
Ok. So I configured it how I wanted it, then I made all the little
incantations that make install asked for, but I *still* can't get
foreign language support working (let's not even get started on
alternate charsets). Correct me if I'm wrong, but I should be able to
type
setenv LANG fr
./mutt
and have mutt give most/all messages to me in French, yes? I guess my
question just boils down to, is there a list somewhere of
* what files mutt needs
* where it needs them
* how it finds them -- this seems to be the tricky one
For example, I have installed all the .mo files in
/cs/share/mutt/locale/$lang/LC_MESSAGES/ ; and I recompiled the intl
code with -DLOCALEDIR="/cs/share/locale", and made sure that mutt was
linked with that version of the intl library... what more do I need to
do?
--
-=-Don [EMAIL PROTECTED]=-=-http://www.cs.brown.edu/~dpb/-=-
Warp 7 -- It's a law we can live with.
Re: installing mutt without root privilege
Hi, Sergei Duzhin! Sometime (on Monday, October 4 at 13:01) I've received something... I have installed mutt a couple of times on Linux systems, as a root, and had no problems whatever. Now I want to install it on a Sparcstation, where I am an ordinary user. The usual installation procedure does not succeed because of write permissions to various catalogs. Mutt's installation guide does not say anything about the possibility of installing mutt without root privileges. Question: is this possible and, if yes, what changes should I make in the Makefile? You have not change any Makefile. Just try ./configure --prefix=$HOME It will help. :) WBR, Andrej.
Re: installing mutt without root privilege
hi, I think all that is required is to run configure --prefix=/path/to/install/mutt and run 'make install'. If you still have problems like 'mail folder is read-only' comment out 'define USE_DOTLOCK 1' in config.h after running configure. Then run 'make install'. HTH, Raju On Mon, Oct 04, 1999 at 06:58:29PM +0900, Sergei Duzhin [[EMAIL PROTECTED]] wrote: I have installed mutt a couple of times on Linux systems, as a root, and had no problems whatever. Now I want to install it on a Sparcstation, where I am an ordinary user. The usual installation procedure does not succeed because of write permissions to various catalogs. Mutt's installation guide does not say anything about the possibility of installing mutt without root privileges. Question: is this possible and, if yes, what changes should I make in the Makefile? Sergei Duzhin, The University of Aizu
Re: installing mutt without root privilege
Thus spake Raju K V ([EMAIL PROTECTED]): I think all that is required is to run configure --prefix=/path/to/install/mutt and run 'make install'. If you still have problems like 'mail folder is read-only' comment out 'define USE_DOTLOCK 1' in config.h after running configure. Then run 'make install'. Another thing to add, if the mail spool dir is not world writable. Ideally the mail spool dir should be group writable my mail, or some other similar uid to avoid other problems. Hence the use of the sgid mutt_dotlock. If the machine has the group writable method, you can easily get around that by using a procmail filter to spool your mail to a file in your $HOME. For example $HOME/mail/in or whatever you would prefer, then you'll want to change your .muttrc and $MAIL environment variable to reflect that change. Then dotlocking that will not be an issue. -- , | . OpenPGP Supported . ' , oneiros ([EMAIL PROTECTED]) | .. the fortune for this e-mail is ..' , | Quark! Quark! Beware the quantum duck! '
Re: installing mutt without root privilege
Quoth Andreas Kahari: In [EMAIL PROTECTED] Sergei Duzhin writes: [cut] Question: is this possible and, if yes, what changes should I make in the Makefile? Sergei Duzhin, The University of Aizu Yes. None. Run 'configure' with the option "--prefix=/path/to/local/install/dir" (and all other options that you want to have enabled/disabled, see "./configure -h"). After that, do "make" and "make install". "/path/to/local/install/dir" should be the path to a directory on your account. Ok, I've been having similar problems (I maintain the local copy of mutt, but don't have root; I need to use a special program "cscp" to copy files into the public hierarchy), so I configured with "--prefix=./subdir". When I make install, I get a bunch of errors: [...] ../mkinstalldirs ./subdir/man/man1 mkdir ./subdir mkdir ./subdir/man mkdir ./subdir/man/man1 /cs/bin/ginstall -c -m 644 mutt.man ./subdir/man/man1/mutt.1 /cs/bin/ginstall -c -m 644 dotlock.man ./subdir/man/man1/mutt_dotlock.1 ../mkinstalldirs /usr/local/doc/mutt mkdir /usr/local/doc mkdir: Failed to make directory "/usr/local/doc"; Permission denied mkdir /usr/local/doc/mutt mkdir: Failed to make directory "/usr/local/doc/mutt"; No such file or directory *** Error code 2 make: Fatal error: Command failed for target `install' Current working directory /godzilla/cs0/mutt/mutt-1.0pre3/doc *** Error code 1 make: Fatal error: Command failed for target `install-recursive' It starts off nice, dealing with ./subdir/man, but then decides it needs access to /usr/local/doc/mutt, which I don't have. I'd fix this in the configure script, but autoconf is still a mysterious black box to me. To be honest, the main thing I'm looking to do here is figure out how to tell it where the po files are, which apparently is done during a (successful) make install. Ah, and system info: I'm on Solaris 2.7 running on an Ultra 10; I'm using whatever the local version of 'make' is, but gmake gives essentially the same error (can't create /usr/local/doc). And for the record, my configure line was: configure --enable-pop --enable-buffy-size --with-sharedir="/cs/share/mutt" --with-included-gettext --prefix="./subdir" -- -=-Don [EMAIL PROTECTED]=-=-http://www.cs.brown.edu/~dpb/-=- "640K ought to be enough for anybody." --Bill Gates, 1981
Re: installing mutt without root privilege
Don Blaheta [EMAIL PROTECTED] wrote on Mon, 04 Oct 1999: It starts off nice, dealing with ./subdir/man, but then decides it needs access to /usr/local/doc/mutt, which I don't have. I'd fix this in the configure script, but autoconf is still a mysterious black box to me. There's an option which isn't listed in "configure --help", --with-docdir. Setting this will probably solve these errors. Also worth checking is what is printed after "checking where to put the documentation" during configure. (Quickly looking at the configure script, it looks like it should be using prefix for docdir too... Strange.) Mikko -- // Mikko Hänninen, aka. Wizzu // [EMAIL PROTECTED] // http://www.iki.fi/wiz/ // The Corrs list maintainer // net.freak // DALnet IRC operator / // Interests: roleplaying, Linux, the Net, fantasy scifi, the Corrs / Never forget: 2 + 2 = 5 for extremely large values of 2.
Re: installing mutt without root privilege
On 991004, at 14:29:52, Don Blaheta wrote: It starts off nice, dealing with ./subdir/man, but then decides it needs access to /usr/local/doc/mutt, which I don't have. I'd fix this in the configure script, but autoconf is still a mysterious black box to me. If configure finds prefix/doc (and maybe prefix/doc/mutt), it puts the documentation there. -- David Ellement [EMAIL PROTECTED]
Re: installing mutt without root privilege
Quoth David Ellement: On 991004, at 14:29:52, Don Blaheta wrote: It starts off nice, dealing with ./subdir/man, but then decides it needs access to /usr/local/doc/mutt, which I don't have. I'd fix this in the configure script, but autoconf is still a mysterious black box to me. If configure finds prefix/doc (and maybe prefix/doc/mutt), it puts the documentation there. First of all, I had set prefix to "./subdir". Second, /usr/local/doc does not exist on our system. -- -=-Don [EMAIL PROTECTED]=-=-http://www.cs.brown.edu/~dpb/-=- An age is called Dark not because the light fails to shine, but because people refuse to see it.-- James Michener, "Space"
Re: installing mutt without root privilege
Don Blaheta [EMAIL PROTECTED] wrote on Mon, 04 Oct 1999: If configure finds prefix/doc (and maybe prefix/doc/mutt), it puts the documentation there. First of all, I had set prefix to "./subdir". Second, /usr/local/doc does not exist on our system. But you probably didn't have a directory called doc under ./subdir, did you? In that case I think that configure falls back into the default, /usr/local/doc, regardless of whether that exists or not. Just guessing... Mikko -- // Mikko Hänninen, aka. Wizzu // [EMAIL PROTECTED] // http://www.iki.fi/wiz/ // The Corrs list maintainer // net.freak // DALnet IRC operator / // Interests: roleplaying, Linux, the Net, fantasy scifi, the Corrs / Mathematician, n: A machine for converting coffee into formulas.
