Re: OT: Making Mutt: log files
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 John P Verel [EMAIL PROTECTED] wrote: Again, as I'm new to make, with the mutt source, if I make and install and find I need or want to uninstall what I just made and installed, how do I do that? Others have already presented their opinions and preferences on this case. Personally, I use 'stow' to keep track of manually installed software. IMHO, stow is pretty nice tool in this purpose. When I compile stuff, I always use '--prefix=/usr/local' with configure and 'prefix=/usr/local/stow/software with 'make install'. Then I get myself to /usr/local/stow and say: stow directory And it creates the appropriate symlinks. If I want to uninstall it, I simply say: stow -D directory And the symlinks are gone. This serves the purpose for me, at least. - -- Jussi Ekholm -- [EMAIL PROTECTED] -- http://erppimaa.ihku.org/ -BEGIN PGP SIGNATURE- Version: GnuPG v1.0.7 (GNU/Linux) iD8DBQE9E3QsAtEARxQQCB4RAvQyAJ0WOBuECFVtM7sCGzZRamBSNx9jXQCdFufJ U9Itb1P9BO2n+b/GbcG19VI= =Ca76 -END PGP SIGNATURE-
Re: OT: Making Mutt: log files
* On 2002.06.09, in 20020609113937.A15126@Verdi, * John P Verel [EMAIL PROTECTED] wrote: I'm getting set to do my first non-rpm install of mutt and therefore my first usage of make. Looking at Sven's Installation Examples, I see outputted logs showing the results of configure, make and make install. Am I correct to assuming that these are generated automatically? You can redirect commands individually, as people have shown. But to easily log the whole thing, I'd recommend script: shell-prompt$ script mutt.log Script started, file is mutt.log sh$ ./configure --whatever sh$ make sh$ make install sh$ exit shell-prompt$ ls mutt.log mutt.log Script starts a new shell. Anything on the stdout or stderr in that shell gets duplicated to the log file. You exit to terminate the log. -- -D.[EMAIL PROTECTED]NSITUniversity of Chicago
OT: Making Mutt: log files
I'm getting set to do my first non-rpm install of mutt and therefore my first usage of make. Looking at Sven's Installation Examples, I see outputted logs showing the results of configure, make and make install. Am I correct to assuming that these are generated automatically? TIA John
Re: OT: Making Mutt: log files
Hi, * John P Verel [EMAIL PROTECTED] [02-06-09 17:39]: Looking at Sven's Installation Examples, I see outputted logs showing the results of configure, make and make install. Am I correct to assuming that these are generated automatically? A config.log is done automatically, but to create make logs you have to redirect make's output. make 21 make.log Thorsten -- It has become appallingly obvious that our technology has exceeded our humanity. - Albert Einstein
Re: OT: Making Mutt: log files
Hi, * John P Verel [02-06-09 17:45:08 +0200] wrote: I'm getting set to do my first non-rpm install of mutt and therefore my first usage of make. Someday it was the first time for all of us. Looking at Sven's Installation Examples, I see outputted logs showing the results of configure, make and make install. Am I correct to assuming that these are generated automatically? Yes and no. What do you mean with automatically? Those tools involved produce that output automatically, yes. But to use them within a homepage, you have to catch them by hand: ./configure ... ./logfile 21 will display nothing but store everything in a logfile (you should consult your shell's manpage and search for I/O redirection). It's very usefull when asking other people for help since only the complete and exact error message shows the details necessary to find the root of the problem. HTH, Cheers, Rocco
Re: OT: Making Mutt: log files
On 06/09/02, 06:01:56PM +0200, Rocco Rutte wrote: Looking at Sven's Installation Examples, I see outputted logs showing the results of configure, make and make install. Am I correct to assuming that these are generated automatically? Yes and no. What do you mean with automatically? Those tools involved produce that output automatically, yes. But to use them within a homepage, you have to catch them by hand: ./configure ... ./logfile 21 will display nothing but store everything in a logfile (you should consult your shell's manpage and search for I/O redirection). So, would ./configure 21 | tee ./logfile_config (etc) capture the output and show it to me on standard output as well (using bash)? John
Re: OT: Making Mutt: log files
John -- ...and then John P Verel said... % % On 06/09/02, 06:01:56PM +0200, Rocco Rutte wrote: % ... % generated automatically? % % Yes and no. What do you mean with automatically? Those tools ... % So, would ./configure 21 | tee ./logfile_config (etc) capture the % output and show it to me on standard output as well (using bash)? Yep. You got it. % % John HTH HAND have fun with your make! Try a patch or two, too! :-) :-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! msg28779/pgp0.pgp Description: PGP signature
Re: OT: Making Mutt: log files
Again, as I'm new to make, with the mutt source, if I make and install and find I need or want to uninstall what I just made and installed, how do I do that? Thank you for your patience with these questions. John
Re: OT: Making Mutt: log files
John -- ...and then John P Verel said... % % Again, as I'm new to make, with the mutt source, if I make and install % and find I need or want to uninstall what I just made and installed, how % do I do that? I don't believe the mutt makefile has an uninstall option, but you could grep for it in Makefile* in the source directory. Better, though, if you're not sure is to run ./configure --prefix=/some/unique/dir ... so that mutt gets installed in that unique dir; you can then safely wipe that dir if you discover that you want to get rid of mutt for some reason. Another approach would be to create a TIMESTAMP.BEG file somewhere before you start your make, and then when you have run your make install create a TIMESTAMP.END file; you'll then pretty safely bracket the time when your mutt was built and you can run a gawdawful find / -newer /path/to/TIMESTAMP.BEG \! -newer /path/to/TIMESTAMP.END to see the files if you've forgotten which were under /etc and which under /usr/local/doc and whatnot. I highly recommend the --prefix approach, though. % % Thank you for your patience with these questions. We'll see how long we can hold out ;-) % % John HTH 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! msg28798/pgp0.pgp Description: PGP signature
