[CSOUND-DEV:5724] Csound5 build report and thoughts
Date | 2005-01-18 19:26 |
From | Iain Duncan |
Subject | [CSOUND-DEV:5724] Csound5 build report and thoughts |
Regular build worked fine. Building with portmidi enabled fails. All based on checking out freshly from CVS today, gentoo linux. - portmidi fail: > /lib/libportmidi.a(pmlinuxalsa.o)(.text+0x1458): In function `pm_linuxalsa_term': > pm_linux/pmlinuxalsa.c:723: undefined reference to `snd_seq_close' > collect2: ld returned 1 exit status > scons: *** [cscore] Error 1 > scons: building terminated because of errors. I know portmidi is working on this machine because I have successfully built my own port midi apps. Other thoughts: - the README file tells you to read csound.pdf. This used to be a nice small pdf on how to build csound, now it's a monstrous manual that takes forever to open, and in the gnome pdf viewer at any rate, is illegible goobledygook. Sure, the gnome pdf viewer is lame, but not that lame, something is seriously wrong there. I think a short file specifically on getting csound5 to build and work was a good plan. And I freaking hate pdf manuals. - there is a NEWS file that is blank. weird - the Loadable_Opcodes.txt file has a nice list, but no instructions on what *to do* to make your opcodes load. Maybe a quick explanation of how to get them to load would be nice in the same place. I've done it before, but I can't remember how 'cause it's been a while, and looks like I'll be hunting through list archives to find out 'cause I sure can't read that manual ... thanks iain |
Date | 2005-01-18 20:16 |
From | Iain Duncan |
Subject | [CSOUND-DEV:5726] Re: Csound5 build report and thoughts |
I just updated alsa-lib to 1.0.6, and still the same thing. Could I have portmidi installed incorectly or something? I have been able to compile my own portmidi apps, but it is very possible that I have it set up wrong or something. error again: > /lib/libportmidi.a(pmlinuxalsa.o)(.text+0x1458): In function `pm_linuxalsa_term': > pm_linux/pmlinuxalsa.c:723: undefined reference to `snd_seq_close' > collect2: ld returned 1 exit status > scons: *** [cscore] Error 1 > scons: building terminated because of errors. thanks iain jpff@codemist.co.uk wrote: > snd_seq_close is defined in alsa-lib-1.0.4/src/seq/seq.c and so is in > the alsa library. What version etc of ALSA do you have? > ==John ffitch > > |
Date | 2005-01-18 21:08 |
From | Iain Duncan |
Subject | [CSOUND-DEV:5729] Re: Csound5 build report and scons problems |
> Is -lalsa before -lportmidi in the build? If so that could cause > problems as portmidi makes references to alsa Can you tell me how I would find that out? I'm not sure where in the output to look. However looking made me find what I consider to be very bad behaviour as we currently have scons working: If in your SConstruct file you ask for various options, ie portaudio, fltk, etc, and then scons doesn't find the header files where it's expecting to, instead of failing, it just builds anyway without those options. Considering on a fast machine all that stuff just blazes by way too fast to read, I didn't even notice that I wasn't actually managing to build with portaudio or fltk or csoundvst until I went looking back through the output. Personally I think this is bad. Better instructions on what scons is going to look for where might be useful too I guess. thanks iain |
Date | 2005-01-18 21:41 |
From | Iain Duncan |
Subject | [CSOUND-DEV:5731] Re: Csound5 build report and thoughts |
So the real problem was that I was not buidling with portaudio, without knowing it. Audacity had put portaudio v19 somewhere funky, so while it was on the machine, it wasn't in the normal spot. A reinstall of the portaudio v19 snapshot solved this. After that was done, building with both portaudio and portmidi worked. I guess that's a gotcha we hadn't found yet, portmidi depending on portaudio, or at least that's not documented I don't think. The above serves as a good example of why I think scons should fail if your chosen options aren't found working. I had no idea I wasn't building with portaudio successfully. Ooops. ; ) Now, what did everyone want tested with portmidi? iain jpff@codemist.co.uk wrote: > snd_seq_close is defined in alsa-lib-1.0.4/src/seq/seq.c and so is in > the alsa library. What version etc of ALSA do you have? > ==John ffitch > > |
Date | 2005-01-19 08:14 |
From | jpff@codemist.co.uk |
Subject | [CSOUND-DEV:5725] Re: Csound5 build report and thoughts |
snd_seq_close is defined in alsa-lib-1.0.4/src/seq/seq.c and so is in the alsa library. What version etc of ALSA do you have? ==John ffitch |
Date | 2005-01-19 09:11 |
From | jpff@codemist.co.uk |
Subject | [CSOUND-DEV:5727] Re: Csound5 build report and thoughts |
Is -lalsa before -lportmidi in the build? If so that could cause problems as portmidi makes references to alsa ==John ffitch |