I was able to do a fresh checkout and build on Cygwin.

By fresh checkout, I mean I moved the csound5 directory and did a "co" on
csound5, retrieving fresh copies of all CVS files. I then did the usual
autoreconf -i -f;./configure;make without problem.

I will test Linux tonight, and other configurations as well.

============================================
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: 
To: "Csound Developers Discussion List" 
Sent: Tuesday, March 09, 2004 2:30 AM
Subject: [CSOUND-DEV:4258] csound5 does not build


> I tried the new version and it does not compile for me
>
>

gcc -DHAVE_CONFIG_H -I. -I. -I./H -DBETA -I./H -I/usr/local/include -I/usr/l
ocal/boost -I/usr/include/Python2.3 -DBETA -I./H -I/usr/local/include -I/usr
/local/boost -I/usr/include/Python2.3 -malign-loops=4 -malign-jumps=4 -g -O2
 -O2 -g -Wall -DBUILDING_LIBCSOUND -g -O2 -O2 -g -Wall -MT
libcsound_la-entry1.lo -MD -MP -MF .deps/libcsound_la-entry1.Tpo -c
Engine/entry1.c  -fPIC -DPIC -o .libs/libcsound_la-entry1.o
> Engine/entry1.c:636: `itablew' undeclared here (not in a function)
> Engine/entry1.c:636: initializer element is not constant
> Engine/entry1.c:636: (near initialization for `opcodlst_1[383].iopadr')
> Engine/entry1.c:637: `tblsetw' undeclared here (not in a function)
> Engine/entry1.c:637: initializer element is not constant
> Engine/entry1.c:637: (near initialization for `opcodlst_1[384].iopadr')
> Engine/entry1.c:637: `ktablew' undeclared here (not in a function)
> Engine/entry1.c:637: initializer element is not constant
> Engine/entry1.c:637: (near initialization for `opcodlst_1[384].kopadr')
> Engine/entry1.c:638: `tblsetw' undeclared here (not in a function)
> and so forth for many lines
>
> ==John ffitch
>

....and now on MaxOSX I check out the code, and then have to build
libsndfile (no problem) and PortAudio -- which is a problem!

1) It has no rule to build -g needs for lib/portaudio.a -- yes I know
that is nonsense but that is what it said.

2) It complains about pkg-config not being present; what does this do?

So anyway having libsndfile I tried to build csound5

It needs autoconf newer than 2.57 -- but OSX does not offer me that.
So what next?  No configure made so I suppose it is back to doing it
the way I used to.  Decided to can the OSX system for the night.

This is on the OSX 10.2 system, but my OSX10.1 system.

On Linux the problem is that there is no ugrw1.h so entry1.c fails

==John ffitch

Hi John,

I haven't tried recently, but the last time I tried autoconf stuff on 
OSX 10.1 I also had no success.  I was able to get past autconf, etc. on 
OSX 10.2 if I remember correctly, but ran into other problems.  I was 
using SourceForge's compile farm to compile on OSX 10.2 as I don't have 
OSX 10.2 installed on anything locally(nice as it's all doable via 
ssh).  This was all with the csound4 GBS. 

Last I checked the configure.ac in csound5 has not been updated to 
handle OSX.  I'll hopefully be able to get CVS working again on my home 
computer (SourceForge person is helping me, seems to be an issue on my 
computer) and after that will spend time this week trying to get 
libsndfile, portaudio, and csound on OSX.

steven


jpff@cs.bath.ac.uk wrote:

>....and now on MaxOSX I check out the code, and then have to build
>libsndfile (no problem) and PortAudio -- which is a problem!
>
>1) It has no rule to build -g needs for lib/portaudio.a -- yes I know
>that is nonsense but that is what it said.
>
>2) It complains about pkg-config not being present; what does this do?
>
>So anyway having libsndfile I tried to build csound5
>
>It needs autoconf newer than 2.57 -- but OSX does not offer me that.
>So what next?  No configure made so I suppose it is back to doing it
>the way I used to.  Decided to can the OSX system for the night.
>
>This is on the OSX 10.2 system, but my OSX10.1 system.
>
>On Linux the problem is that there is no ugrw1.h so entry1.c fails
>
>==John ffitch
>
>
>
>  
>

Hi John,

I got things back in order on my system so gave tried to compile 
portaudio on the sourceforge compilefarm.  The configure script doesn't 
seem to work for OSX.  Looking at this page:

http://www.portaudio.com/docs/pa_tut_mac_osx.html

it recommends to use project builder, which I don't have access to as 
I'm shelling into the compile farm.  It at least lists the necessary 
files, so will probably go make a Makefile to see if I can progress 
forward with this.

steven

jpff@cs.bath.ac.uk wrote:

>1) It has no rule to build -g needs for lib/portaudio.a -- yes I know
>that is nonsense but that is what it said.
>  
>

steven yi  writes:

> This was all with the csound4 GBS. 

I was never able to build a distribution on Darwin with csound4 GBS.
I was able to configure, make, and install a distribution built on
Cygwin.  I think the current distribution still builds on Darwin, but
I haven't tested it lately.

John

I think I was incorrect in this email and I think those instructions are 
for v18.  I was building a Makefile and when trying to compile 
pa_mac_core/pa_mac_core.c it reported not being able to find pa_host.h.  
Looking around, my guess is that pa_mac_core is old and not up to date 
with the rest of v19 as (it seems) header files changed names.  Looking 
at pa_mac_core.c, the last comment written was from 3.31.2002, so my 
guess is that this might not even work on OSX. =( (Someone please 
correct me if I'm wrong.)

steven


steven yi wrote:

> Hi John,
>
> I got things back in order on my system so gave tried to compile 
> portaudio on the sourceforge compilefarm.  The configure script 
> doesn't seem to work for OSX.  Looking at this page:
>
> http://www.portaudio.com/docs/pa_tut_mac_osx.html
>
> it recommends to use project builder, which I don't have access to as 
> I'm shelling into the compile farm.  It at least lists the necessary 
> files, so will probably go make a Makefile to see if I can progress 
> forward with this.
>
> steven
>
> jpff@cs.bath.ac.uk wrote:
>
>> 1) It has no rule to build -g needs for lib/portaudio.a -- yes I know
>> that is nonsense but that is what it said.
>>  
>>
>
>
>

That indeed is an old version. I have been using a v18 "snapshot" ca Jan 2004; 
the last comment in pa_mac_core.c is dated 12.09.03. It works flawlessly (well, 
only simple file playback tried so far) in Panther, including sending 
multi-channel to the Firewire 410.

Richard Dobson

steven yi wrote:
> I think I was incorrect in this email and I think those instructions are 
> for v18.  I was building a Makefile and when trying to compile 
> pa_mac_core/pa_mac_core.c it reported not being able to find pa_host.h.  
> Looking around, my guess is that pa_mac_core is old and not up to date 
> with the rest of v19 as (it seems) header files changed names.  Looking 
> at pa_mac_core.c, the last comment written was from 3.31.2002, so my 
> guess is that this might not even work on OSX. =( (Someone please 
> correct me if I'm wrong.)
> 
> steven

Very strange!  I downloaded both v18 and v19 snapshots to check and sure 
enough the v19 snapshot's pa_mac_core.c  is much older than the one in 
the v18 snapshot tarball.  (v19's is marked as cvs 1.8 while the v18 is 
marked as cvs 1.8.4.13). 

I did a cvs checkout from portaudio's cvs's main branch using:

cvs -d:pserver:anonymous@www.portaudio.com:/home/cvs co portaudio

and got the older 1.8 version of the file.  I looked through the CVS 
with a CVS GUI and I couldn't find where the 1.8.4.13 file exists in any 
of the branches. 

So, any suggestions on how to progress from here?

steven


Richard Dobson wrote:

> That indeed is an old version. I have been using a v18 "snapshot" ca 
> Jan 2004; the last comment in pa_mac_core.c is dated 12.09.03. It 
> works flawlessly (well, only simple file playback tried so far) in 
> Panther, including sending multi-channel to the Firewire 410.
>
> Richard Dobson

I built csound 4.23f11 on Darwin a couple of days ago with no problem.  
Includes FLTK stuff as well.  But I did not use configuration stuff
==John ff

On 10 Mar 2004, John D. Ramsdell wrote:

> steven yi  writes:
> 
> > This was all with the csound4 GBS. 
> 
> I was never able to build a distribution on Darwin with csound4 GBS.
> I was able to configure, make, and install a distribution built on
> Cygwin.  I think the current distribution still builds on Darwin, but
> I haven't tested it lately.
> 
> John
> 
> 
> 
> 

I have project builder, but have never managed to get it to do anything.
==John ff