I have to agree with John Fitch here. This is the kind of testing we need
to do.

I think what is happening is that somebody (like me or John Ramsdell) does
an autotools build system with a more recent version of autotools, and then
somebody tries to do a build using a less recent version of autotools.

I'm not sure what to do about this.

Original Message:
-----------------
From:  jpff@codemist.co.uk
Date: Sun, 18 Jan 2004 21:07:22 +0000
To: csound-dev@eartha.mills.edu, csound-dev@eartha.mills.edu
Subject: [CSOUND-DEV:3953] Re: How to configure


>>>>> "John" == John D Ramsdell  writes:

 John> John ffitch  writes:
 >> ...and more.  The make fails as winX11.o does not exist when it creates 
 >> someting called libanalutils.a whatever that it for.  Seems even more 
 >> broken that I thought!

 John> Where you able to build the system by renaming Makefile.lnx to
 John> Makefile and typing make in the csound directory?  This should allow
 John> you to build a system just as you have always done.

I thought the whole point of the autoconf stuff was to write a correct
makefile.   No I have not tried that as i was acting like a user, nit
a developer.  I followed the CVS rules to down load what it gave me,
and read the README file.  Surely I am not the only person in the
universe using Debian stable?  This is not my usual platform, but i
was experimenting with Debian in preparation for the loss of Redhat.
If Csound does not build on a freshly installed and upgraded system
then something is very wrong.  Sure I could transfer by working tree,
but there is little point in that.

==John ffitch


--------------------------------------------------------------------
mail2web - Check your email from the web at
http://mail2web.com/ .