csound/config.h.in is created, but the build still fails in the way
previously described.

Making on Linux and moving the tar file to Cygwin may work, but only for
those who have Linux. I would prefer the system to work from scratch on
Cygwin. That's what the autotools are all about, anyway. Might as well just
have customisable makefiles if this doesn't work, as far as I'm concerned.

============================================
Michael Gogins
gogins at pipeline period com
Irreducible Productions
CsoundVST, an extended version of Csound for programming music and sound
Available at http://sourceforge.net/projects/csound/
============================================


----- Original Message ----- 
From: "John D. Ramsdell" 
To: "Csound Developers Discussion List" 
Sent: Sunday, December 07, 2003 11:56 AM
Subject: [CSOUND-DEV:3695] Re: Autotools build fails on Cygwin


> Please verify that csound/config.h.in is missing, then run autoheader
> and look again.  I am quite mystified by the fact that others seem to
> be able to build the system.
>
> There is another way to build a distibution.  Just do" autoreconf -i;
> ./configure; make" on Linux, and move the tar file to Cygwin.  This is
> what I do.
>
> John
>
> "Michael Gogins"  writes:
>
> > I tried your sequence of commands, with the same failure as before. The
> > first error is
> >
> > configure.ac:9: required file `csound/config.h.in' not found
> >
> > ============================================
> > Michael Gogins
> > gogins at pipeline period com
> > Irreducible Productions
> > CsoundVST, an extended version of Csound for programming music and sound
> > Available at http://sourceforge.net/projects/csound/
> > ============================================
> >
> >
> > ----- Original Message ----- 
> > From: "John D. Ramsdell" 
> > To: "Csound Developers Discussion List" 
> > Sent: Sunday, December 07, 2003 1:24 AM
> > Subject: [CSOUND-DEV:3690] Re: Autotools build fails on Cygwin
> >
> >
> > > "Michael Gogins"  writes:
> > >
> > > > $ aclocal;autoconf;automake --add-missing;./configure;make
> > > > configure.ac:9: required file `csound/config.h.in' not found
> > >
> > > The problem is that autoheader in not being run.  You need to run
> > > autoreconf -i, not autoconf.  If you don't have autoreconf, just type
> > > aclocal; automake; autoheader; autoconf.
> > >
> > > John
> > >
>

"Michael Gogins"  writes:

> Making on Linux and moving the tar file to Cygwin may work, but only
> for those who have Linux. I would prefer the system to work from
> scratch on Cygwin. That's what the autotools are all about,
> anyway. Might as well just have customisable makefiles if this
> doesn't work, as far as I'm concerned.

Of course, you're right.  I was suggesting this as a workaround until
Cygwin autoreconf works for you.  By the way, I verified that
autoreconf works on my Cygwin installation, so I continue to be
mystified by your problem.

John

Hi All,

After an hour of trying to figure this out, I figured it out and
realized I had figured out this same exact thing a while ago and
forgotten about it (though with a slightly different error message which
is why this didn't trigger in my head). 

configure.ac needs to be converted to unix newlines.  

Michael, please check this when you have a chance.  John R: When
checking with Cygwin, did you do your cvs checkout on linux or on
windows?  

There's a series of lines near the end of configure.ac for the
AC_CONFIG_FILES rule.  

I did add "\" at the end of each of those lines as I saw them in John
ff's configure.in in csound5 cvs, but I don't think they're necessary. 
Please try the newlines first, and if that wasn't what fixed it, add the
"\" at the end of each line for the AC_CONFIG_FILES rule to join the
lines.  (I think it's the newlines though).

Was configure.ac originally configured as binary in the cvs and switched
to -kkv?  (I'm curious as it *was* working up until about a week ago). 
I believe unless a file is set to binary, any text file that gets
checked out of CVS get formatted for new lines depending on what
platform it is being checked out on.  Normally this is great except in
this case because bash or M4 gets confused on windows.

steven

stevenyi  writes:

> Hi All,
> 
> After an hour of trying ....
> 
> configure.ac needs to be converted to unix newlines.  

Oh, thank you, thank you, Steven, for figuring this out.  I had no
idea what could be going wrong, and I was not getting close to the
solution. 

> Michael, please check this when you have a chance.  John R: When
> checking with Cygwin, did you do your cvs checkout on linux or on
> windows?  

I have firewall issues when using CVS from Cygwin, so I use it on
Linux.  I make a distribution there, and copy it to Cygwin for
testing. 

> There's a series of lines near the end of configure.ac for the
> AC_CONFIG_FILES rule.  

I added a backslash at the end of each line as John ffitch did.
Please update your sandbox.

> Was configure.ac originally configured as binary in the cvs and switched
> to -kkv?  

No.  Here is what status says:

sh-2.05b$ sfcvs csound status configure.ac
ramsdell@cvs.csound.sourceforge.net's password:

===================================================================
File: configure.ac     	Status: Up-to-date

   Working revision:	1.24
   Repository revision:	1.24	/cvsroot/csound/csound/configure.ac,v
   Sticky Tag:		(none)
   Sticky Date:		(none)
   Sticky Options:	(none)

sh-2.05b$ sfcvs csound status csound/winsound.ico
ramsdell@cvs.csound.sourceforge.net's password:

===================================================================
File: winsound.ico     	Status: Up-to-date

   Working revision:	1.1
   Repository revision:	1.1	/cvsroot/csound/csound/csound/winsound.ico,v
   Sticky Tag:		(none)
   Sticky Date:		(none)
   Sticky Options:	-kb

sh-2.05b$ pwd


> (I'm curious as it *was* working up until about a week ago).  I
> believe unless a file is set to binary, any text file that gets
> checked out of CVS get formatted for new lines depending on what
> platform it is being checked out on.  Normally this is great except
> in this case because bash or M4 gets confused on windows.

I think it stopped working when I added the Makefiles for the
utilities.  Only then did AC_CONFIG_FILES require multiple lines.

John