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. this one should have all the configure stuff working with the new assembly infrastructure. I have tried to make it as easy as possible to port routines to assembly. all that's really needed now is to write the corresponding routine for a specific instruction set, then use the cpu info structure in the encoder/decoder setup to set the right function pointer. configure should set all the right #defines to get the relevant asm files compiled and linked. see FLAC__encoder_init() for an example. anyway, try it out and let me know if anything bad happens! it should be a short jump from beta 10 to 1.0. thanks, Josh __________________________________________________ Do You Yahoo!? Yahoo! Auctions - buy the things you want at great prices http://auctions.yahoo.com/
> > 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/
Josh Coalson <xflac@yahoo.com> wrote:> 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.What's the sequence of steps required to turn this into a buildable distribution? | # nasm build rule: | %.lo: %.s Do we officially depend on GNU make now? You could express this portably with something like this: .SUFFIXES: .lo .s .s.lo: ... | $(NASM) -f elf -d ELF $< -o $@ This won't fly on OpenBSD/i386, which is a.out. -- Christian "naddy" Weisgerber naddy@mips.inka.de
Christian Weisgerber <naddy@mips.inka.de> wrote:> | # nasm build rule: > | %.lo: %.sEven with gmake, this really works only by accident. Automake generates a competing suffix rule, and gmake apparently gives the rule above a higher priority than the suffix rule (or that just happens to be the evaluation order). Matt, since you seem to understand automake, can you come up with something to properly integrate this with automake's logic?> .SUFFIXES: .lo .s > .s.lo:(This of course doesn't work with automake.) -- Christian "naddy" Weisgerber naddy@mips.inka.de
On Fri, 25 May 2001, Josh Coalson wrote:> 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 sure what I'm doing. Cheers.> > thanks, > 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
--- Christian Weisgerber <naddy@mips.inka.de> wrote:> Josh Coalson <xflac@yahoo.com> wrote: > > > 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. > > What's the sequence of steps required to turn this into a buildable > distribution? >(except for the other problems you mention below) the sequence I use is: $ aclocal && autoconf && automake -c -a -i and when I'm ready to build: $ ./configure [options]> | # nasm build rule: > | %.lo: %.s > > Do we officially depend on GNU make now? > You could express this portably with something like this: > > .SUFFIXES: .lo .s > .s.lo: > ... > > | $(NASM) -f elf -d ELF $< -o $@ > > This won't fly on OpenBSD/i386, which is a.out. >yeah, my preferences are showing through... I'm not familiar with OpenBSD. the only boxes I have are Linux, Solaris, and Win32. nasm.h does the right thing for a.out formats but the Makefile.am is not flexible enough. also, there is no intention to make it build only on gnu make, it's just that since that's all I use, I don't catch the things you mentioned. the patches should be minor but I don't think I could guess it all correctly without a system to test it on. can you submit such a patch? it would be much appreciated. Josh __________________________________________________ Do You Yahoo!? Get personalized email addresses from Yahoo! Mail - only $35 a year! http://personal.mail.yahoo.com/
On Wed, May 30, 2001 at 05:16:46PM +0000, Christian Weisgerber wrote:> Josh Coalson <xflac@yahoo.com> wrote: > > > 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. > > What's the sequence of steps required to turn this into a buildable > distribution?aclocal && autoconf && automake --foreign --add-missing This should probably be placed in a shell script in CVS (other projects use the name 'autogen.sh').> | # nasm build rule: > | %.lo: %.s > > Do we officially depend on GNU make now? > You could express this portably with something like this: > > .SUFFIXES: .lo .s > .s.lo: > ...FLAC has required GNU make (or at least something more than the lowest common denominator) for some time now. The pre-automake makefiles used include statements, which are not supported by many makes.> | $(NASM) -f elf -d ELF $< -o $@ > > This won't fly on OpenBSD/i386, which is a.out.This might be solved by using 'as' instead of nasm, though many versions of 'as' don't support Intel syntax (GNU as does). -- - mdz