Re: autoconf and mutt-1.3.14
Well, now I understand the directory structure of the mutt site a little better, so in the future I won't get lost again. But is there any documentation that would direct people to the "devel" directory instead of "snapshots"? The intended target audience for devel hangs out on mutt-dev ...
Re: autoconf and mutt-1.3.14
Lars Hecking [EMAIL PROTECTED] writes: Well, now I understand the directory structure of the mutt site a little better, so in the future I won't get lost again. But is there any documentation that would direct people to the "devel" directory instead of "snapshots"? The intended target audience for devel hangs out on mutt-dev ... ... and yet, people are discussing version 1.3.14i here within this mutt-users mailing list. But my question had to do with the mutt web site, not the mailing lists. I couldn't find any documentation on the web site describing where to go to find the mutt-1.3.14i.tar.gz tarball that I was referred to here, nor explaining differences between the contents of the tarballs in the "devel" and "snapshots" directories. The "downloads" link on the web site simply redirects the user to a list of FTP sites. -- Lloyd Zusman [EMAIL PROTECTED]
Re: autoconf and mutt-1.3.14
Lloyd Zusman muttered: I have recently downloaded the current unstable mutt release, version 1.3.14. It doesn't come with a `configure' script Mine does: tar tvfz mutt-1.3.14i.tar.gz | grep configure -rwxr-xr-x 1000/1000231190 2001-01-27 14:47:53 mutt-1.3.14/configure -rw-r--r-- 1000/1000 24602 2001-01-27 14:47:52 mutt-1.3.14/configure.in HTH, Michael -- "Linux: the operating system with a CLUE... Command Line User Environment". (seen in a posting in comp.software.testing) PGP-Key: http://www-stud.ims.uni-stuttgart.de/~tatgeml/public.key
Re: autoconf and mutt-1.3.14
On Sun, Feb 11, 2001 at 05:04:19PM +0100, Michael Tatge allegedly said: Mine does: tar tvfz mutt-1.3.14i.tar.gz | grep configure -rwxr-xr-x 1000/1000231190 2001-01-27 14:47:53 mutt-1.3.14/configure -rw-r--r-- 1000/1000 24602 2001-01-27 14:47:52 mutt-1.3.14/configure.in I had no problems either. Regards Brian -- Brian Galbraith [ Mutt 1.3.14i]| GnuPG 1.0.4d | SuSE Linux 7.0 ] Encrypted Mail Preferred NEW KEY from 7thJan 2001 http://seattle.keyserver.net:11371/pks/lookup?op=getsearch=0x98A102F3 Hushmail Secure Webmail: [EMAIL PROTECTED]
Re: autoconf and mutt-1.3.14
Michael Tatge writes: Lloyd Zusman muttered: I have recently downloaded the current unstable mutt release, version 1.3.14. It doesn't come with a `configure' script Mine does: Maybe he downloaded the cvs version? It does indeed not have a configure script, and one needs to run the included prepare script to generate all auto* files. If the generated configure script is broken, someone may have messed with autoconf on that box.
Re: autoconf and mutt-1.3.14
Michael Tatge [EMAIL PROTECTED] writes: Lloyd Zusman muttered: I have recently downloaded the current unstable mutt release, version 1.3.14. It doesn't come with a `configure' script Mine does: tar tvfz mutt-1.3.14i.tar.gz | grep configure -rwxr-xr-x 1000/1000231190 2001-01-27 14:47:53 mutt-1.3.14/configure -rw-r--r-- 1000/1000 24602 2001-01-27 14:47:52 mutt-1.3.14/configure.in However, for me ... tar -tzvf mutt-unstable-20010211.tar.gz | grep configure -rw-r--r-- roessler/roessler 24605 2001-01-31 03:01:12 mutt/configure.in No `configure', only `configure.in'. I retrieved mutt-1.3.14 as follows: (1) I went to http://www.mutt.org (2) I clicked on the "downloading" link. (3) I clicked on the "ftp://ftp.mutt.org/pub/mutt/" link. (4) I clicked on the "snapshots" link. (5) I clicked on the following link to download the tarball: ftp://ftp.mutt.org/pub/mutt/snapshots/mutt-unstable-20010211.tar.gz As you can see from my `tar' command above, no `configure' script exists in this tarball, only `configure.in'. This is why I was asking about the proper `autoconf' invocation for correctly generating a `configure' script from this `configure.in' file. Or instead of suggesting a proper `autoconf' invocation, does anyone know where I can find the `mutt-1.3.14i.tar.gz' tarball that you are referring to above? Thanks in advance. HTH, Well, I'm not sure how it could help me simply for you to tell me that your own tarball contains a `configure' script. Clearly, mine didn't. But thanks, anyway. -- Lloyd Zusman [EMAIL PROTECTED]
Re: autoconf and mutt-1.3.14
Lars Hecking [EMAIL PROTECTED] writes: Michael Tatge writes: Lloyd Zusman muttered: I have recently downloaded the current unstable mutt release, version 1.3.14. It doesn't come with a `configure' script Mine does: Maybe he downloaded the cvs version? It does indeed not have a configure script, and one needs to run the included prepare script to generate all auto* files. Aha! Yes, I ran the `prepare' script, and indeed it worked fine. Thank you very much. If the generated configure script is broken, someone may have messed with autoconf on that box. My `autoconf' is fine. But given what is done within the `prepare' script, it's clear that simply running `autoconf' alone isn't enough. The sequence that the `prepare' script performs is ... aclocal -I m4 autoheader cd m4 make -f Makefile.am.in automake -i autoconf ... etc. ... From this, it's clear that the first 5 steps have to run prior to `autoconf', in order for `autoconf' to work properly. This is what I was trying to find out in my initial message. But using `prepare' is even better. The `prepare' script is mentioned within the `INSTALL' file. However, I didn't initially run it, because this documentation states that `prepare' is used with a CVS retrieval, and I didn't get this source from CVS, but rather, I downloaded the following tarball: "mutt-unstable-20010211.tar.gz". Now I realize that this tarball probably contains the same data as what I would have gotten if I went directly to CVS, and therefore, I now see that the `prepare' script applies to this tarball, as well. Thanks again. -- Lloyd Zusman [EMAIL PROTECTED]
Re: autoconf and mutt-1.3.14
Now I realize that this tarball probably contains the same data as what I would have gotten if I went directly to CVS, and therefore, I now see that the `prepare' script applies to this tarball, as well. Correct. The tarball you downloaded is a daily (or nightly :) snapshot of the cvs. All release archives mutt-1.x.yi.tar.gz include the necessary files.
Re: autoconf and mutt-1.3.14
Lars Hecking [EMAIL PROTECTED] writes: Now I realize that this tarball probably contains the same data as what I would have gotten if I went directly to CVS, and therefore, I now see that the `prepare' script applies to this tarball, as well. Correct. The tarball you downloaded is a daily (or nightly :) snapshot of the cvs. All release archives mutt-1.x.yi.tar.gz include the necessary files. I was looking for mutt-1.3.14 in ftp://ftp.mutt.org/pub/mutt, but the highest release there was mutt-1.2.5i. This is what caused me to download the "unstable" release from the "snapshots" directory. But after going back to the FTP site and digging around, I now realize that I could have found version 1.3.14i in ftp://ft.mutt.org/pub/mutt/devel. Well, now I understand the directory structure of the mutt site a little better, so in the future I won't get lost again. But is there any documentation that would direct people to the "devel" directory instead of "snapshots"? But anyway, all's well that ends well. Thanks again to everyone. -- Lloyd Zusman [EMAIL PROTECTED]
Re: autoconf and mutt-1.3.14
Lloyd Zusman muttered: Michael Tatge [EMAIL PROTECTED] writes: Lloyd Zusman muttered: I have recently downloaded the current unstable mutt release, version 1.3.14. It doesn't come with a `configure' script Mine does: tar tvfz mutt-1.3.14i.tar.gz | grep configure ^^^ tar -tzvf mutt-unstable-20010211.tar.gz | grep configure ^ HTH, Well, I'm not sure how it could help me simply for you to tell me that your own tarball contains a `configure' script. Clearly, mine didn't. Since you allready solved this prob, my intension was to give you the 'correct' filename of the tarball that has a configure script. Michael -- Why use Windows, since there is a door? (By [EMAIL PROTECTED], Andre Fachat) PGP-Key: http://www-stud.ims.uni-stuttgart.de/~tatgeml/public.key
autoconf and mutt-1.3.14
I have recently downloaded the current unstable mutt release, version 1.3.14. It doesn't come with a `configure' script, so I ran the latest version of `autoconf' (version 2.13) to generate one. However, running the resulting `configure' file generates the following error: ./configure: syntax error near unexpected token `AM_CONFIG_HEADER(config.h)' ./configure: ./configure: line 584: `AM_CONFIG_HEADER(config.h)' Is there a special way to run `autoconf' for mutt-1.3.14? Thanks in advance. -- Lloyd Zusman [EMAIL PROTECTED]
