Peter Dyballa wrote:
Am 15.09.2006 um 00:30 schrieb ken:
It was ''installed'' under that user's $HOME directory. Does that explain whatever made you think that it's not installed?
No. I would like to read that you ./configure'd accordingly and did a 'make install'. You instead mentioned editing Makefile.in files – this is *not* the proper way.
Editing the Makefile used to be the proper way, the proper first step. At that time there was no ./configure script. And some apps still today are distributed as tarballs which have no ./configure script; you just edit the Makefile and run make. After unpacking mew, I browsed through several files, including 00readme, Makefile.in, and several others. Then I made backup copies of configure.in and Makefile.in, something a previous disaster taught me to do. While reading through Makefile.in, before my second cup of coffee, I ran across the lines: # ## EDIT THE FOLLOWINGS ## prefix=@prefix@ exec_prefix=@exec_prefix@ libdir=@libdir@ datadir=@datadir@ infodir=@infodir@ and, recognizing these as standard values I'd probably need to do the install, immediately shot off an email asking about the values for these (in the Makefile, not this Makefile.in). Please note that all the above occurred in preparation to installing *mew*, and *not emacs*. And to be perfectly clear, I haven't done anything with mew so far aside from untarring it and reading some files. As for the emacs install: When I installed this CVS version of emacs several weeks ago, I consulted the INSTALL.CVS and followed those as best as the ambiguous instructions there would allow. So to address your statement above, "I would like to read that you ./configure'd accordingly and did a 'make install'", I can only reply that (1) I don't recall all the exact commands I used anymore, (2) the instructions in INSTALL.CVS aren't/weren't clear enough for me to know then or now whether I ran all the commands correctly for this particular situation, but (3) yes, I did run ./configure (that much of the instructions was unambiguous).
I don't know mew, but it probably also has its own configure script, which can name what it needs. If mew's tarball does not bring all explanations you need to install for private use, you should start with giving mew's configure some of the Emacs configure options, particularly --prefix=... From this "top level value" almost everything is expanded/derived.
BTW, when I launch GNU Emacs as ./src/emacs or ./emacs from the src directory, it does not show our local and German calendar. Check whether you also see Chinese, Islamic, Jewish, Baha'i holidays ... (I presume you switched them off.)
They were off by default, so I had to turn them on. But, yes, I get Islamic, Mayan, Coptic, Julian, and a lot of other entries. So, given everything working that was mentioned in my previous email, given that calendar/diary is working, and despite the fact that I'm running the executable from the source directory, it would seem that I've gotten this single-user emacs from CVS installed correctly. Hmm. Now I wish I would have taken notes on how I did that install. I could have provided those to you. Frankly, because I didn't understand clearly the INSTALL.CVS, I didn't think the install would go correctly, so I didn't bother. Too bad. Thanks for your concerns.
-- Greetings
Pete
Some day we may discover how to make magnets that can point in any direction.
-- One is not superior merely because one sees the world as odious. -- Chateaubriand (1768-1848)