[CSOUND-DEV:4768] RE: Linux failure
Date | 2004-05-25 14:56 |
From | "gogins@pipeline.com" |
Subject | [CSOUND-DEV:4768] RE: Linux failure |
I don't know what your problem is, I built csound5 last night with jack and portaudio on Fedora Core 1 with no problem -- wiped my directory, did a fresh checkout, ran scons, build completed and Csound ran. This is with portaudio v19-devel built for jack as well. Possibly you have several installations of jack (or of portaudio)? I have no need for jack, it could be defaulted back to "off" (I changed it to default to "on" when I was struggling with portaudio on Linux). Original Message: ----------------- From: jpff@codemist.co.uk Date: Tue, 25 May 2004 09:21:54 +0100 To: csound-dev@eartha.mills.edu Subject: [CSOUND-DEV:4767] Linux failure I updates the files on the second RH machine this morning, but the build failed as it could not find -ljack which is reasonable as it does not exist. This used to build; has jack suddenly become essential? It did not build for me when I tried before as they portaudio driver expects v18 (as far as I can tell). Lots of errors like In file included from portaudio_driver.c:41: portaudio_driver.h:57: parse error before `PortAudioStream' portaudio_driver.h:57: warning: no semicolon at end of struct or union portaudio_driver.h:59: warning: type defaults to `int' in declaration of `portaudio_driver_t' portaudio_driver.h:59: warning: data definition has no type or storage class portaudio_driver.c:47: parse error before `PaTimestamp' portaudio_driver.c: In function `paCallback': portaudio_driver.c:49: `driver' undeclared (first use in this function) portaudio_driver.c:49: (Each undeclared identifier is reported only once portaudio_driver.c:49: for each function it appears in.) portaudio_driver.c:49: parse error before `)' portaudio_driver.c:51: `inputBuffer' undeclared (first use in this function) portaudio_driver.c:52: `outputBuffer' undeclared (first use in this function) portaudio_driver.c:54: `framesPerBuffer' undeclared (first use in this function) portaudio_driver.c:55: warning: control reaches end of non-void function portaudio_driver.c: At top level: portaudio_driver.c:58: parse error before `*' portaudio_driver.c: In function `portaudio_driver_attach': portaudio_driver.c:65: `driver' undeclared (first use in this function) portaudio_driver.c:65: `engine' undeclared (first use in this function) portaudio_driver.c: At top level: etc etc If I build with useJack=0 strangely it still complains that it cannot find -ljack ==John ffitch -------------------------------------------------------------------- mail2web - Check your email from the web at http://mail2web.com/ . |
Date | 2004-05-25 15:16 |
From | jpff@cs.bath.ac.uk |
Subject | [CSOUND-DEV:4769] RE: Linux failure |
On my other RedHat machine it said "Adding Jack" although I had set useJack=0 so there is something very odd -- especially as it does not create tag files any more. I downloaded Jack on friday last, and it is that that does not compile. No I do not have any other Jack, there is no libjack on the machine anyway, and I have never used jack. The failure to compile is on both RedHat machines. I have not tried the Debian one yet, nor the Suse. Anyway the situation is that I cannot compile Csound on one machine, and suspect that may be the state on the other, whose files are actually up-to-date as of this morning. While typing -- two other things. 1) If we are to use Jack via portaudio it seems to me that it needs a different binary, linked a different way? I have not found the documentation yet on how to select devices. 2) I started work again on the parser last week, and did some sorting out this morning. Will be doing more between the marking ==John ffitch |
Date | 2004-05-25 16:52 |
From | stevenyi |
Subject | [CSOUND-DEV:4770] RE: Linux failure |
Hi John, I notice sometimes that the SConstruct file works fine using syntax like: if commonEnvironment['useJack']: while on my Fedora linux computer I sometimes have to change to something like: if commonEnvironment['useJack] == 1: I just tried a build on my computer and it too added jack regardless of setting to 0 or 1 on commandline. I've made this kind of change a few times and they seem to get overwritten every time the next person checks in. Explicitly comparing to 1 seems a requirement for python 2.2. Sidenotes - buildZip in SConstruct uses python2.3-only os.walk function, thus function fails for me (I'm using python 2.2 primarily). - anyone notice that doing compiles seems to recompile a lot of files that probably don't need to be recompiled? steven On Tue, 2004-05-25 at 07:16, jpff@cs.bath.ac.uk wrote: > On my other RedHat machine it said "Adding Jack" although I had set > useJack=0 so there is something very odd -- especially as it does not > create tag files any > more. > > I downloaded Jack on friday last, and it is that that does not > compile. No I do not have any other Jack, there is no libjack on the > machine anyway, and I have never used jack. > > The failure to compile is on both RedHat machines. I have not tried > the Debian one yet, nor the Suse. > > Anyway the situation is that I cannot compile Csound on one machine, > and suspect that may be the state on the other, whose files are > actually up-to-date as of this morning. > > While typing -- two other things. > > 1) If we are to use Jack via portaudio it seems to me that it needs a > different binary, linked a different way? I have not found the > documentation yet on how to select devices. > > 2) I started work again on the parser last week, and did some sorting > out this morning. Will be doing more between the marking > > ==John ffitch > > |