We all understand that your build system has worked for you.

Please understand that your makefile-based build system has NOT worked for
at least some of us, in spite of the fact that we greatly appreciate your
work porting Csound to different platforms. We wouldn't even be having this
discussion if you hadn't done that.

We also understand that the current state of the build system does not work
for you, and naturally we are concerned to remedy this.

To get my build system working, I put the Csound5 files on my Red Hat Linux
8.0 laptop, and tried building the dependencies. I build most of them except
for PortAudio, which wouldn't build because Red Hat 8 doesn't come with ALSA
drivers. But Csound 5 wouldn't work because Red Hat 8's autotools aren't
current enough. I re-installed them from sources from the GNU home pages for
autoconf, automake, and libtool. Then Csound 5 built OK -- until it wanted
PortAudio.

I started upgrading the ALSA drivers, and they had lots of dependencies that
weren't satisfied, so I decided to upgrade to Fedora Core 1. I did that (it
took most of the day). The PortAudio configure script still didn't work, so
I found the workaround documented in the current Csound 5 configure.ac.
Finally, everything built.

I would guess that a similar effort will probably be required on OS X and
maybe on some of the other Linuxes as well.

This is painful, but once things work, they seem to keep working.

If you have ALSA on Linux, I would guess that you could get Csound 5
configure.ac and Makefile.am working by upgrading autotools from the latest
sources, as I did.

============================================
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 ffitch" 
To: "Csound Developers Discussion List" 
Sent: Sunday, February 22, 2004 3:22 PM
Subject: [CSOUND-DEV:4087] Re: Major commits to Csound 5


> On Sun, 22 Feb 2004, stevenyi wrote:
>
> > I have to say that until the
> > autotools work was going on, I was never able to easily compile csound
> > on any platform, and now I am able to pretty consistently on different
> > linux systems and cygwin/windows systems I've tried.
> >
>
> I have the opposite experience.  Since the introduction of these tools I
> have not been able to build Csounmd for ANY platform!
>
> I have been developing multi-platform software for rather a long time
> without this hassle.
>
> I have checked this machine (RedHar7.3 +) and it has
> autoconf (GNU Autoconf) 2.57
> automake (GNU automake) 1.4-p5
>
> The Debian machine has I think autoconf 2.19 (turned if off before supper)
>
> The Macintosh has
> autoconf (GNU Autoconf) 2.58
> automake (GNU automake) 1.7.8
>
> The other machines are probably 2.57/1.4 except the Windows machine which
> does not have any of these.
>
> I do not know a sire from whence I could upgrade these system.  RH have
> ceased to be interested in 7.3.  Macintosh do not seem to have a
> mechanism.
>
> So it looks as if I will be back to mailing changes to people.
>
> ==John ff
>
>
>

Michael, These are the errors I'm getting on Cygwin.
I updated to libtool 1.5.2 and automake 1.8.2.
Windows XP system.
Csound 5.

sherlock@bobby-junior ~/csoundcvs/csound5
$ autoreconf -i -f
autoreconf: warning: both `configure.ac' and `configure.in' are present.
autoreconf: warning: proceeding with `configure.ac'.
warning: `configure.ac' and `configure.in' both present.
 at /usr/autotool/devel/bin/aclocal line 59
warning: proceeding with `configure.ac'.
 at /usr/autotool/devel/bin/aclocal line 59
autoreconf: `configure.ac' and `configure.in' both present.
autoreconf: proceeding with `configure.ac'.
warning: `configure.ac' and `configure.in' both present.
 at /usr/autotool/devel/bin/aclocal line 59
warning: proceeding with `configure.ac'.
 at /usr/autotool/devel/bin/aclocal line 59
autoconf: warning: both `configure.ac' and `configure.in' are present.
autoconf: warning: proceeding with `configure.ac'.
Using `AC_PROG_RANLIB' is rendered obsolete by `AC_PROG_LIBTOOL'
warning: `configure.ac' and `configure.in' both present.
 at /usr/autotool/devel/bin/aclocal line 59
warning: proceeding with `configure.ac'.
 at /usr/autotool/devel/bin/aclocal line 59
autoconf: warning: both `configure.ac' and `configure.in' are present.
autoconf: warning: proceeding with `configure.ac'.
autoheader: `configure.ac' and `configure.in' both present.
autoheader: proceeding with `configure.ac'.
warning: `configure.ac' and `configure.in' both present.
 at /usr/autotool/devel/bin/automake line 5412
warning: proceeding with `configure.ac'.
 at /usr/autotool/devel/bin/automake line 5412
configure.ac: installing `./mkinstalldirs'
configure.ac: installing `./missing'
Makefile.am: `babo.la' is not a standard libtool library name
Makefile.am: installing `./compile'
Makefile.am: `bbcut.la' is not a standard libtool library name
Makefile.am: `biquad.la' is not a standard libtool library name
Makefile.am: `butter.la' is not a standard libtool library name
Makefile.am: `clfilt.la' is not a standard libtool library name
Makefile.am: `cross2.la' is not a standard libtool library name
Makefile.am: `dam.la' is not a standard libtool library name
Makefile.am: `filter.la' is not a standard libtool library name
Makefile.am: `flanger.la' is not a standard libtool library name
Makefile.am: `follow.la' is not a standard libtool library name
Makefile.am: `grain.la' is not a standard libtool library name
Makefile.am: `grain4.la' is not a standard libtool library name
Makefile.am: `hrtferX.la' is not a standard libtool library name
Makefile.am: `locsig.la' is not a standard libtool library name
Makefile.am: `lowpassr.la' is not a standard libtool library name
Makefile.am: `midiops2.la' is not a standard libtool library name
Makefile.am: `midiops3.la' is not a standard libtool library name
Makefile.am: `modal4.la' is not a standard libtool library name
Makefile.am: `nlfilt.la' is not a standard libtool library name
Makefile.am: `oscbnk.la' is not a standard libtool library name
Makefile.am: `phisem.la' is not a standard libtool library name
Makefile.am: `physmod.la' is not a standard libtool library name
Makefile.am: `pitch.la' is not a standard libtool library name
Makefile.am: `pluck.la' is not a standard libtool library name
Makefile.am: `repluck.la' is not a standard libtool library name
Makefile.am: `scansyn.la' is not a standard libtool library name
Makefile.am: `scansynx.la' is not a standard libtool library name
Makefile.am: `sfont.la' is not a standard libtool library name
Makefile.am: `sndwarp.la' is not a standard libtool library name
Makefile.am: `space.la' is not a standard libtool library name
Makefile.am: `spat3d.la' is not a standard libtool library name
Makefile.am: `ugensa.la' is not a standard libtool library name
Makefile.am: `uggab.la' is not a standard libtool library name
Makefile.am: `ugmoss.la' is not a standard libtool library name
Makefile.am: `ugsc.la' is not a standard libtool library name
Makefile.am: `wave_terrain.la' is not a standard libtool library name
Makefile.am: installing `./depcomp'
autoreconf: automake failed with exit status: 1

sherlock@bobby-junior ~/csoundcvs/csound5
$

ALSA may already be second-choice on Linux now - PortAudio supports Jack (for 
which an OS X port has also been announced), and quite probably an install 
system for linux may need at least to offer the possibioity of using Jack, 
rather than trying to drive (and install) ALSA directly.

It worries me if versions of the autoconf tools are not backwards compatible - 
something that the GNU advocates always criticise Windows for.

And if "ordinary" end-users have to leap through the hoops you have desccribed 
below, before thay can even start to install Csound, then I think this whole 
approach must be called into question. In the time this has all taken, with it 
not yet "all working" (and I remain unconvinced, on the evidence, that it will 
eventually work - seems a major leap of faith to me!), we could probably have 
implemented a bespoke installer program for each platform! I never thought that 
"cross-platform" for the autoconf system meant anything beyond 
"cross-unix-variants". Windows users will want a version of setup.exe; and OS X 
users will expect a disk image and a standard OS X Package inside it.

For the record, with Panther and Xcode 1.1, I get the following versions:

autoconf: 2.57
automake: 1.6.3.
libtool:  ??? no version option available.

I suspect that asking OS X users to install special versions of these tools is 
not an acceptable solution.

Richard Dobson



Michael Gogins wrote:

> We all understand that your build system has worked for you.
> 
> Please understand that your makefile-based build system has NOT worked for
> at least some of us, in spite of the fact that we greatly appreciate your
> work porting Csound to different platforms. We wouldn't even be having this
> discussion if you hadn't done that.
> 
> We also understand that the current state of the build system does not work
> for you, and naturally we are concerned to remedy this.
> 
> To get my build system working, I put the Csound5 files on my Red Hat Linux
> 8.0 laptop, and tried building the dependencies. I build most of them except
> for PortAudio, which wouldn't build because Red Hat 8 doesn't come with ALSA
> drivers. But Csound 5 wouldn't work because Red Hat 8's autotools aren't
> current enough. I re-installed them from sources from the GNU home pages for
> autoconf, automake, and libtool. Then Csound 5 built OK -- until it wanted
> PortAudio.
> 
> I started upgrading the ALSA drivers, and they had lots of dependencies that
> weren't satisfied, so I decided to upgrade to Fedora Core 1. I did that (it
> took most of the day). The PortAudio configure script still didn't work, so
> I found the workaround documented in the current Csound 5 configure.ac.
> Finally, everything built.
> 
> I would guess that a similar effort will probably be required on OS X and
> maybe on some of the other Linuxes as well.
> 
> This is painful, but once things work, they seem to keep working.
> 
> If you have ALSA on Linux, I would guess that you could get Csound 5
> configure.ac and Makefile.am working by upgrading autotools from the latest
> sources, as I did.
>