> > I have checked in all the latest into CVS and am going to start the > > test suite again. if all goes well I will probably release this as > > beta 10. > > > > anyway, try it out and let me know if anything bad happens! it > > should be a short jump from beta 10 to 1.0. > > I've just checked out the latest from scratch. There is no configure > script (as there never has been). Running autoconf creates one. > However, > it doesn't work under FreeBSD 4.3-S, because of a syntax error in the > script at this point: > > AM_INIT_AUTOMAKE(flac, 0.9) > > I've never had to run autoconf manually before so I'm not really surewhat> I'm doing. >hmm... not sure what the syntax error is; did you run aclocal first? but it does remind me to update the version number. Josh __________________________________________________ Do You Yahoo!? Yahoo! Auctions - buy the things you want at great prices http://auctions.yahoo.com/
> > > AM_INIT_AUTOMAKE(flac, 0.9) > > > > > > I've never had to run autoconf manually before so I'm not really > sure > > what > > > I'm doing. > > > > > hmm... not sure what the syntax error is; did you run aclocal > first? > > No. Had no idea I had to. I've gleaned from someone else's message > that I > should be doing something like: > > $ aclocal && autoconf && automake -c -a -i > aclocal: configure.in: 45: macro `AM_PATH_XMMS' not found in library > > As you can see that still gives me an error though? Any ideas? This > is > FreeBSD 4.3-STABLE.my hunch is that your version of either automake or possibly autoconf is not recent enough. but I should have a release out tonight or tomorrow if you can't upgrade right now. Josh __________________________________________________ Do You Yahoo!? Get personalized email addresses from Yahoo! Mail - only $35 a year! http://personal.mail.yahoo.com/
On Tue, 29 May 2001, Josh Coalson wrote:> > AM_INIT_AUTOMAKE(flac, 0.9) > > > > I've never had to run autoconf manually before so I'm not really sure > what > > I'm doing. > > > hmm... not sure what the syntax error is; did you run aclocal first?No. Had no idea I had to. I've gleaned from someone else's message that I should be doing something like: $ aclocal && autoconf && automake -c -a -i aclocal: configure.in: 45: macro `AM_PATH_XMMS' not found in library As you can see that still gives me an error though? Any ideas? This is FreeBSD 4.3-STABLE. Cheers.> but it does remind me to update the version number. > > Josh > > > __________________________________________________ > Do You Yahoo!? > Yahoo! Auctions - buy the things you want at great prices > http://auctions.yahoo.com/ > > _______________________________________________ > Flac-dev mailing list > Flac-dev@lists.sourceforge.net > http://lists.sourceforge.net/lists/listinfo/flac-dev >Mark Powell - UNIX System Administrator - The University of Salford Academic Information Services, Clifford Whitworth Building, Salford University, Manchester, M5 4WT, UK. Tel: +44 161 295 5936 Fax: +44 161 295 5888 www.pgp.com for PGP key
On Tue, May 29, 2001 at 11:42:27AM -0700, Josh Coalson wrote:> > AM_INIT_AUTOMAKE(flac, 0.9) > > > > I've never had to run autoconf manually before so I'm not really sure > what > > I'm doing. > > > hmm... not sure what the syntax error is; did you run aclocal first? but it > does remind me to update the version number.Creating the distribution with 'make dist' will use the version number from configure.in, which makes it hard to create a new release without remembering to update it. I noticed the following in include/FLAC/format.h: /* VERSION should come from configure */ #ifdef VERSION #define FLAC__VERSION_STRING VERSION #else #define FLAC__VERSION_STRING "0.10" #endif Is there any circumstance where you would want to support building without VERSION defined? Supplying a default leaves you vulnerable to some subtle bugs; for example, if/when a config.h is used instead of -Dvar=val, forgetting to include config.h would cause the default value to be used instead. If you change this code, then configure.in could be a single place to change the version number. -- - mdz
> I noticed the following in include/FLAC/format.h: > > /* VERSION should come from configure */ > #ifdef VERSION > #define FLAC__VERSION_STRING VERSION > #else > #define FLAC__VERSION_STRING "0.10" > #endif > > Is there any circumstance where you would want to support building > without > VERSION defined? Supplying a default leaves you vulnerable to some > subtle > bugs; for example, if/when a config.h is used instead of -Dvar=val, > forgetting > to include config.h would cause the default value to be used instead. > If you > change this code, then configure.in could be a single place to change > the > version number. >good you noticed this. it is actually a relic from the Makefile.lite make system that I meant to fix. so I removed the default behavior moved it to the build/*.mk files (which I think only I use and won't be the official source distro anymore). Josh __________________________________________________ Do You Yahoo!? Spot the hottest trends in music, movies, and more. http://buzz.yahoo.com/