chuck build (fedora 8)

flies · Joined: May 20, 2008 Posts: 33 Location: NJ

I'm building chuck on my fedora 8 box. make can't find sndfile.h, and i'm not sure how to solve the problem.

any help for us?

Kassen · Posted: Tue May 20, 2008 8:46 am Post subject:

Not sure how installing stuff on Fedora works, but would this help?
http://www.mega-nerd.com/libsndfile/#Download

[edit] Welcome one board!

flies · Joined: May 20, 2008 Posts: 33 Location: NJ

i am no linux/fedora expert, but i had already installed libsndfile by

yum install libsndfile

i had figured this would be enough, but i've now compiled libsndfile and installed it, the chuck install seems to be going smoothly for now. i'll be sure and whine like a little baby if anything goes wrong Cool

edit:
[minerva@tesla src]$ chuck
[chuck]: no input files... (try --help)

Very Happy

Kassen · Posted: Tue May 20, 2008 9:29 am Post subject:

flies · Joined: May 20, 2008 Posts: 33 Location: NJ

hmm, well, i haven't quite gotten it working.

Kassen · Posted: Tue May 20, 2008 10:07 am Post subject:

Ow, no, that's not quite right.

Can you still see if building it resulted in any particularly wrong-looking remarks?
I still suspect you need libsndfile-dev but maybe Fedora packages dev files with the normal library?

Also, considering that the only thing you are doing in the example code is address the DAC we might suspect the issue to be in the sound system.

Those too need libraries, something like libalsa-dev or libjack-dev or similar. This of course needs to match the type of audio driver you'd like to use.

I wonder if we have somebody around with knowledge of Fedora packages and how they work?

flies · Joined: May 20, 2008 Posts: 33 Location: NJ

Kassen · Posted: Tue May 20, 2008 11:24 am Post subject:

flies · Joined: May 20, 2008 Posts: 33 Location: NJ

so it's not that libsndfile ain't working:

[root@tesla minerva]# yum list all | grep libsnd
libsndfile.i386 1.0.17-2.fc8 installed
libsndfile.x86_64 1.0.17-2.fc8 installed
libsndfile-devel.x86_64 1.0.17-2.fc8 installed
libsndfile-devel.i386 1.0.17-2.fc8 installed

i did have to install the -devel bits. still no luck...

Kassen · Posted: Tue May 20, 2008 6:26 pm Post subject:

Could you try the same for "alsa"?

flies · Joined: May 20, 2008 Posts: 33 Location: NJ

sure.

Kassen · Posted: Wed May 21, 2008 8:47 am Post subject:

Ok, so you do have the alsa "dev" one as well.

...But I think I may have bad news, all these "64" numbers, might those mean you are running a 64 bit install of Linux? Perhaps?

That would be quite relevant since sadly at the moment ChucK won't work with 64 bit Linux (yet!), so perhaps you did compile it all right, that would explain the seg-fault, I think.

If that's the issue I'm not sure how to proceed, it would depend on whether you want ChucK badly enough to switch to a 32 bit version of your OS...

If this is not in the DOC's it should be.

Kassen · Posted: Wed May 21, 2008 8:59 am Post subject:

I pointed the issue out on the list, hopefully this will save others from this matter in the future.

Figuring stuff out on your own is is a beautiful thing indeed, BTW, a essential skill for ChucKists, I fear... :¬)

flies · Joined: May 20, 2008 Posts: 33 Location: NJ

Kassen · Posted: Wed May 21, 2008 1:38 pm Post subject:

Mr Theremin · Joined: Mar 22, 2008 Posts: 22 Location: Ohio

I have a question for the Linux experts.

I am having a difficult time creating a Linux ChucK machine. I had ChucK compiled and working once on Red Hat Enterprise 5.1 using g++ 3.4.6-3. I no longer have access to that machine and have not had a working ChucK since. :<(

My first attempt was with ChucK 1.2.1.1 on a fresh Fedora 9 i386 with g++ 4.3. They must have rearranged the libraries because I get lots of compile errors. The first one is :sort is not a member of stdlib. I gave up for now.

My second attempt was on a fresh Red Hat Enterprise 5 i386 with g++ 4.1.1. Chuck compiles but I get segmentation faults when I run any .ck file with audio.

Can anyone tell me what OS configuration they are using for ChucK 1.2.1.1?

Kassen · Posted: Fri May 30, 2008 3:03 am Post subject:

Yeah, I successfully build it for Demidu, Studio64 (32bit version) and Ubuntu (both current and the last). After the first time I had it down and now it's a matter of minutes.

All of those are based on Debian and have Debian's package management system. Though I enjoy Linux as a OS a lot and am firmly behind it's politics I'm no great expert on it which makes Debian's package management quite convenient for me. Especially Ubuntu makes nearly everything trivially easy for me.

Not trying to start a distro war, just sharing my own experiences.

I'd say Ubuntu would be a good choice, preferably with a realtime kernel pluged in, Ubuntu-studio would also be great as it comes with such a kernel and with a lot of other sound/music tools/toys. Some people (Nescivi, for example) prefer studio 64 (but do get the 32 bit version for ChucK!).

If you haven't already that might be a good thing to try. You just start "synaptic" (which is the graphical interface for package management), you select the ones that you want/need (don't forget the -dev versions!), you hit "apply" and it will sort all the dependencies and so on out for you. If you prefer KDE there's Kubuntu for that as well.

Mr Theremin · Joined: Mar 22, 2008 Posts: 22 Location: Ohio

Thanks Kassen. Since I am building a ChucK specific machine and ChucK is about the coolest audio development tool I have ever used, I'm happy to install whatever OS it takes.

I have been looking around the ChucK web pages in order to figure out how the program is authored. Does Mr. Wang write the code? Do you or Inventor or Frostburn or any of the guys write or maintain the code? Is ChucK developed on OSX and then ported to PC and Linux or is it the other way around?

I’m sorry if this is public knowledge and I missed it.

I have noticed that many of the G++ 4.3 compile errors are from C++ libraries that don’t contain some of the standard functions any more. Several modules compile OK until chuck_vm.cpp and then the trouble starts. sort is not a member of std any more, youhave to include <algorithm>. It may only take a few includes to remedy the problems. I am tempted to try and fix it but I’m not sure if someone else had fixed it or if anyone else would be interested in the repaired code.

Even if I did fix ChucK for Red Hat G++ 4.3 I don’t know if it would be backwards compatible with the OS that rest of the community is using or if someone is testing and controlling quality.

Kassen · Posted: Fri May 30, 2008 6:30 am Post subject: Re: Compile Problems

Kassen · Posted: Fri May 30, 2008 6:50 am Post subject:

Send a mail to the list requesting help on this. We'll need to sort this, RedHat isn't exactly a obscure distro....

flies · Joined: May 20, 2008 Posts: 33 Location: NJ

so, if you were to pick a linux distro to do chuck on, which would you pick?

sorry, i know this is an annoying question. The computer i tried to use was my work machine, and i am installing linux on my home machine now....

Mr Theremin · Joined: Mar 22, 2008 Posts: 22 Location: Ohio

In my latest experiment I used CentOS 5.1. Chuck and LibSndFile compile without any complaint and are totally functional.

CentOS advertises that they are built from RedHat Enterprise source code and, having used both, that sure seems to be the case. Funny thing is that I was getting all of those errors under RedHat Enterprise 5.1.

Kassen · Posted: Fri Jun 20, 2008 8:27 am Post subject:

Ubuntu with a RT kernel for me.
64Studio (in the 32 bit version!) could also suit your needs. ( http://64studio.com/about )

Not a annoying question at all but note I like Debian & Gnome and you may have other tastes.

Frostburn · Posted: Fri Jun 20, 2008 10:12 am Post subject:

I picked Ubuntu Studio. It's designed for working with graphics,sound and video and comes with a real time kernel.