Hi all,

I would like to do a new install to try out the new moog filters, but I get this error when doing build-dep:

E: Build-Depends dependency for csound cannot be satisfied because candidate version of package cdbs can't satisfy version requirements

Any advice much appreciated!

brian

Oh, I thought I had to follow the Debian/Ubuntu link on that link, but now I see there's another install process, so I'll try that and report back.

Thanks!  :)

@Victor:  thank you for getting me back "in" the mailing! :)  I didn't know what happened there for a moment...

brian

On Mon, 11 Jan 2016 20:24:02 +0100, Hlöðver Sigurðsson wrote:

You are not really building from git if you are using apt-get package manager? I dont use ubuntu but I would suggest that you build it with make and sudo make install from git as described here: https://github.com/csound/csound/blob/develop/BUILD.md

2016-01-11 14:03 GMT+01:00 <brian@linuxsynths.com>:

Hi all,

I would like to do a new install to try out the new moog filters, but I get this error when doing build-dep:

E: Build-Depends dependency for csound cannot be satisfied because candidate version of package cdbs can't satisfy version requirements

 

Any advice much appreciated!

 

brian

 

Csound mailing list Csound@listserv.heanet.ie https://listserv.heanet.ie/cgi-bin/wa?A0=CSOUND Send bugs reports to https://github.com/csound/csound/issues Discussions of bugs and features can be posted here

Csound mailing list Csound@listserv.heanet.ie https://listserv.heanet.ie/cgi-bin/wa?A0=CSOUND Send bugs reports to https://github.com/csound/csound/issues Discussions of bugs and features can be posted here

Maybe. I'll try that too!

brian

On Mon, 11 Jan 2016 20:29:21 +0100, Hlöðver Sigurðsson wrote:

Ah ok I see why you are using build-deps. If Csound was working already, cant you skip that step and go straight to compilation?

2016-01-11 14:03 GMT+01:00 <brian@linuxsynths.com>:

Hi all,

I would like to do a new install to try out the new moog filters, but I get this error when doing build-dep:

E: Build-Depends dependency for csound cannot be satisfied because candidate version of package cdbs can't satisfy version requirements

 

Any advice much appreciated!

 

brian

 

Csound mailing list Csound@listserv.heanet.ie https://listserv.heanet.ie/cgi-bin/wa?A0=CSOUND Send bugs reports to https://github.com/csound/csound/issues Discussions of bugs and features can be posted here

Csound mailing list Csound@listserv.heanet.ie https://listserv.heanet.ie/cgi-bin/wa?A0=CSOUND Send bugs reports to https://github.com/csound/csound/issues Discussions of bugs and features can be posted here

Hi!

What distro and what version? I guess debian or ubuntu?

I am personally on openSuse and don't know exactly byt I guess cdbs is a kind of helping tool of debian packages. Can you see if there is a newer version available. Or if not you can install the necessary dependencies also with separate commands. See the necessary packages

under the csound Build.md Fedora guidelines:

https://github.com/csound/csound/blob/develop/BUILD.md#fedora

I guess for debian the development package names end with -dev not devel, but I am not sure. So you could do

apt-get install ladspa ladspa-devel fluidsynth fluidsynth-devel boost boost-devel java-devel etc

Don't worry, building from source can take time first time, but later is really easy.

Note that you need to checkout to git branch 'develop' to try out the newest state of development, master branch stays on the latest release state.

Hope it helps!

tarmo

On Monday 11 January 2016 14:03:07 you wrote:

> Hi all,

>

> I would like to do a new install to try out the new moog

> filters, but I get this error when doing build-dep:

>

> E: Build-Depends

> dependency for csound cannot be satisfied because candidate version of

> package cdbs can't satisfy version requirements

>

> Any advice much

> appreciated!

>

> brian

>

> Csound mailing list

> Csound@listserv.heanet.ie

> https://listserv.heanet.ie/cgi-bin/wa?A0=CSOUND

> Send bugs reports to

> https://github.com/csound/csound/issues

> Discussions of bugs and features can be posted here

Oh, I thought I had to follow the Debian/Ubuntu link on that link, but now I see there's another install process, so I'll try that and report back.

Thanks!  :)

@Victor:  thank you for getting me back "in" the mailing! :)  I didn't know what happened there for a moment...

 

brian

 

On Mon, 11 Jan 2016 20:24:02 +0100, Hlöðver Sigurðsson wrote:

You are not really building from git if you are using apt-get package manager? I dont use ubuntu but I would suggest that you build it with make and sudo make install from git as described here: https://github.com/csound/csound/blob/develop/BUILD.md

2016-01-11 14:03 GMT+01:00 <brian@linuxsynths.com>:

Hi all,

I would like to do a new install to try out the new moog filters, but I get this error when doing build-dep:

E: Build-Depends dependency for csound cannot be satisfied because candidate version of package cdbs can't satisfy version requirements

 

Any advice much appreciated!

 

brian

 

Csound mailing list Csound@listserv.heanet.ie https://listserv.heanet.ie/cgi-bin/wa?A0=CSOUND Send bugs reports to https://github.com/csound/csound/issues Discussions of bugs and features can be posted here

Csound mailing list Csound@listserv.heanet.ie https://listserv.heanet.ie/cgi-bin/wa?A0=CSOUND Send bugs reports to https://github.com/csound/csound/issues Discussions of bugs and features can be posted here

 

 

Csound mailing list Csound@listserv.heanet.ie https://listserv.heanet.ie/cgi-bin/wa?A0=CSOUND Send bugs reports to https://github.com/csound/csound/issues Discussions of bugs and features can be posted here

That build dep step should work. One of the packages needs updating I think. You should be able to find the list of packages on the github site. It'll be there somewhere.

That build dep step should work. One of the packages needs updating I think. You should be able to find the list of packages on the github site. It'll be there somewhere.

On 11 Jan 2016 19:37, "Victor Lazzarini" <Victor.Lazzarini@nuim.ie> wrote:

I did not do anything, but John might have. Glad you can post now.

Victor Lazzarini

Dean of Arts, Celtic Studies, and Philosophy

Maynooth University

Ireland

On 11 Jan 2016, at 19:31, brian@LINUXSYNTHS.COM wrote:

Oh, I thought I had to follow the Debian/Ubuntu link on that link, but now I see there's another install process, so I'll try that and report back.

Thanks!  :)

@Victor:  thank you for getting me back "in" the mailing! :)  I didn't know what happened there for a moment...

 

brian

 

On Mon, 11 Jan 2016 20:24:02 +0100, Hlöðver Sigurðsson wrote:

You are not really building from git if you are using apt-get package manager? I dont use ubuntu but I would suggest that you build it with make and sudo make install from git as described here: https://github.com/csound/csound/blob/develop/BUILD.md

2016-01-11 14:03 GMT+01:00 <brian@linuxsynths.com>:

Hi all,

I would like to do a new install to try out the new moog filters, but I get this error when doing build-dep:

E: Build-Depends dependency for csound cannot be satisfied because candidate version of package cdbs can't satisfy version requirements

 

Any advice much appreciated!

 

brian

 

Csound mailing list Csound@listserv.heanet.ie https://listserv.heanet.ie/cgi-bin/wa?A0=CSOUND Send bugs reports to https://github.com/csound/csound/issues Discussions of bugs and features can be posted here

Csound mailing list Csound@listserv.heanet.ie https://listserv.heanet.ie/cgi-bin/wa?A0=CSOUND Send bugs reports to https://github.com/csound/csound/issues Discussions of bugs and features can be posted here

 

 

Csound mailing list Csound@listserv.heanet.ie https://listserv.heanet.ie/cgi-bin/wa?A0=CSOUND Send bugs reports to https://github.com/csound/csound/issues Discussions of bugs and features can be posted here

Csound mailing list Csound@listserv.heanet.ie https://listserv.heanet.ie/cgi-bin/wa?A0=CSOUND Send bugs reports to https://github.com/csound/csound/issues Discussions of bugs and features can be posted here

Csound mailing list Csound@listserv.heanet.ie https://listserv.heanet.ie/cgi-bin/wa?A0=CSOUND Send bugs reports to https://github.com/csound/csound/issues Discussions of bugs and features can be posted here

Unfortunately no. It's only because I'm on a distro release that's a bit old (Bodhi 12.04) and I thought I'd give it a shot. I will probably need to just install the apps one-by-one as needed and see if it works that way. I'll look into it tomorrow and check back with results.

brian

On Mon, 11 Jan 2016 20:41:23 +0000, Victor Lazzarini wrote:

does apt-get update help?

Victor Lazzarini

Dean of Arts, Celtic Studies, and Philosophy

Maynooth University

Ireland

On 11 Jan 2016, at 20:32, Rory Walsh <rorywalsh@EAR.IE> wrote:

That build dep step should work. One of the packages needs updating I think. You should be able to find the list of packages on the github site. It'll be there somewhere.

On 11 Jan 2016 19:37, "Victor Lazzarini" <Victor.Lazzarini@nuim.ie> wrote:

I did not do anything, but John might have. Glad you can post now.

Victor Lazzarini

Dean of Arts, Celtic Studies, and Philosophy

Maynooth University

Ireland

On 11 Jan 2016, at 19:31, brian@LINUXSYNTHS.COM wrote:

Oh, I thought I had to follow the Debian/Ubuntu link on that link, but now I see there's another install process, so I'll try that and report back.

Thanks!  :)

@Victor:  thank you for getting me back "in" the mailing! :)  I didn't know what happened there for a moment...

 

brian

 

On Mon, 11 Jan 2016 20:24:02 +0100, Hlöðver Sigurðsson wrote:

You are not really building from git if you are using apt-get package manager? I dont use ubuntu but I would suggest that you build it with make and sudo make install from git as described here: https://github.com/csound/csound/blob/develop/BUILD.md

2016-01-11 14:03 GMT+01:00 <brian@linuxsynths.com>:

Hi all,

I would like to do a new install to try out the new moog filters, but I get this error when doing build-dep:

E: Build-Depends dependency for csound cannot be satisfied because candidate version of package cdbs can't satisfy version requirements

 

Any advice much appreciated!

 

brian

 

Csound mailing list Csound@listserv.heanet.ie https://listserv.heanet.ie/cgi-bin/wa?A0=CSOUND Send bugs reports to https://github.com/csound/csound/issues Discussions of bugs and features can be posted here

Csound mailing list Csound@listserv.heanet.ie https://listserv.heanet.ie/cgi-bin/wa?A0=CSOUND Send bugs reports to https://github.com/csound/csound/issues Discussions of bugs and features can be posted here

 

 

Csound mailing list Csound@listserv.heanet.ie https://listserv.heanet.ie/cgi-bin/wa?A0=CSOUND Send bugs reports to https://github.com/csound/csound/issues Discussions of bugs and features can be posted here

Csound mailing list Csound@listserv.heanet.ie https://listserv.heanet.ie/cgi-bin/wa?A0=CSOUND Send bugs reports to https://github.com/csound/csound/issues Discussions of bugs and features can be posted here

Csound mailing list Csound@listserv.heanet.ie https://listserv.heanet.ie/cgi-bin/wa?A0=CSOUND Send bugs reports to https://github.com/csound/csound/issues Discussions of bugs and features can be posted here

Csound mailing list Csound@listserv.heanet.ie https://listserv.heanet.ie/cgi-bin/wa?A0=CSOUND Send bugs reports to https://github.com/csound/csound/issues Discussions of bugs and features can be posted here

Hi Tarmo,

thanks for the tips; I'll check the packages one-by-one and see how I fare, then post my results...

On Mon, 11 Jan 2016 21:34:11 +0200, Tarmo Johannes wrote:

Hi!

 

What distro and what version? I guess debian or ubuntu?

 

I am personally on openSuse and don't know exactly byt I guess cdbs is a kind of helping tool of debian packages. Can you see if there is a newer version available. Or if not you can install the necessary dependencies also with separate commands. See the necessary packages

 

under the csound Build.md Fedora guidelines:

https://github.com/csound/csound/blob/develop/BUILD.md#fedora

 

I guess for debian the development package names end with -dev not devel, but I am not sure. So you could do

apt-get install ladspa ladspa-devel fluidsynth fluidsynth-devel boost boost-devel java-devel etc

 

Don't worry, building from source can take time first time, but later is really easy.

 

Note that you need to checkout to git branch 'develop' to try out the newest state of development, master branch stays on the latest release state.

 

Hope it helps!

 

tarmo

 

 

 

On Monday 11 January 2016 14:03:07 you wrote:

> Hi all,

>

> I would like to do a new install to try out the new moog

> filters, but I get this error when doing build-dep:

>

> E: Build-Depends

> dependency for csound cannot be satisfied because candidate version of

> package cdbs can't satisfy version requirements

>

> Any advice much

> appreciated!

>

> brian

>

> Csound mailing list

> Csound@listserv.heanet.ie

> https://listserv.heanet.ie/cgi-bin/wa?A0=CSOUND

> Send bugs reports to

> https://github.com/csound/csound/issues

> Discussions of bugs and features can be posted here

 

Csound mailing list Csound@listserv.heanet.ie https://listserv.heanet.ie/cgi-bin/wa?A0=CSOUND Send bugs reports to https://github.com/csound/csound/issues Discussions of bugs and features can be posted here

Hi everyone,

I removed the (old, v.5.17) version I was using from the Bodhi repositories and only needed to install cmake, flex and bison. The git install went fine and I'm now testing Mr. Yi's "corny" demo of the newly-added Moog LPF! :D

Personally, I like the moogladder filter better. It has a quality to it that I can't find elsewhere. :)

brian

On Tue, 12 Jan 2016 00:22:55 +0100, brian@LINUXSYNTHS.COM wrote:

Hi Tarmo,

thanks for the tips; I'll check the packages one-by-one and see how I fare, then post my results...

 

On Mon, 11 Jan 2016 21:34:11 +0200, Tarmo Johannes wrote:

Hi!

 

What distro and what version? I guess debian or ubuntu?

 

I am personally on openSuse and don't know exactly byt I guess cdbs is a kind of helping tool of debian packages. Can you see if there is a newer version available. Or if not you can install the necessary dependencies also with separate commands. See the necessary packages

 

under the csound Build.md Fedora guidelines:

https://github.com/csound/csound/blob/develop/BUILD.md#fedora

 

I guess for debian the development package names end with -dev not devel, but I am not sure. So you could do

apt-get install ladspa ladspa-devel fluidsynth fluidsynth-devel boost boost-devel java-devel etc

 

Don't worry, building from source can take time first time, but later is really easy.

 

Note that you need to checkout to git branch 'develop' to try out the newest state of development, master branch stays on the latest release state.

 

Hope it helps!

 

tarmo

 

 

 

On Monday 11 January 2016 14:03:07 you wrote:

> Hi all,

>

> I would like to do a new install to try out the new moog

> filters, but I get this error when doing build-dep:

>

> E: Build-Depends

> dependency for csound cannot be satisfied because candidate version of

> package cdbs can't satisfy version requirements

>

> Any advice much

> appreciated!

>

> brian

>

> Csound mailing list

> Csound@listserv.heanet.ie

> https://listserv.heanet.ie/cgi-bin/wa?A0=CSOUND

> Send bugs reports to

> https://github.com/csound/csound/issues

> Discussions of bugs and features can be posted here

 

Csound mailing list Csound@listserv.heanet.ie https://listserv.heanet.ie/cgi-bin/wa?A0=CSOUND Send bugs reports to https://github.com/csound/csound/issues Discussions of bugs and features can be posted here

 

 

Csound mailing list Csound@listserv.heanet.ie https://listserv.heanet.ie/cgi-bin/wa?A0=CSOUND Send bugs reports to https://github.com/csound/csound/issues Discussions of bugs and features can be posted here

Hi again everyone,

so, the installation of Csound git version was a success-- but I can't open any csound instruments anymore!  I always get some error, each  instrument has "its own." Examples include: "define macro unexpected character )(0x29) awaiting #"  or  "error: syntax error, unexpected INTEGER_TOKEN  (token "103") from file SawSquareSynth.csd (1) line 14: >>>FLcolor      103 <<< Unexpected untyped word FLcolor when expecting a variable"  or  similar.

Note, that all these instruments work fine (and worked fine on the older 5.17 version).

Blah..

brian

On Tue, 12 Jan 2016 10:04:02 +0100, brian@LINUXSYNTHS.COM wrote:

Hi everyone,

I removed the (old, v.5.17) version I was using from the Bodhi repositories and only needed to install cmake, flex and bison. The git install went fine and I'm now testing Mr. Yi's "corny" demo of the newly-added Moog LPF! :D

Personally, I like the moogladder filter better. It has a quality to it that I can't find elsewhere. :)

 

brian

 

On Tue, 12 Jan 2016 00:22:55 +0100, brian@LINUXSYNTHS.COM wrote:

Hi Tarmo,

thanks for the tips; I'll check the packages one-by-one and see how I fare, then post my results...

 

On Mon, 11 Jan 2016 21:34:11 +0200, Tarmo Johannes wrote:

Hi!

 

What distro and what version? I guess debian or ubuntu?

 

I am personally on openSuse and don't know exactly byt I guess cdbs is a kind of helping tool of debian packages. Can you see if there is a newer version available. Or if not you can install the necessary dependencies also with separate commands. See the necessary packages

 

under the csound Build.md Fedora guidelines:

https://github.com/csound/csound/blob/develop/BUILD.md#fedora

 

I guess for debian the development package names end with -dev not devel, but I am not sure. So you could do

apt-get install ladspa ladspa-devel fluidsynth fluidsynth-devel boost boost-devel java-devel etc

 

Don't worry, building from source can take time first time, but later is really easy.

 

Note that you need to checkout to git branch 'develop' to try out the newest state of development, master branch stays on the latest release state.

 

Hope it helps!

 

tarmo

 

 

 

On Monday 11 January 2016 14:03:07 you wrote:

> Hi all,

>

> I would like to do a new install to try out the new moog

> filters, but I get this error when doing build-dep:

>

> E: Build-Depends

> dependency for csound cannot be satisfied because candidate version of

> package cdbs can't satisfy version requirements

>

> Any advice much

> appreciated!

>

> brian

>

> Csound mailing list

> Csound@listserv.heanet.ie

> https://listserv.heanet.ie/cgi-bin/wa?A0=CSOUND

> Send bugs reports to

> https://github.com/csound/csound/issues

> Discussions of bugs and features can be posted here

 

Csound mailing list Csound@listserv.heanet.ie https://listserv.heanet.ie/cgi-bin/wa?A0=CSOUND Send bugs reports to https://github.com/csound/csound/issues Discussions of bugs and features can be posted here

 

 

Csound mailing list Csound@listserv.heanet.ie https://listserv.heanet.ie/cgi-bin/wa?A0=CSOUND Send bugs reports to https://github.com/csound/csound/issues Discussions of bugs and features can be posted here

 

 

Csound mailing list Csound@listserv.heanet.ie https://listserv.heanet.ie/cgi-bin/wa?A0=CSOUND Send bugs reports to https://github.com/csound/csound/issues Discussions of bugs and features can be posted here

Could be that you didn't build the fltk opcodes. If you install and run cmake-gui from your Csound build dir you can enable our disable the building of any of these opcodes. It may not have built them breccias you dont have fltk installed. Cmake-gui will tell you more.

Hi Rory,

I'm not sure I understand. Which folder and which command?

Also, after I do what you said here, do I have to "purge" the old install before doing a make again?

brian

On Tue, 12 Jan 2016 20:49:02 +0000, Rory Walsh wrote:

Could be that you didn't build the fltk opcodes. If you install and run cmake-gui from your Csound build dir you can enable our disable the building of any of these opcodes. It may not have built them breccias you dont have fltk installed. Cmake-gui will tell you more.

On 12 Jan 2016 20:43, <brian@linuxsynths.com> wrote:

Hi again everyone,

so, the installation of Csound git version was a success-- but I can't open any csound instruments anymore!  I always get some error, each  instrument has "its own." Examples include: "define macro unexpected character )(0x29) awaiting #"  or  "error: syntax error, unexpected INTEGER_TOKEN  (token "103") from file SawSquareSynth.csd (1) line 14: >>>FLcolor      103 <<< Unexpected untyped word FLcolor when expecting a variable"  or  similar.

Note, that all these instruments work fine (and worked fine on the older 5.17 version).

Blah..

 

brian

 

On Tue, 12 Jan 2016 10:04:02 +0100, brian@LINUXSYNTHS.COM wrote:

Hi everyone,

I removed the (old, v.5.17) version I was using from the Bodhi repositories and only needed to install cmake, flex and bison. The git install went fine and I'm now testing Mr. Yi's "corny" demo of the newly-added Moog LPF! :D

Personally, I like the moogladder filter better. It has a quality to it that I can't find elsewhere. :)

 

brian

 

On Tue, 12 Jan 2016 00:22:55 +0100, brian@LINUXSYNTHS.COM wrote:

Hi Tarmo,

thanks for the tips; I'll check the packages one-by-one and see how I fare, then post my results...

 

On Mon, 11 Jan 2016 21:34:11 +0200, Tarmo Johannes wrote:

Hi!

 

What distro and what version? I guess debian or ubuntu?

 

I am personally on openSuse and don't know exactly byt I guess cdbs is a kind of helping tool of debian packages. Can you see if there is a newer version available. Or if not you can install the necessary dependencies also with separate commands. See the necessary packages

 

under the csound Build.md Fedora guidelines:

https://github.com/csound/csound/blob/develop/BUILD.md#fedora

 

I guess for debian the development package names end with -dev not devel, but I am not sure. So you could do

apt-get install ladspa ladspa-devel fluidsynth fluidsynth-devel boost boost-devel java-devel etc

 

Don't worry, building from source can take time first time, but later is really easy.

 

Note that you need to checkout to git branch 'develop' to try out the newest state of development, master branch stays on the latest release state.

 

Hope it helps!

 

tarmo

 

 

 

On Monday 11 January 2016 14:03:07 you wrote:

> Hi all,

>

> I would like to do a new install to try out the new moog

> filters, but I get this error when doing build-dep:

>

> E: Build-Depends

> dependency for csound cannot be satisfied because candidate version of

> package cdbs can't satisfy version requirements

>

> Any advice much

> appreciated!

>

> brian

>

> Csound mailing list

> Csound@listserv.heanet.ie

> https://listserv.heanet.ie/cgi-bin/wa?A0=CSOUND

> Send bugs reports to

> https://github.com/csound/csound/issues

> Discussions of bugs and features can be posted here

 

Csound mailing list Csound@listserv.heanet.ie https://listserv.heanet.ie/cgi-bin/wa?A0=CSOUND Send bugs reports to https://github.com/csound/csound/issues Discussions of bugs and features can be posted here

 

 

Csound mailing list Csound@listserv.heanet.ie https://listserv.heanet.ie/cgi-bin/wa?A0=CSOUND Send bugs reports to https://github.com/csound/csound/issues Discussions of bugs and features can be posted here

 

 

Csound mailing list Csound@listserv.heanet.ie https://listserv.heanet.ie/cgi-bin/wa?A0=CSOUND Send bugs reports to https://github.com/csound/csound/issues Discussions of bugs and features can be posted here

 

 

Csound mailing list Csound@listserv.heanet.ie https://listserv.heanet.ie/cgi-bin/wa?A0=CSOUND Send bugs reports to https://github.com/csound/csound/issues Discussions of bugs and features can be posted here

Csound mailing list Csound@listserv.heanet.ie https://listserv.heanet.ie/cgi-bin/wa?A0=CSOUND Send bugs reports to https://github.com/csound/csound/issues Discussions of bugs and features can be posted here

I'm not sure of the first problem but the second sounds like an issue with the fltk opcodes. You built Csound yourself from the instructions on the Csound git page? I assume you ran cmake at some point to generate your makefiles? Sorry, I'm trying to follow what steps you may have taken here! 

Anyhow, if you install cmake-gui and run it and select the Csound source folder along with the build folder, you should get a list of install build options. It's here that you can tweak the build settings. But you did build Csound yourself right? Otherwise this email, typed on a rather useless android phone with a screen smaller than most microorganisms has been a complete and utter waste of time!

No, your efforts have not been in vain, I guarantee! :)

I did indeed build from git, following the instructions in the Debian/Ubuntu section. However, since I couldn't build the dependencies, I installed three that I am sure are required: bison, curl and flex.  The Libsndfile is installed (in the repos here it is called libsndfile1, but there is also libsndfile-static).

Then I followed the build instructions, and all *seemed* to go well. When I go to open an instrument, Csound starts, but then gets an error and stops.

So where do I get the cmake-gui and how do I install it?   (sorry for my persistant noobie-ness..)

brian

PS: I'll check back tomorrow, it's pretty late here now..

On Tue, 12 Jan 2016 22:40:42 +0000, Rory Walsh wrote:

I'm not sure of the first problem but the second sounds like an issue with the fltk opcodes. You built Csound yourself from the instructions on the Csound git page? I assume you ran cmake at some point to generate your makefiles? Sorry, I'm trying to follow what steps you may have taken here! 

Anyhow, if you install cmake-gui and run it and select the Csound source folder along with the build folder, you should get a list of install build options. It's here that you can tweak the build settings. But you did build Csound yourself right? Otherwise this email, typed on a rather useless android phone with a screen smaller than most microorganisms has been a complete and utter waste of time!

On 12 Jan 2016 22:27, <brian@linuxsynths.com> wrote:

Hi Rory,

I'm not sure I understand. Which folder and which command?

Also, after I do what you said here, do I have to "purge" the old install before doing a make again?

 

brian

 

On Tue, 12 Jan 2016 20:49:02 +0000, Rory Walsh wrote:

Could be that you didn't build the fltk opcodes. If you install and run cmake-gui from your Csound build dir you can enable our disable the building of any of these opcodes. It may not have built them breccias you dont have fltk installed. Cmake-gui will tell you more.

On 12 Jan 2016 20:43, <brian@linuxsynths.com> wrote:

Hi again everyone,

so, the installation of Csound git version was a success-- but I can't open any csound instruments anymore!  I always get some error, each  instrument has "its own." Examples include: "define macro unexpected character )(0x29) awaiting #"  or  "error: syntax error, unexpected INTEGER_TOKEN  (token "103") from file SawSquareSynth.csd (1) line 14: >>>FLcolor      103 <<< Unexpected untyped word FLcolor when expecting a variable"  or  similar.

Note, that all these instruments work fine (and worked fine on the older 5.17 version).

Blah..

 

brian

 

On Tue, 12 Jan 2016 10:04:02 +0100, brian@LINUXSYNTHS.COM wrote:

Hi everyone,

I removed the (old, v.5.17) version I was using from the Bodhi repositories and only needed to install cmake, flex and bison. The git install went fine and I'm now testing Mr. Yi's "corny" demo of the newly-added Moog LPF! :D

Personally, I like the moogladder filter better. It has a quality to it that I can't find elsewhere. :)

 

brian

 

On Tue, 12 Jan 2016 00:22:55 +0100, brian@LINUXSYNTHS.COM wrote:

Hi Tarmo,

thanks for the tips; I'll check the packages one-by-one and see how I fare, then post my results...

 

On Mon, 11 Jan 2016 21:34:11 +0200, Tarmo Johannes wrote:

Hi!

 

What distro and what version? I guess debian or ubuntu?

 

I am personally on openSuse and don't know exactly byt I guess cdbs is a kind of helping tool of debian packages. Can you see if there is a newer version available. Or if not you can install the necessary dependencies also with separate commands. See the necessary packages

 

under the csound Build.md Fedora guidelines:

https://github.com/csound/csound/blob/develop/BUILD.md#fedora

 

I guess for debian the development package names end with -dev not devel, but I am not sure. So you could do

apt-get install ladspa ladspa-devel fluidsynth fluidsynth-devel boost boost-devel java-devel etc

 

Don't worry, building from source can take time first time, but later is really easy.

 

Note that you need to checkout to git branch 'develop' to try out the newest state of development, master branch stays on the latest release state.

 

Hope it helps!

 

tarmo

 

 

 

On Monday 11 January 2016 14:03:07 you wrote:

> Hi all,

>

> I would like to do a new install to try out the new moog

> filters, but I get this error when doing build-dep:

>

> E: Build-Depends

> dependency for csound cannot be satisfied because candidate version of

> package cdbs can't satisfy version requirements

>

> Any advice much

> appreciated!

>

> brian

>

> Csound mailing list

> Csound@listserv.heanet.ie

> https://listserv.heanet.ie/cgi-bin/wa?A0=CSOUND

> Send bugs reports to

> https://github.com/csound/csound/issues

> Discussions of bugs and features can be posted here

 

Csound mailing list Csound@listserv.heanet.ie https://listserv.heanet.ie/cgi-bin/wa?A0=CSOUND Send bugs reports to https://github.com/csound/csound/issues Discussions of bugs and features can be posted here

 

 

Csound mailing list Csound@listserv.heanet.ie https://listserv.heanet.ie/cgi-bin/wa?A0=CSOUND Send bugs reports to https://github.com/csound/csound/issues Discussions of bugs and features can be posted here

 

 

Csound mailing list Csound@listserv.heanet.ie https://listserv.heanet.ie/cgi-bin/wa?A0=CSOUND Send bugs reports to https://github.com/csound/csound/issues Discussions of bugs and features can be posted here

 

 

Csound mailing list Csound@listserv.heanet.ie https://listserv.heanet.ie/cgi-bin/wa?A0=CSOUND Send bugs reports to https://github.com/csound/csound/issues Discussions of bugs and features can be posted here

Csound mailing list Csound@listserv.heanet.ie https://listserv.heanet.ie/cgi-bin/wa?A0=CSOUND Send bugs reports to https://github.com/csound/csound/issues Discussions of bugs and features can be posted here

 

 

Csound mailing list Csound@listserv.heanet.ie https://listserv.heanet.ie/cgi-bin/wa?A0=CSOUND Send bugs reports to https://github.com/csound/csound/issues Discussions of bugs and features can be posted here

Csound mailing list Csound@listserv.heanet.ie https://listserv.heanet.ie/cgi-bin/wa?A0=CSOUND Send bugs reports to https://github.com/csound/csound/issues Discussions of bugs and features can be posted here

Hi, some guesses:

- did you do

$ sudo ldconfig

to let the system know about new libraries?

- did you set the OPCODE6DIR64 evironment variable (if you had Csound 5 before, this is needed for Csound6). Run in terminal before starting csound:

export OPCODE6DIR64=/usr/local/lib/csound/plugins64-6.0/

#or where your Csound6 plugins are installed

or better if you add this line to $HOME/.bashrc logout and log in again

- are you perhaps trying it via old CsoundQt? If that was built against Csound5 you probably need to rebuild CsoundQt as well. See instructions on:

https://github.com/csound/csound/wiki/CsoundQt-with-Csound6-on-Debian-Ubuntu:-a-build-guide

https://github.com/csound/csound/wiki/Compiling-CsoundQT-for-Fedora-22-w-Python-and-RTmidi-support

Hope it helps!

tarmo

On Wednesday 13 January 2016 00:02:28 you wrote:

> No, your efforts have not been in vain, I guarantee! :)

>

> I did

> indeed build from git, following the instructions in the Debian/Ubuntu

> section. However, since I couldn't build the dependencies, I installed

> three that I am sure are required: bison, curl and flex. The Libsndfile

> is installed (in the repos here it is called libsndfile1, but there is

> also libsndfile-static).

>

> Then I followed the build instructions, and

> all *seemed* to go well. When I go to open an instrument, Csound starts,

> but then gets an error and stops.

>

> So where do I get the cmake-gui and

> how do I install it? (sorry for my persistant noobie-ness..)

>

> brian

>

>

> PS: I'll check back tomorrow, it's pretty late here now..

>

> On Tue, 12

>

> Jan 2016 22:40:42 +0000, Rory Walsh wrote:

> > I'm not sure of the first

>

> problem but the second sounds like an issue with the fltk opcodes. You

> built Csound yourself from the instructions on the Csound git page? I

> assume you ran cmake at some point to generate your makefiles? Sorry,

> I'm trying to follow what steps you may have taken here!

>

> > Anyhow,

>

> if you install cmake-gui and run it and select the Csound source folder

> along with the build folder, you should get a list of install build

> options. It's here that you can tweak the build settings. But you did

> build Csound yourself right? Otherwise this email, typed on a rather

> useless android phone with a screen smaller than most microorganisms has

> been a complete and utter waste of time!

>

> > On 12 Jan 2016 22:27,

>

> wrote:

> >> Hi Rory,

> >>

> >> I'm not sure I understand. Which folder

>

> and which command?

>

> >> Also, after I do what you said here, do I

>

> have to "purge" the old install before doing a make again?

>

> >> brian

>

> >> On Tue, 12 Jan 2016 20:49:02 +0000, Rory Walsh wrote:

> Could be that you didn't build the fltk opcodes. If you install and run

> cmake-gui from your Csound build dir you can enable our disable the

> building of any of these opcodes. It may not have built them breccias

> you dont have fltk installed. Cmake-gui will tell you more.

>

> >>> On 12

>

> Jan 2016 20:43, wrote:

> >>>> Hi again everyone,

> >>>>

> >>>> so, the

>

> installation of Csound git version was a success-- but I can't open any

> csound instruments anymore! I always get some error, each instrument has

> "its own." Examples include: "define macro unexpected character )(0x29)

> awaiting #" or "error: syntax error, unexpected INTEGER_TOKEN (token

> "103") from file SawSquareSynth.csd (1) line 14: >>>FLcolor 103

>

> Csound mailing list Csound@listserv.heanet.ie [20]

> https://listserv.heanet.ie/cgi-bin/wa?A0=CSOUND [21] Send bugs reports

> to https://github.com/csound/csound/issues [22] Discussions of bugs and

> features can be posted here

>

> >> Csound mailing list

>

> Csound@listserv.heanet.ie [23]

> https://listserv.heanet.ie/cgi-bin/wa?A0=CSOUND [24] Send bugs reports

> to https://github.com/csound/csound/issues [25] Discussions of bugs and

> features can be posted here

>

> > Csound mailing list

>

> Csound@listserv.heanet.ie [27]

> https://listserv.heanet.ie/cgi-bin/wa?A0=CSOUND [28] Send bugs reports

> to https://github.com/csound/csound/issues [29] Discussions of bugs and

> features can be posted here

>

>

>

> Links:

> ------

> [1]

> https://github.com/csound/csound/blob/develop/BUILD.md#fedora

> [2]

> mailto:Csound@listserv.heanet.ie

> [3]

> https://listserv.heanet.ie/cgi-bin/wa?A0=CSOUND

> [4]

> https://github.com/csound/csound/issues

> [5]

> mailto:Csound@listserv.heanet.ie

> [6]

> https://listserv.heanet.ie/cgi-bin/wa?A0=CSOUND

> [7]

> https://github.com/csound/csound/issues

> [8]

> mailto:Csound@listserv.heanet.ie

> [9]

> https://listserv.heanet.ie/cgi-bin/wa?A0=CSOUND

> [10]

> https://github.com/csound/csound/issues

> [11]

> mailto:brian@LINUXSYNTHS.COM

> [12] mailto:Csound@listserv.heanet.ie

> [13]

> https://listserv.heanet.ie/cgi-bin/wa?A0=CSOUND

> [14]

> https://github.com/csound/csound/issues

> [15]

> mailto:brian@LINUXSYNTHS.COM

> [16] mailto:Csound@listserv.heanet.ie

> [17]

> https://listserv.heanet.ie/cgi-bin/wa?A0=CSOUND

> [18]

> https://github.com/csound/csound/issues

> [19]

> mailto:brian@linuxsynths.com

> [20] mailto:Csound@listserv.heanet.ie

> [21]

> https://listserv.heanet.ie/cgi-bin/wa?A0=CSOUND

> [22]

> https://github.com/csound/csound/issues

> [23]

> mailto:Csound@listserv.heanet.ie

> [24]

> https://listserv.heanet.ie/cgi-bin/wa?A0=CSOUND

> [25]

> https://github.com/csound/csound/issues

> [26]

> mailto:brian@linuxsynths.com

> [27] mailto:Csound@listserv.heanet.ie

> [28]

> https://listserv.heanet.ie/cgi-bin/wa?A0=CSOUND

> [29]

> https://github.com/csound/csound/issues

>

> Csound mailing list

> Csound@listserv.heanet.ie

> https://listserv.heanet.ie/cgi-bin/wa?A0=CSOUND

> Send bugs reports to

> https://github.com/csound/csound/issues

> Discussions of bugs and features can be posted here

Hi Tarmo,

Yes, I did sudo ldconfig; I did not set the OPCODE6DIR64 variable. Is this for 64-bit systems? (mine is 32-bit)

I installed fltk from source (unzipped the tarball in the csound directory) and did a re-make, but I still get this type of error:

0dBFS level = 32768.0
Csound version 6.07 (double samples) Jan 12 2016
libsndfile-1.0.25
UnifiedCSD:  MonoPolySynthII.csd
STARTING FILE
Creating options
Creating orchestra
Creating score
rtmidi: ALSA Raw MIDI module enabled
rtaudio: JACK module enabled
define macro unexpected character )(0x29) awaiting #

cannot compile orchestra
end of score.              overall amps:      0.0
           overall samples out of range:        0
2 errors in performance

----

brian

On Wed, 13 Jan 2016 08:34:47 +0200, Tarmo Johannes wrote:

Hi, some guesses:

 

- did you do

$ sudo ldconfig

to let the system know about new libraries?

 

- did you set the OPCODE6DIR64 evironment variable (if you had Csound 5 before, this is needed for Csound6). Run in terminal before starting csound:

export OPCODE6DIR64=/usr/local/lib/csound/plugins64-6.0/

#or where your Csound6 plugins are installed

or better if you add this line to $HOME/.bashrc logout and log in again

 

- are you perhaps trying it via old CsoundQt? If that was built against Csound5 you probably need to rebuild CsoundQt as well. See instructions on:

https://github.com/csound/csound/wiki/CsoundQt-with-Csound6-on-Debian-Ubuntu:-a-build-guide

https://github.com/csound/csound/wiki/Compiling-CsoundQT-for-Fedora-22-w-Python-and-RTmidi-support

 

Hope it helps!

 

tarmo

 

 

On Wednesday 13 January 2016 00:02:28 you wrote:

> No, your efforts have not been in vain, I guarantee! :)

>

> I did

> indeed build from git, following the instructions in the Debian/Ubuntu

> section. However, since I couldn't build the dependencies, I installed

> three that I am sure are required: bison, curl and flex. The Libsndfile

> is installed (in the repos here it is called libsndfile1, but there is

> also libsndfile-static).

>

> Then I followed the build instructions, and

> all *seemed* to go well. When I go to open an instrument, Csound starts,

> but then gets an error and stops.

>

> So where do I get the cmake-gui and

> how do I install it? (sorry for my persistant noobie-ness..)

>

> brian

>

>

> PS: I'll check back tomorrow, it's pretty late here now..

>

> On Tue, 12

>

> Jan 2016 22:40:42 +0000, Rory Walsh wrote:

> > I'm not sure of the first

>

> problem but the second sounds like an issue with the fltk opcodes. You

> built Csound yourself from the instructions on the Csound git page? I

> assume you ran cmake at some point to generate your makefiles? Sorry,

> I'm trying to follow what steps you may have taken here!

>

> > Anyhow,

>

> if you install cmake-gui and run it and select the Csound source folder

> along with the build folder, you should get a list of install build

> options. It's here that you can tweak the build settings. But you did

> build Csound yourself right? Otherwise this email, typed on a rather

> useless android phone with a screen smaller than most microorganisms has

> been a complete and utter waste of time!

>

> > On 12 Jan 2016 22:27,

>

> wrote:

> >> Hi Rory,

> >>

> >> I'm not sure I understand. Which folder

>

> and which command?

>

> >> Also, after I do what you said here, do I

>

> have to "purge" the old install before doing a make again?

>

> >> brian

>

> >> On Tue, 12 Jan 2016 20:49:02 +0000, Rory Walsh wrote:

> Could be that you didn't build the fltk opcodes. If you install and run

> cmake-gui from your Csound build dir you can enable our disable the

> building of any of these opcodes. It may not have built them breccias

> you dont have fltk installed. Cmake-gui will tell you more.

>

> >>> On 12

>

> Jan 2016 20:43, wrote:

> >>>> Hi again everyone,

> >>>>

> >>>> so, the

>

> installation of Csound git version was a success-- but I can't open any

> csound instruments anymore! I always get some error, each instrument has

> "its own." Examples include: "define macro unexpected character )(0x29)

> awaiting #" or "error: syntax error, unexpected INTEGER_TOKEN (token

> "103") from file SawSquareSynth.csd (1) line 14: >>>FLcolor 103

>

> Csound mailing list Csound@listserv.heanet.ie [20]

> https://listserv.heanet.ie/cgi-bin/wa?A0=CSOUND [21] Send bugs reports

> to https://github.com/csound/csound/issues [22] Discussions of bugs and

> features can be posted here

>

> >> Csound mailing list

>

> Csound@listserv.heanet.ie [23]

> https://listserv.heanet.ie/cgi-bin/wa?A0=CSOUND [24] Send bugs reports

> to https://github.com/csound/csound/issues [25] Discussions of bugs and

> features can be posted here

>

> > Csound mailing list

>

> Csound@listserv.heanet.ie [27]

> https://listserv.heanet.ie/cgi-bin/wa?A0=CSOUND [28] Send bugs reports

> to https://github.com/csound/csound/issues [29] Discussions of bugs and

> features can be posted here

>

>

>

> Links:

> ------

> [1]

> https://github.com/csound/csound/blob/develop/BUILD.md#fedora

> [2]

> mailto:Csound@listserv.heanet.ie

> [3]

> https://listserv.heanet.ie/cgi-bin/wa?A0=CSOUND

> [4]

> https://github.com/csound/csound/issues

> [5]

> mailto:Csound@listserv.heanet.ie

> [6]

> https://listserv.heanet.ie/cgi-bin/wa?A0=CSOUND

> [7]

> https://github.com/csound/csound/issues

> [8]

> mailto:Csound@listserv.heanet.ie

> [9]

> https://listserv.heanet.ie/cgi-bin/wa?A0=CSOUND

> [10]

> https://github.com/csound/csound/issues

> [11]

> mailto:brian@LINUXSYNTHS.COM

> [12] mailto:Csound@listserv.heanet.ie

> [13]

> https://listserv.heanet.ie/cgi-bin/wa?A0=CSOUND

> [14]

> https://github.com/csound/csound/issues

> [15]

> mailto:brian@LINUXSYNTHS.COM

> [16] mailto:Csound@listserv.heanet.ie

> [17]

> https://listserv.heanet.ie/cgi-bin/wa?A0=CSOUND

> [18]

> https://github.com/csound/csound/issues

> [19]

> mailto:brian@linuxsynths.com

> [20] mailto:Csound@listserv.heanet.ie

> [21]

> https://listserv.heanet.ie/cgi-bin/wa?A0=CSOUND

> [22]

> https://github.com/csound/csound/issues

> [23]

> mailto:Csound@listserv.heanet.ie

> [24]

> https://listserv.heanet.ie/cgi-bin/wa?A0=CSOUND

> [25]

> https://github.com/csound/csound/issues

> [26]

> mailto:brian@linuxsynths.com

> [27] mailto:Csound@listserv.heanet.ie

> [28]

> https://listserv.heanet.ie/cgi-bin/wa?A0=CSOUND

> [29]

> https://github.com/csound/csound/issues

>

> Csound mailing list

> Csound@listserv.heanet.ie

> https://listserv.heanet.ie/cgi-bin/wa?A0=CSOUND

> Send bugs reports to

> https://github.com/csound/csound/issues

> Discussions of bugs and features can be posted here

 

Csound mailing list Csound@listserv.heanet.ie https://listserv.heanet.ie/cgi-bin/wa?A0=CSOUND Send bugs reports to https://github.com/csound/csound/issues Discussions of bugs and features can be posted here

CsoundQt or command line? Can you get some very simple csd work from command line?
64bit is for Csound, how exact numbers it uses, not architecture. So 32bit system is fine.
T

OPCODE6DIR64 is for double build rather than floats

What input are you using?  I suspect a nalformed definiton ttemt


On Wed, 13 Jan 2016, brian@LINUXSYNTHS.COM wrote:

> 
> Hi Tarmo,
> 
> Yes, I did sudo ldconfig; I did not set the OPCODE6DIR64 variable. Is this
> for 64-bit systems? (mine is 32-bit)
> 
> I installed fltk from source (unzipped the tarball in the csound directory)
> and did a re-make, but I still get this type of error:
> 
> 0dBFS level = 32768.0
> Csound version 6.07 (double samples) Jan 12 2016
> libsndfile-1.0.25
> UnifiedCSD:  MonoPolySynthII.csd
> STARTING FILE
> Creating options
> Creating orchestra
> Creating score
> rtmidi: ALSA Raw MIDI module enabled
> rtaudio: JACK module enabled
> define macro unexpected character )(0x29) awaiting #
> 
> cannot compile orchestra
> end of score.              overall amps:      0.0
>            overall samples out of range:        0
> 2 errors in performance
> 
>  
> 
> ----
> 
> brian
> 
>  
> 
>  
> 
> On Wed, 13 Jan 2016 08:34:47 +0200, Tarmo Johannes wrote:
>
>       Hi, some guesses:
>
>        
>
>       - did you do
>
>       $ sudo ldconfig
>
>       to let the system know about new libraries?
>
>        
>
>       - did you set the OPCODE6DIR64 evironment variable (if you had
>       Csound 5 before, this is needed for Csound6). Run in terminal
>       before starting csound:
>
>       export OPCODE6DIR64=/usr/local/lib/csound/plugins64-6.0/
>
>       #or where your Csound6 plugins are installed
>
>       or better if you add this line to $HOME/.bashrc logout and log
>       in again
>
>        
>
>       - are you perhaps trying it via old CsoundQt? If that was built
>       against Csound5 you probably need to rebuild CsoundQt as well.
>       See instructions on:
> 
> https://github.com/csound/csound/wiki/CsoundQt-with-Csound6-on-Debian-Ubunt
>       u:-a-build-guide
> 
> https://github.com/csound/csound/wiki/Compiling-CsoundQT-for-Fedora-22-w-Py
>       thon-and-RTmidi-support
>
>        
>
>       Hope it helps!
>
>        
>
>       tarmo
>
>        
>
>        
>
>       On Wednesday 13 January 2016 00:02:28 you wrote:
>
>       > No, your efforts have not been in vain, I guarantee! :)
>
>       >
>
>       > I did
>
>       > indeed build from git, following the instructions in the
>       Debian/Ubuntu
>
>       > section. However, since I couldn't build the dependencies, I
>       installed
>
>       > three that I am sure are required: bison, curl and flex. The
>       Libsndfile
>
>       > is installed (in the repos here it is called libsndfile1, but
>       there is
>
>       > also libsndfile-static).
>
>       >
>
>       > Then I followed the build instructions, and
>
>       > all *seemed* to go well. When I go to open an instrument,
>       Csound starts,
>
>       > but then gets an error and stops.
>
>       >
>
>       > So where do I get the cmake-gui and
>
>       > how do I install it? (sorry for my persistant noobie-ness..)
>
>       >
>
>       > brian
>
>       >
>
>       >
>
>       > PS: I'll check back tomorrow, it's pretty late here now..
>
>       >
>
>       > On Tue, 12
>
>       >
>
>       > Jan 2016 22:40:42 +0000, Rory Walsh wrote:
>
>       > > I'm not sure of the first
>
>       >
>
>       > problem but the second sounds like an issue with the fltk
>       opcodes. You
>
>       > built Csound yourself from the instructions on the Csound git
>       page? I
>
>       > assume you ran cmake at some point to generate your makefiles?
>       Sorry,
>
>       > I'm trying to follow what steps you may have taken here!
>
>       >
>
>       > > Anyhow,
>
>       >
>
>       > if you install cmake-gui and run it and select the Csound
>       source folder
>
>       > along with the build folder, you should get a list of install
>       build
>
>       > options. It's here that you can tweak the build settings. But
>       you did
>
>       > build Csound yourself right? Otherwise this email, typed on a
>       rather
>
>       > useless android phone with a screen smaller than most
>       microorganisms has
>
>       > been a complete and utter waste of time!
>
>       >
>
>       > > On 12 Jan 2016 22:27,
>
>       >
>
>       > wrote:
>
>       > >> Hi Rory,
>
>       > >>
>
>       > >> I'm not sure I understand. Which folder
>
>       >
>
>       > and which command?
>
>       >
>
>       > >> Also, after I do what you said here, do I
>
>       >
>
>       > have to "purge" the old install before doing a make again?
>
>       >
>
>       > >> brian
>
>       >
>
>       > >> On Tue, 12 Jan 2016 20:49:02 +0000, Rory Walsh wrote:
>
>       > Could be that you didn't build the fltk opcodes. If you
>       install and run
>
>       > cmake-gui from your Csound build dir you can enable our
>       disable the
>
>       > building of any of these opcodes. It may not have built them
>       breccias
>
>       > you dont have fltk installed. Cmake-gui will tell you more.
>
>       >
>
>       > >>> On 12
>
>       >
>
>       > Jan 2016 20:43, wrote:
>
>       > >>>> Hi again everyone,
>
>       > >>>>
>
>       > >>>> so, the
>
>       >
>
>       > installation of Csound git version was a success-- but I can't
>       open any
>
>       > csound instruments anymore! I always get some error, each
>       instrument has
>
>       > "its own." Examples include: "define macro unexpected
>       character )(0x29)
>
>       > awaiting #" or "error: syntax error, unexpected INTEGER_TOKEN
>       (token
>
>       > "103") from file SawSquareSynth.csd (1) line 14: >>>FLcolor
>       103
>
>       >
>
>       > Csound mailing list Csound@listserv.heanet.ie [20]
>
>       > https://listserv.heanet.ie/cgi-bin/wa?A0=CSOUND [21] Send bugs
>       reports
>
>       > to https://github.com/csound/csound/issues [22] Discussions of
>       bugs and
>
>       > features can be posted here
>
>       >
>
>       > >> Csound mailing list
>
>       >
>
>       > Csound@listserv.heanet.ie [23]
>
>       > https://listserv.heanet.ie/cgi-bin/wa?A0=CSOUND [24] Send bugs
>       reports
>
>       > to https://github.com/csound/csound/issues [25] Discussions of
>       bugs and
>
>       > features can be posted here
>
>       >
>
>       > > Csound mailing list
>
>       >
>
>       > Csound@listserv.heanet.ie [27]
>
>       > https://listserv.heanet.ie/cgi-bin/wa?A0=CSOUND [28] Send bugs
>       reports
>
>       > to https://github.com/csound/csound/issues [29] Discussions of
>       bugs and
>
>       > features can be posted here
>
>       >
>
>       >
>
>       >
>
>       > Links:
>
>       > ------
>
>       > [1]
>
>       > https://github.com/csound/csound/blob/develop/BUILD.md#fedora
>
>       > [2]
>
>       > mailto:Csound@listserv.heanet.ie
>
>       > [3]
>
>       > https://listserv.heanet.ie/cgi-bin/wa?A0=CSOUND
>
>       > [4]
>
>       > https://github.com/csound/csound/issues
>
>       > [5]
>
>       > mailto:Csound@listserv.heanet.ie
>
>       > [6]
>
>       > https://listserv.heanet.ie/cgi-bin/wa?A0=CSOUND
>
>       > [7]
>
>       > https://github.com/csound/csound/issues
>
>       > [8]
>
>       > mailto:Csound@listserv.heanet.ie
>
>       > [9]
>
>       > https://listserv.heanet.ie/cgi-bin/wa?A0=CSOUND
>
>       > [10]
>
>       > https://github.com/csound/csound/issues
>
>       > [11]
>
>       > mailto:brian@LINUXSYNTHS.COM
>
>       > [12] mailto:Csound@listserv.heanet.ie
>
>       > [13]
>
>       > https://listserv.heanet.ie/cgi-bin/wa?A0=CSOUND
>
>       > [14]
>
>       > https://github.com/csound/csound/issues
>
>       > [15]
>
>       > mailto:brian@LINUXSYNTHS.COM
>
>       > [16] mailto:Csound@listserv.heanet.ie
>
>       > [17]
>
>       > https://listserv.heanet.ie/cgi-bin/wa?A0=CSOUND
>
>       > [18]
>
>       > https://github.com/csound/csound/issues
>
>       > [19]
>
>       > mailto:brian@linuxsynths.com
>
>       > [20] mailto:Csound@listserv.heanet.ie
>
>       > [21]
>
>       > https://listserv.heanet.ie/cgi-bin/wa?A0=CSOUND
>
>       > [22]
>
>       > https://github.com/csound/csound/issues
>
>       > [23]
>
>       > mailto:Csound@listserv.heanet.ie
>
>       > [24]
>
>       > https://listserv.heanet.ie/cgi-bin/wa?A0=CSOUND
>
>       > [25]
>
>       > https://github.com/csound/csound/issues
>
>       > [26]
>
>       > mailto:brian@linuxsynths.com
>
>       > [27] mailto:Csound@listserv.heanet.ie
>
>       > [28]
>
>       > https://listserv.heanet.ie/cgi-bin/wa?A0=CSOUND
>
>       > [29]
>
>       > https://github.com/csound/csound/issues
>
>       >
>
>       > Csound mailing list
>
>       > Csound@listserv.heanet.ie
>
>       > https://listserv.heanet.ie/cgi-bin/wa?A0=CSOUND
>
>       > Send bugs reports to
>
>       > https://github.com/csound/csound/issues
>
>       > Discussions of bugs and features can be posted here
>
>        
>
>       Csound mailing list Csound@listserv.heanet.ie
>       https://listserv.heanet.ie/cgi-bin/wa?A0=CSOUND Send bugs
>       reports to https://github.com/csound/csound/issues Discussions
>       of bugs and features can be posted here
> 
>  
> 
>  
> Csound mailing list Csound@listserv.heanet.ie
> https://listserv.heanet.ie/cgi-bin/wa?A0=CSOUND Send bugs reports to
> https://github.com/csound/csound/issues Discussions of bugs and features can
> be posted here
>

Csound mailing list
Csound@listserv.heanet.ie
https://listserv.heanet.ie/cgi-bin/wa?A0=CSOUND
Send bugs reports to
        https://github.com/csound/csound/issues
Discussions of bugs and features can be posted here

At the moment I'm using just the command line, not CsoundQT.

What is the full line I should add to .bashrc  and where in the file should I paste it?

On Wed, 13 Jan 2016 12:28:17 +0200, Tarmo Johannes wrote:

CsoundQt or command line? Can you get some very simple csd work from command line?
64bit is for Csound, how exact numbers it uses, not architecture. So 32bit system is fine.
T

13.01.2016 12:23 kirjutas kuupäeval <brian@linuxsynths.com>:

Hi Tarmo,

Yes, I did sudo ldconfig; I did not set the OPCODE6DIR64 variable. Is this for 64-bit systems? (mine is 32-bit)

I installed fltk from source (unzipped the tarball in the csound directory) and did a re-make, but I still get this type of error:

0dBFS level = 32768.0
Csound version 6.07 (double samples) Jan 12 2016
libsndfile-1.0.25
UnifiedCSD:  MonoPolySynthII.csd
STARTING FILE
Creating options
Creating orchestra
Creating score
rtmidi: ALSA Raw MIDI module enabled
rtaudio: JACK module enabled
define macro unexpected character )(0x29) awaiting #

cannot compile orchestra
end of score.              overall amps:      0.0
           overall samples out of range:        0
2 errors in performance

 

----

brian

 

 

On Wed, 13 Jan 2016 08:34:47 +0200, Tarmo Johannes wrote:

Hi, some guesses:

 

- did you do

$ sudo ldconfig

to let the system know about new libraries?

 

- did you set the OPCODE6DIR64 evironment variable (if you had Csound 5 before, this is needed for Csound6). Run in terminal before starting csound:

export OPCODE6DIR64=/usr/local/lib/csound/plugins64-6.0/

#or where your Csound6 plugins are installed

or better if you add this line to $HOME/.bashrc logout and log in again

 

- are you perhaps trying it via old CsoundQt? If that was built against Csound5 you probably need to rebuild CsoundQt as well. See instructions on:

https://github.com/csound/csound/wiki/CsoundQt-with-Csound6-on-Debian-Ubuntu:-a-build-guide

https://github.com/csound/csound/wiki/Compiling-CsoundQT-for-Fedora-22-w-Python-and-RTmidi-support

 

Hope it helps!

 

tarmo

 

 

On Wednesday 13 January 2016 00:02:28 you wrote:

> No, your efforts have not been in vain, I guarantee! :)

>

> I did

> indeed build from git, following the instructions in the Debian/Ubuntu

> section. However, since I couldn't build the dependencies, I installed

> three that I am sure are required: bison, curl and flex. The Libsndfile

> is installed (in the repos here it is called libsndfile1, but there is

> also libsndfile-static).

>

> Then I followed the build instructions, and

> all *seemed* to go well. When I go to open an instrument, Csound starts,

> but then gets an error and stops.

>

> So where do I get the cmake-gui and

> how do I install it? (sorry for my persistant noobie-ness..)

>

> brian

>

>

> PS: I'll check back tomorrow, it's pretty late here now..

>

> On Tue, 12

>

> Jan 2016 22:40:42 +0000, Rory Walsh wrote:

> > I'm not sure of the first

>

> problem but the second sounds like an issue with the fltk opcodes. You

> built Csound yourself from the instructions on the Csound git page? I

> assume you ran cmake at some point to generate your makefiles? Sorry,

> I'm trying to follow what steps you may have taken here!

>

> > Anyhow,

>

> if you install cmake-gui and run it and select the Csound source folder

> along with the build folder, you should get a list of install build

> options. It's here that you can tweak the build settings. But you did

> build Csound yourself right? Otherwise this email, typed on a rather

> useless android phone with a screen smaller than most microorganisms has

> been a complete and utter waste of time!

>

> > On 12 Jan 2016 22:27,

>

> wrote:

> >> Hi Rory,

> >>

> >> I'm not sure I understand. Which folder

>

> and which command?

>

> >> Also, after I do what you said here, do I

>

> have to "purge" the old install before doing a make again?

>

> >> brian

>

> >> On Tue, 12 Jan 2016 20:49:02 +0000, Rory Walsh wrote:

> Could be that you didn't build the fltk opcodes. If you install and run

> cmake-gui from your Csound build dir you can enable our disable the

> building of any of these opcodes. It may not have built them breccias

> you dont have fltk installed. Cmake-gui will tell you more.

>

> >>> On 12

>

> Jan 2016 20:43, wrote:

> >>>> Hi again everyone,

> >>>>

> >>>> so, the

>

> installation of Csound git version was a success-- but I can't open any

> csound instruments anymore! I always get some error, each instrument has

> "its own." Examples include: "define macro unexpected character )(0x29)

> awaiting #" or "error: syntax error, unexpected INTEGER_TOKEN (token

> "103") from file SawSquareSynth.csd (1) line 14: >>>FLcolor 103

>

> Csound mailing list Csound@listserv.heanet.ie [20]

> https://listserv.heanet.ie/cgi-bin/wa?A0=CSOUND [21] Send bugs reports

> to https://github.com/csound/csound/issues [22] Discussions of bugs and

> features can be posted here

>

> >> Csound mailing list

>

> Csound@listserv.heanet.ie [23]

> https://listserv.heanet.ie/cgi-bin/wa?A0=CSOUND [24] Send bugs reports

> to https://github.com/csound/csound/issues [25] Discussions of bugs and

> features can be posted here

>

> > Csound mailing list

>

> Csound@listserv.heanet.ie [27]

> https://listserv.heanet.ie/cgi-bin/wa?A0=CSOUND [28] Send bugs reports

> to https://github.com/csound/csound/issues [29] Discussions of bugs and

> features can be posted here

>

>

>

> Links:

> ------

> [1]

> https://github.com/csound/csound/blob/develop/BUILD.md#fedora

> [2]

> mailto:Csound@listserv.heanet.ie

> [3]

> https://listserv.heanet.ie/cgi-bin/wa?A0=CSOUND

> [4]

> https://github.com/csound/csound/issues

> [5]

> mailto:Csound@listserv.heanet.ie

> [6]

> https://listserv.heanet.ie/cgi-bin/wa?A0=CSOUND

> [7]

> https://github.com/csound/csound/issues

> [8]

> mailto:Csound@listserv.heanet.ie

> [9]

> https://listserv.heanet.ie/cgi-bin/wa?A0=CSOUND

> [10]

> https://github.com/csound/csound/issues

> [11]

> mailto:brian@LINUXSYNTHS.COM

> [12] mailto:Csound@listserv.heanet.ie

> [13]

> https://listserv.heanet.ie/cgi-bin/wa?A0=CSOUND

> [14]

> https://github.com/csound/csound/issues

> [15]

> mailto:brian@LINUXSYNTHS.COM

> [16] mailto:Csound@listserv.heanet.ie

> [17]

> https://listserv.heanet.ie/cgi-bin/wa?A0=CSOUND

> [18]

> https://github.com/csound/csound/issues

> [19]

> mailto:brian@linuxsynths.com

> [20] mailto:Csound@listserv.heanet.ie

> [21]

> https://listserv.heanet.ie/cgi-bin/wa?A0=CSOUND

> [22]

> https://github.com/csound/csound/issues

> [23]

> mailto:Csound@listserv.heanet.ie

> [24]

> https://listserv.heanet.ie/cgi-bin/wa?A0=CSOUND

> [25]

> https://github.com/csound/csound/issues

> [26]

> mailto:brian@linuxsynths.com

> [27] mailto:Csound@listserv.heanet.ie

> [28]

> https://listserv.heanet.ie/cgi-bin/wa?A0=CSOUND

> [29]

> https://github.com/csound/csound/issues

>

> Csound mailing list

> Csound@listserv.heanet.ie

> https://listserv.heanet.ie/cgi-bin/wa?A0=CSOUND

> Send bugs reports to

> https://github.com/csound/csound/issues

> Discussions of bugs and features can be posted here

 

Csound mailing list Csound@listserv.heanet.ie https://listserv.heanet.ie/cgi-bin/wa?A0=CSOUND Send bugs reports to https://github.com/csound/csound/issues Discussions of bugs and features can be posted here

 

 

Csound mailing list Csound@listserv.heanet.ie https://listserv.heanet.ie/cgi-bin/wa?A0=CSOUND Send bugs reports to https://github.com/csound/csound/issues Discussions of bugs and features can be posted here

Csound mailing list Csound@listserv.heanet.ie https://listserv.heanet.ie/cgi-bin/wa?A0=CSOUND Send bugs reports to https://github.com/csound/csound/issues Discussions of bugs and features can be posted here

I just run  "csound [instrument].csd"   Of course, making sure that the options section complies with my audio setup..

On Wed, 13 Jan 2016 10:30:52 +0000, jpff wrote:

OPCODE6DIR64 is for double build rather than floats

What input are you using?  I suspect a nalformed definiton ttemt


On Wed, 13 Jan 2016, brian@LINUXSYNTHS.COMwrote:

Hi Tarmo, Yes, I did sudo ldconfig; I did not set the OPCODE6DIR64 variable. Is this for 64-bit systems? (mine is 32-bit) I installed fltk from source (unzipped the tarball in the csound directory) and did a re-make, but I still get this type of error: 0dBFS level = 32768.0 Csound version 6.07 (double samples) Jan 12 2016 libsndfile-1.0.25 UnifiedCSD:  MonoPolySynthII.csd STARTING FILE Creating options Creating orchestra Creating score rtmidi: ALSA Raw MIDI module enabled rtaudio: JACK module enabled define macro unexpected character )(0x29) awaiting # cannot compile orchestra end of score.              overall amps:      0.0            overall samples out of range:        0 2 errors in performance   ---- brian     On Wed, 13 Jan 2016 08:34:47 +0200, Tarmo Johannes wrote: Hi, some guesses:   - did you do $ sudo ldconfig to let the system know about new libraries?   - did you set the OPCODE6DIR64 evironment variable (if you had Csound 5 before, this is needed for Csound6). Run in terminal before starting csound: export OPCODE6DIR64=/usr/local/lib/csound/plugins64-6.0/ #or where your Csound6 plugins are installed or better if you add this line to $HOME/.bashrc logout and log in again   - are you perhaps trying it via old CsoundQt? If that was built against Csound5 you probably need to rebuild CsoundQt as well. See instructions on: https://github.com/csound/csound/wiki/CsoundQt-with-Csound6-on-Debian-Ubunt u:-a-build-guide https://github.com/csound/csound/wiki/Compiling-CsoundQT-for-Fedora-22-w-Python-and-RTmidi-support   Hope it helps!   tarmo     On Wednesday 13 January 2016 00:02:28 you wrote:

No, your efforts have not been in vain, I guarantee! :)

I did

indeed build from git, following the instructions in the

Debian/Ubuntu

section. However, since I couldn't build the dependencies, I

installed

three that I am sure are required: bison, curl and flex. The

Libsndfile

is installed (in the repos here it is called libsndfile1, but

there is

also libsndfile-static).

Then I followed the build instructions, and

all *seemed* to go well. When I go to open an instrument,

Csound starts,

but then gets an error and stops.

So where do I get the cmake-gui and

how do I install it? (sorry for my persistant noobie-ness..)

brian

PS: I'll check back tomorrow, it's pretty late here now..

On Tue, 12

Jan 2016 22:40:42 +0000, Rory Walsh wrote:

I'm not sure of the first

problem but the second sounds like an issue with the fltk

opcodes. You

built Csound yourself from the instructions on the Csound git

page? I

assume you ran cmake at some point to generate your makefiles?

Sorry,

I'm trying to follow what steps you may have taken here!

Anyhow,

if you install cmake-gui and run it and select the Csound

source folder

along with the build folder, you should get a list of install

build

options. It's here that you can tweak the build settings. But

you did

build Csound yourself right? Otherwise this email, typed on a

rather

useless android phone with a screen smaller than most

microorganisms has

been a complete and utter waste of time!

On 12 Jan 2016 22:27,

wrote:

Hi Rory,

I'm not sure I understand. Which folder

and which command?

Also, after I do what you said here, do I

have to "purge" the old install before doing a make again?

brian

On Tue, 12 Jan 2016 20:49:02 +0000, Rory Walsh wrote:

Could be that you didn't build the fltk opcodes. If you

install and run

cmake-gui from your Csound build dir you can enable our

disable the

building of any of these opcodes. It may not have built them

breccias

you dont have fltk installed. Cmake-gui will tell you more.

On 12

Jan 2016 20:43, wrote:

Hi again everyone,

so, the

installation of Csound git version was a success-- but I can't

open any

csound instruments anymore! I always get some error, each

instrument has

"its own." Examples include: "define macro unexpected

character )(0x29)

awaiting #" or "error: syntax error, unexpected INTEGER_TOKEN

(token

"103") from file SawSquareSynth.csd (1) line 14: >>>FLcolor

103

Csound mailing list Csound@listserv.heanet.ie [20]

https://listserv.heanet.ie/cgi-bin/wa?A0=CSOUND [21] Send bugs

reports

to https://github.com/csound/csound/issues [22] Discussions of

bugs and

features can be posted here

Csound mailing list

Csound@listserv.heanet.ie [23]

https://listserv.heanet.ie/cgi-bin/wa?A0=CSOUND [24] Send bugs

reports

to https://github.com/csound/csound/issues [25] Discussions of

bugs and

features can be posted here

Csound mailing list

Csound@listserv.heanet.ie [27]

https://listserv.heanet.ie/cgi-bin/wa?A0=CSOUND [28] Send bugs

reports

to https://github.com/csound/csound/issues [29] Discussions of

bugs and

features can be posted here

Links:

------

[1]

https://github.com/csound/csound/blob/develop/BUILD.md#fedora

[2]

mailto:Csound@listserv.heanet.ie

[3]

https://listserv.heanet.ie/cgi-bin/wa?A0=CSOUND

[4]

https://github.com/csound/csound/issues

[5]

mailto:Csound@listserv.heanet.ie

[6]

https://listserv.heanet.ie/cgi-bin/wa?A0=CSOUND

[7]

https://github.com/csound/csound/issues

[8]

mailto:Csound@listserv.heanet.ie

[9]

https://listserv.heanet.ie/cgi-bin/wa?A0=CSOUND

[10]

https://github.com/csound/csound/issues

[11]

mailto:brian@LINUXSYNTHS.COM

[12] mailto:Csound@listserv.heanet.ie

[13]

https://listserv.heanet.ie/cgi-bin/wa?A0=CSOUND

[14]

https://github.com/csound/csound/issues

[15]

mailto:brian@LINUXSYNTHS.COM

[16] mailto:Csound@listserv.heanet.ie

[17]

https://listserv.heanet.ie/cgi-bin/wa?A0=CSOUND

[18]

https://github.com/csound/csound/issues

[19]

mailto:brian@linuxsynths.com

[20] mailto:Csound@listserv.heanet.ie

[21]

https://listserv.heanet.ie/cgi-bin/wa?A0=CSOUND

[22]

https://github.com/csound/csound/issues

[23]

mailto:Csound@listserv.heanet.ie

[24]

https://listserv.heanet.ie/cgi-bin/wa?A0=CSOUND

[25]

https://github.com/csound/csound/issues

[26]

mailto:brian@linuxsynths.com

[27] mailto:Csound@listserv.heanet.ie

[28]

https://listserv.heanet.ie/cgi-bin/wa?A0=CSOUND

[29]

https://github.com/csound/csound/issues

Csound mailing list

Csound@listserv.heanet.ie

https://listserv.heanet.ie/cgi-bin/wa?A0=CSOUND

Send bugs reports to

https://github.com/csound/csound/issues

Discussions of bugs and features can be posted here

  Csound mailing list Csound@listserv.heanet.ie https://listserv.heanet.ie/cgi-bin/wa?A0=CSOUND Send bugs reports to https://github.com/csound/csound/issues Discussions of bugs and features can be posted here     Csound mailing list Csound@listserv.heanet.ie https://listserv.heanet.ie/cgi-bin/wa?A0=CSOUND Send bugs reports to https://github.com/csound/csound/issues Discussions of bugs and features can be posted here

Csound mailing list
Csound@listserv.heanet.ie
https://listserv.heanet.ie/cgi-bin/wa?A0=CSOUND
Send bugs reports to
        https://github.com/csound/csound/issues
Discussions of bugs and features can be posted here

Hi,

try to find, in which folder are your Csound plugins installed (poably something like /usr/local/lib/csound/plugins ) If you use 32-bit architecture, I guess you need to set in terminal

export OPCODE6DIR=/something/plugins

before starting Csound.

But seems the error is in something else... Maybe there are somewhere leftovers from previous installation and things get messed up?

Can you try to run

$ which csound

to see which binary is started and

$ldd /usr/local/bin/csound # or wherever is you csound binary

to check which libraries are used to see if there is something wrong.

I am afraid I have no further idea...

tarmo

On Wednesday 13 January 2016 12:04:10 you wrote:

> At the moment I'm using just the command line, not CsoundQT.

>

> What

> is the full line I should add to .bashrc and where in the file should I

> paste it?

>

> On Wed, 13 Jan 2016 12:28:17 +0200, Tarmo Johannes wrote:

> > CsoundQt or command line? Can you get some very simple csd work from

>

> command line?

>

> > 64bit is for Csound, how exact numbers it uses, not

>

> architecture. So 32bit system is fine.

>

> > T

> > 13.01.2016 12:23 kirjutas

>

> kuupäeval :

> >> Hi Tarmo,

> >>

> >> Yes, I did sudo ldconfig; I did not

>

> set the OPCODE6DIR64 variable. Is this for 64-bit systems? (mine is

> 32-bit)

>

> >> I installed fltk from source (unzipped the tarball in

>

> the csound directory) and did a re-make, but I still get this type of

>

> error:

> >> 0dBFS level = 32768.0

> >> Csound version 6.07 (double

>

> samples) Jan 12 2016

>

> >> libsndfile-1.0.25

>

> >> UnifiedCSD:

> MonoPolySynthII.csd

>

> >> STARTING FILE

> >> Creating options

> >> Creating

>

> orchestra

>

> >> Creating score

> >> rtmidi: ALSA Raw MIDI module enabled

>

> rtaudio: JACK module enabled

>

> >> define macro unexpected character

>

> )(0x29) awaiting #

>

> >> cannot compile orchestra

> >> end of score.

>

> overall amps: 0.0

>

> >> overall samples out of range: 0

> >> 2 errors in

>

> performance

>

> >> ----

> >>

> >> brian

> >>

> >> On Wed, 13 Jan 2016

>

> 08:34:47 +0200, Tarmo Johannes wrote:

> >>> Hi, some guesses:

> >>>

> >>>

> >>> - did you do

> >>>

> >>> $ sudo ldconfig

> >>>

> >>> to let the system

>

> know about new libraries?

>

> >>> - did you set the OPCODE6DIR64

>

> evironment variable (if you had Csound 5 before, this is needed for

>

> Csound6). Run in terminal before starting csound:

> >>> export

>

> OPCODE6DIR64=/usr/local/lib/csound/plugins64-6.0/

>

> >>> #or where

>

> your Csound6 plugins are installed

>

> >>> or better if you add this

>

> line to $HOME/.bashrc logout and log in again

>

> >>> - are you

>

> perhaps trying it via old CsoundQt? If that was built against Csound5

> you probably need to rebuild CsoundQt as well. See instructions on:

>

>

>

> https://github.com/csound/csound/wiki/CsoundQt-with-Csound6-on-Debian-Ubuntu

> :-a-build-guide [1]

>

>

> https://github.com/csound/csound/wiki/Compiling-CsoundQT-for-Fedora-22-w-Pyt

> hon-and-RTmidi-support [2]

>

> >>> Hope it helps!

> >>>

> >>> tarmo

> >>>

> >>> On Wednesday 13

>

> January 2016 00:02:28 you wrote:

> >>>> No, your efforts have not

>

> been in vain, I guarantee! :)

>

> >>>> I did

>

> indeed build from git, following the instructions in the Debian/Ubuntu

>

> >>>> section. However, since I couldn't build the dependencies, I

>

> installed

>

> >>>> three that I am sure are required: bison, curl and

>

> flex. The Libsndfile

>

> >>>> is installed (in the repos here it is

>

> called libsndfile1, but there is

>

> >>>> also libsndfile-static).

> >>>>

> >>>>

> >>>>

> >>>>

> >>>> Then I followed the build instructions, and

> >>>>

> >>>>

> >>>> all *seemed* to go well. When I go to open an instrument, Csound

>

> starts,

>

> >>>> but then gets an error and stops.

> >>>>

> >>>>

> >>>>

> >>>>

> >>>> So where do I get the cmake-gui and

> >>>>

> >>>> how do I install

>

> it? (sorry for my persistant noobie-ness..)

>

> >>>> brian

> >>>>

> >>>>

> >>>>

> >>>>

> >>>>

> >>>>

> >>>> PS: I'll check back tomorrow, it's

>

> pretty late here now..

>

> >>>> On Tue, 12

> >>>>

> >>>> Jan 2016 22:40:42 +0000, Rory Walsh wrote:

> >>>> > I'm not

>

> sure of the first

>

> >>>> problem but the second sounds

>

> like an issue with the fltk opcodes. You

>

> >>>> built Csound

>

> yourself from the instructions on the Csound git page? I

>

>

> assume you ran cmake at some point to generate your makefiles? Sorry,

>

> >>>> I'm trying to follow what steps you may have taken here!

> >>>>

> >>>> > Anyhow,

> >>>>

> >>>> if you install

>

> cmake-gui and run it and select the Csound source folder

>

>

> along with the build folder, you should get a list of install build

>

> >>>> options. It's here that you can tweak the build settings. But you

>

> did

>

> >>>> build Csound yourself right? Otherwise this email, typed

>

> on a rather

>

> >>>> useless android phone with a screen smaller than

>

> most microorganisms has

>

> >>>> been a complete and utter waste of

>

> time!

>

> >>>> > On 12 Jan 2016 22:27,

> >>>>

> >>>> wrote:

> >>>> >> Hi Rory,

> >>>> >>

> >>>> >>

> >>>> >>

> >>>> >> I'm not

>

> sure I understand. Which folder

>

> >>>> and which command?

> >>>>

> >>>> >> Also, after I do what you said here, do I

> >>>>

> >>>> have to "purge" the old install before doing a make

>

> again?

>

> >>>> >> brian

> >>>> >>

> >>>> >>

> >>>> >>

> >>>> >> On Tue,

>

> 12 Jan 2016 20:49:02 +0000, Rory Walsh wrote:

> >>>> Could be that

>

> you didn't build the fltk opcodes. If you install and run

>

>

> cmake-gui from your Csound build dir you can enable our disable the

>

> >>>> building of any of these opcodes. It may not have built them

>

> breccias

>

> >>>> you dont have fltk installed. Cmake-gui will tell

>

> you more.

>

> >>>> >>> On 12

> >>>>

> >>>> Jan 2016

>

> 20:43, wrote:

> >>>> >>>> Hi again everyone,

> >>>> >>>>

> >>>> >>>>

> >>>> >>>>

> >>>> >>>>

> >>>> >>>> so, the

> >>>>

> >>>> installation of Csound git

>

> version was a success-- but I can't open any

>

> >>>> csound

>

> instruments anymore! I always get some error, each instrument has

>

> >>>> "its own." Examples include: "define macro unexpected character

>

> )(0x29)

>

> >>>> awaiting #" or "error: syntax error, unexpected

>

> INTEGER_TOKEN (token

>

> >>>> "103") from file SawSquareSynth.csd (1)

>

> line 14: >>>FLcolor 103

>

> >>>> Csound mailing list

>

> Csound@listserv.heanet.ie [3] [20]

>

>

> https://listserv.heanet.ie/cgi-bin/wa?A0=CSOUND [4] [21] Send bugs

> reports

>

> >>>> to https://github.com/csound/csound/issues [5] [22]

>

> Discussions of bugs and

>

> >>>> features can be posted here

> >>>>

> >>>> >> Csound mailing list

>

> Csound@listserv.heanet.ie [6] [23]

>

>

> https://listserv.heanet.ie/cgi-bin/wa?A0=CSOUND [7] [24] Send bugs

> reports

>

> >>>> to https://github.com/csound/csound/issues [8] [25]

>

> Discussions of bugs and

>

> >>>> features can be posted here

> >>>>

> >>>> > Csound mailing list

>

> Csound@listserv.heanet.ie [9] [27]

>

>

> https://listserv.heanet.ie/cgi-bin/wa?A0=CSOUND [10] [28] Send bugs

> reports

>

> >>>> to https://github.com/csound/csound/issues [11] [29]

>

> Discussions of bugs and

>

> >>>> features can be posted here

> >>>>

> >>>>

> >>>>

> >>>>

> >>>>

> >>>>

> >>>>

> >>>>

> >>>> Links:

> >>>>

> >>>> ------

> >>>>

> >>>>

> >>>> [1]

>

> https://github.com/csound/csound/blob/develop/BUILD.md#fedora [12]

>

> >>>> [2]

> >>>>

> >>>> mailto:Csound@listserv.heanet.ie [13]

>

> [3]

>

> >>>> https://listserv.heanet.ie/cgi-bin/wa?A0=CSOUND [14]

> >>>>

> >>>>

> >>>> [4]

> >>>>

> >>>> https://github.com/csound/csound/issues [15]

> >>>>

> >>>>

> >>>> [5]

> >>>>

> >>>> mailto:Csound@listserv.heanet.ie [16]

>

> [6]

>

> >>>> https://listserv.heanet.ie/cgi-bin/wa?A0=CSOUND [17]

> >>>>

> >>>>

> >>>> [7]

> >>>>

> >>>> https://github.com/csound/csound/issues [18]

> >>>>

> >>>>

> >>>> [8]

> >>>>

> >>>> mailto:Csound@listserv.heanet.ie [19]

>

> [9]

>

> >>>> https://listserv.heanet.ie/cgi-bin/wa?A0=CSOUND [20]

> >>>>

> >>>>

> >>>> [10]

> >>>>

> >>>> https://github.com/csound/csound/issues [21]

> >>>>

> >>>>

> >>>> [11]

> >>>>

> >>>> mailto:brian@LINUXSYNTHS.COM [22]

> >>>>

> >>>> [12]

>

> mailto:Csound@listserv.heanet.ie [23]

>

> >>>> [13]

>

> https://listserv.heanet.ie/cgi-bin/wa?A0=CSOUND [24]

>

> >>>> [14]

> >>>>

> >>>>

> >>>> https://github.com/csound/csound/issues [25]

> >>>>

> >>>> [15]

> >>>>

> >>>>

> >>>> mailto:brian@LINUXSYNTHS.COM [26]

> >>>>

> >>>> [16]

>

> mailto:Csound@listserv.heanet.ie [27]

>

> >>>> [17]

>

> https://listserv.heanet.ie/cgi-bin/wa?A0=CSOUND [28]

>

> >>>> [18]

> >>>>

> >>>>

> >>>> https://github.com/csound/csound/issues [29]

> >>>>

> >>>> [19]

> >>>>

> >>>>

> >>>> mailto:brian@linuxsynths.com [30]

> >>>>

> >>>> [20]

>

> mailto:Csound@listserv.heanet.ie [31]

>

> >>>> [21]

>

> https://listserv.heanet.ie/cgi-bin/wa?A0=CSOUND [32]

>

> >>>> [22]

> >>>>

> >>>>

> >>>> https://github.com/csound/csound/issues [33]

> >>>>

> >>>> [23]

> >>>>

> >>>>

> >>>> mailto:Csound@listserv.heanet.ie [34]

> >>>>

> >>>> [24]

> >>>>

> >>>>

> >>>> https://listserv.heanet.ie/cgi-bin/wa?A0=CSOUND [35]

>

> [25]

>

> >>>> https://github.com/csound/csound/issues [36]

>

> [26]

>

> >>>> mailto:brian@linuxsynths.com [37]

> >>>>

> >>>> [27]

>

> mailto:Csound@listserv.heanet.ie [38]

>

> >>>> [28]

>

> https://listserv.heanet.ie/cgi-bin/wa?A0=CSOUND [39]

>

> >>>> [29]

> >>>>

> >>>>

> >>>> https://github.com/csound/csound/issues [40]

> >>>>

> >>>>

> >>>>

> >>>>

> >>>> Csound mailing list

> >>>>

> >>>> Csound@listserv.heanet.ie [41]

> >>>>

> >>>>

> >>>> https://listserv.heanet.ie/cgi-bin/wa?A0=CSOUND [42]

>

> Send bugs reports to

>

> >>>> https://github.com/csound/csound/issues

>

> [43]

>

> >>>> Discussions of bugs and features can be posted here

> >>>

> >>> Csound mailing list Csound@listserv.heanet.ie [44]

>

> https://listserv.heanet.ie/cgi-bin/wa?A0=CSOUND [45] Send bugs reports

> to https://github.com/csound/csound/issues [46] Discussions of bugs and

> features can be posted here

>

> >> Csound mailing list

>

> Csound@listserv.heanet.ie [47]

> https://listserv.heanet.ie/cgi-bin/wa?A0=CSOUND [48] Send bugs reports

> to https://github.com/csound/csound/issues [49] Discussions of bugs and

> features can be posted here

>

> > Csound mailing list

>

> Csound@listserv.heanet.ie [51]

> https://listserv.heanet.ie/cgi-bin/wa?A0=CSOUND [52] Send bugs reports

> to https://github.com/csound/csound/issues [53] Discussions of bugs and

> features can be posted here

>

>

>

> Links:

> ------

> [1]

> https://github.com/csound/csound/wiki/CsoundQt-with-Csound6-on-Debian-Ubuntu

> :-a-build-guide [2]

> https://github.com/csound/csound/wiki/Compiling-CsoundQT-for-Fedora-22-w-Pyt

> hon-and-RTmidi-support [3]

> mailto:Csound@listserv.heanet.ie

> [4]

> https://listserv.heanet.ie/cgi-bin/wa?A0=CSOUND

> [5]

> https://github.com/csound/csound/issues

> [6]

> mailto:Csound@listserv.heanet.ie

> [7]

> https://listserv.heanet.ie/cgi-bin/wa?A0=CSOUND

> [8]

> https://github.com/csound/csound/issues

> [9]

> mailto:Csound@listserv.heanet.ie

> [10]

> https://listserv.heanet.ie/cgi-bin/wa?A0=CSOUND

> [11]

> https://github.com/csound/csound/issues

> [12]

> https://github.com/csound/csound/blob/develop/BUILD.md#fedora

> [13]

> mailto:Csound@listserv.heanet.ie

> [14]

> https://listserv.heanet.ie/cgi-bin/wa?A0=CSOUND

> [15]

> https://github.com/csound/csound/issues

> [16]

> mailto:Csound@listserv.heanet.ie

> [17]

> https://listserv.heanet.ie/cgi-bin/wa?A0=CSOUND

> [18]

> https://github.com/csound/csound/issues

> [19]

> mailto:Csound@listserv.heanet.ie

> [20]

> https://listserv.heanet.ie/cgi-bin/wa?A0=CSOUND

> [21]

> https://github.com/csound/csound/issues

> [22]

> mailto:brian@LINUXSYNTHS.COM

> [23] mailto:Csound@listserv.heanet.ie

> [24]

> https://listserv.heanet.ie/cgi-bin/wa?A0=CSOUND

> [25]

> https://github.com/csound/csound/issues

> [26]

> mailto:brian@LINUXSYNTHS.COM

> [27] mailto:Csound@listserv.heanet.ie

> [28]

> https://listserv.heanet.ie/cgi-bin/wa?A0=CSOUND

> [29]

> https://github.com/csound/csound/issues

> [30]

> mailto:brian@linuxsynths.com

> [31] mailto:Csound@listserv.heanet.ie

> [32]

> https://listserv.heanet.ie/cgi-bin/wa?A0=CSOUND

> [33]

> https://github.com/csound/csound/issues

> [34]

> mailto:Csound@listserv.heanet.ie

> [35]

> https://listserv.heanet.ie/cgi-bin/wa?A0=CSOUND

> [36]

> https://github.com/csound/csound/issues

> [37]

> mailto:brian@linuxsynths.com

> [38] mailto:Csound@listserv.heanet.ie

> [39]

> https://listserv.heanet.ie/cgi-bin/wa?A0=CSOUND

> [40]

> https://github.com/csound/csound/issues

> [41]

> mailto:Csound@listserv.heanet.ie

> [42]

> https://listserv.heanet.ie/cgi-bin/wa?A0=CSOUND

> [43]

> https://github.com/csound/csound/issues

> [44]

> mailto:Csound@listserv.heanet.ie

> [45]

> https://listserv.heanet.ie/cgi-bin/wa?A0=CSOUND

> [46]

> https://github.com/csound/csound/issues

> [47]

> mailto:Csound@listserv.heanet.ie

> [48]

> https://listserv.heanet.ie/cgi-bin/wa?A0=CSOUND

> [49]

> https://github.com/csound/csound/issues

> [50]

> mailto:brian@linuxsynths.com

> [51] mailto:Csound@listserv.heanet.ie

> [52]

> https://listserv.heanet.ie/cgi-bin/wa?A0=CSOUND

> [53]

> https://github.com/csound/csound/issues

>

> Csound mailing list

> Csound@listserv.heanet.ie

> https://listserv.heanet.ie/cgi-bin/wa?A0=CSOUND

> Send bugs reports to

> https://github.com/csound/csound/issues

> Discussions of bugs and features can be posted here

Hi Tarmo,

I appreciate your time and help. I'm probably the most inexperienced user here, so if you can tolerate me you can deal with just about anyone! :D

I did the export command from the exact place you guessed: /usr/local/lib/csound/plugins  and it looks like all is well, as there were no error comments printed out in the terminal.

Then I checked which binary, and got: /usr/local/bin/csound

Then I ran the ldd command and got this:

ldd /usr/local/bin/csound
        linux-gate.so.1 =>  (0xb7729000)
        libcsound64.so.6.0 => /usr/local/lib/libcsound64.so.6.0 (0xb7413000)
        libpthread.so.0 => /lib/i386-linux-gnu/libpthread.so.0 (0xb73f8000)
        libc.so.6 => /lib/i386-linux-gnu/libc.so.6 (0xb724e000)
        libsndfile.so.1 => /usr/lib/i386-linux-gnu/libsndfile.so.1 (0xb71db000)
        libm.so.6 => /lib/i386-linux-gnu/libm.so.6 (0xb71af000)
        libdl.so.2 => /lib/i386-linux-gnu/libdl.so.2 (0xb71aa000)
        librt.so.1 => /lib/i386-linux-gnu/librt.so.1 (0xb71a1000)
        /lib/ld-linux.so.2 (0xb772a000)
        libFLAC.so.8 => /usr/lib/i386-linux-gnu/libFLAC.so.8 (0xb7152000)
        libvorbisenc.so.2 => /usr/lib/i386-linux-gnu/libvorbisenc.so.2 (0xb6fda000)
        libvorbis.so.0 => /usr/lib/i386-linux-gnu/libvorbis.so.0 (0xb6faf000)
        libogg.so.0 => /usr/lib/i386-linux-gnu/libogg.so.0 (0xb6fa7000)

Hope this helps!
I'll be out for a few hours now, but will check back this evening..

brian

On Wed, 13 Jan 2016 14:29:30 +0200, Tarmo Johannes wrote:

Hi,

 

try to find, in which folder are your Csound plugins installed (poably something like /usr/local/lib/csound/plugins ) If you use 32-bit architecture, I guess you need to set in terminal

 

export OPCODE6DIR=/something/plugins

 

before starting Csound.

 

But seems the error is in something else... Maybe there are somewhere leftovers from previous installation and things get messed up?

 

Can you try to run

$ which csound

to see which binary is started and

 

$ldd /usr/local/bin/csound # or wherever is you csound binary

 

to check which libraries are used to see if there is something wrong.

 

I am afraid I have no further idea...

 

tarmo

 

On Wednesday 13 January 2016 12:04:10 you wrote:

> At the moment I'm using just the command line, not CsoundQT.

>

> What

> is the full line I should add to .bashrc and where in the file should I

> paste it?

>

> On Wed, 13 Jan 2016 12:28:17 +0200, Tarmo Johannes wrote:

> > CsoundQt or command line? Can you get some very simple csd work from

>

> command line?

>

> > 64bit is for Csound, how exact numbers it uses, not

>

> architecture. So 32bit system is fine.

>

> > T

> > 13.01.2016 12:23 kirjutas

>

> kuupäeval :

> >> Hi Tarmo,

> >>

> >> Yes, I did sudo ldconfig; I did not

>

> set the OPCODE6DIR64 variable. Is this for 64-bit systems? (mine is

> 32-bit)

>

> >> I installed fltk from source (unzipped the tarball in

>

> the csound directory) and did a re-make, but I still get this type of

>

> error:

> >> 0dBFS level = 32768.0

> >> Csound version 6.07 (double

>

> samples) Jan 12 2016

>

> >> libsndfile-1.0.25

>

> >> UnifiedCSD:

> MonoPolySynthII.csd

>

> >> STARTING FILE

> >> Creating options

> >> Creating

>

> orchestra

>

> >> Creating score

> >> rtmidi: ALSA Raw MIDI module enabled

>

> rtaudio: JACK module enabled

>

> >> define macro unexpected character

>

> )(0x29) awaiting #

>

> >> cannot compile orchestra

> >> end of score.

>

> overall amps: 0.0

>

> >> overall samples out of range: 0

> >> 2 errors in

>

> performance

>

> >> ----

> >>

> >> brian

> >>

> >> On Wed, 13 Jan 2016

>

> 08:34:47 +0200, Tarmo Johannes wrote:

> >>> Hi, some guesses:

> >>>

> >>>

> >>> - did you do

> >>>

> >>> $ sudo ldconfig

> >>>

> >>> to let the system

>

> know about new libraries?

>

> >>> - did you set the OPCODE6DIR64

>

> evironment variable (if you had Csound 5 before, this is needed for

>

> Csound6). Run in terminal before starting csound:

> >>> export

>

> OPCODE6DIR64=/usr/local/lib/csound/plugins64-6.0/

>

> >>> #or where

>

> your Csound6 plugins are installed

>

> >>> or better if you add this

>

> line to $HOME/.bashrc logout and log in again

>

> >>> - are you

>

> perhaps trying it via old CsoundQt? If that was built against Csound5

> you probably need to rebuild CsoundQt as well. See instructions on:

>

>

>

> https://github.com/csound/csound/wiki/CsoundQt-with-Csound6-on-Debian-Ubuntu

> :-a-build-guide [1]

>

>

> https://github.com/csound/csound/wiki/Compiling-CsoundQT-for-Fedora-22-w-Pyt

> hon-and-RTmidi-support [2]

>

> >>> Hope it helps!

> >>>

> >>> tarmo

> >>>

> >>> On Wednesday 13

>

> January 2016 00:02:28 you wrote:

> >>>> No, your efforts have not

>

> been in vain, I guarantee! :)

>

> >>>> I did

>

> indeed build from git, following the instructions in the Debian/Ubuntu

>

> >>>> section. However, since I couldn't build the dependencies, I

>

> installed

>

> >>>> three that I am sure are required: bison, curl and

>

> flex. The Libsndfile

>

> >>>> is installed (in the repos here it is

>

> called libsndfile1, but there is

>

> >>>> also libsndfile-static).

> >>>>

> >>>>

> >>>>

> >>>>

> >>>> Then I followed the build instructions, and

> >>>>

> >>>>

> >>>> all *seemed* to go well. When I go to open an instrument, Csound

>

> starts,

>

> >>>> but then gets an error and stops.

> >>>>

> >>>>

> >>>>

> >>>>

> >>>> So where do I get the cmake-gui and

> >>>>

> >>>> how do I install

>

> it? (sorry for my persistant noobie-ness..)

>

> >>>> brian

> >>>>

> >>>>

> >>>>

> >>>>

> >>>>

> >>>>

> >>>> PS: I'll check back tomorrow, it's

>

> pretty late here now..

>

> >>>> On Tue, 12

> >>>>

> >>>> Jan 2016 22:40:42 +0000, Rory Walsh wrote:

> >>>> > I'm not

>

> sure of the first

>

> >>>> problem but the second sounds

>

> like an issue with the fltk opcodes. You

>

> >>>> built Csound

>

> yourself from the instructions on the Csound git page? I

>

>

> assume you ran cmake at some point to generate your makefiles? Sorry,

>

> >>>> I'm trying to follow what steps you may have taken here!

> >>>>

> >>>> > Anyhow,

> >>>>

> >>>> if you install

>

> cmake-gui and run it and select the Csound source folder

>

>

> along with the build folder, you should get a list of install build

>

> >>>> options. It's here that you can tweak the build settings. But you

>

> did

>

> >>>> build Csound yourself right? Otherwise this email, typed

>

> on a rather

>

> >>>> useless android phone with a screen smaller than

>

> most microorganisms has

>

> >>>> been a complete and utter waste of

>

> time!

>

> >>>> > On 12 Jan 2016 22:27,

> >>>>

> >>>> wrote:

> >>>> >> Hi Rory,

> >>>> >>

> >>>> >>

> >>>> >>

> >>>> >> I'm not

>

> sure I understand. Which folder

>

> >>>> and which command?

> >>>>

> >>>> >> Also, after I do what you said here, do I

> >>>>

> >>>> have to "purge" the old install before doing a make

>

> again?

>

> >>>> >> brian

> >>>> >>

> >>>> >>

> >>>> >>

> >>>> >> On Tue,

>

> 12 Jan 2016 20:49:02 +0000, Rory Walsh wrote:

> >>>> Could be that

>

> you didn't build the fltk opcodes. If you install and run

>

>

> cmake-gui from your Csound build dir you can enable our disable the

>

> >>>> building of any of these opcodes. It may not have built them

>

> breccias

>

> >>>> you dont have fltk installed. Cmake-gui will tell

>

> you more.

>

> >>>> >>> On 12

> >>>>

> >>>> Jan 2016

>

> 20:43, wrote:

> >>>> >>>> Hi again everyone,

> >>>> >>>>

> >>>> >>>>

> >>>> >>>>

> >>>> >>>>

> >>>> >>>> so, the

> >>>>

> >>>> installation of Csound git

>

> version was a success-- but I can't open any

>

> >>>> csound

>

> instruments anymore! I always get some error, each instrument has

>

> >>>> "its own." Examples include: "define macro unexpected character

>

> )(0x29)

>

> >>>> awaiting #" or "error: syntax error, unexpected

>

> INTEGER_TOKEN (token

>

> >>>> "103") from file SawSquareSynth.csd (1)

>

> line 14: >>>FLcolor 103

>

> >>>> Csound mailing list

>

> Csound@listserv.heanet.ie [3] [20]

>

>

> https://listserv.heanet.ie/cgi-bin/wa?A0=CSOUND [4] [21] Send bugs

> reports

>

> >>>> to https://github.com/csound/csound/issues [5] [22]

>

> Discussions of bugs and

>

> >>>> features can be posted here

> >>>>

> >>>> >> Csound mailing list

>

> Csound@listserv.heanet.ie [6] [23]

>

>

> https://listserv.heanet.ie/cgi-bin/wa?A0=CSOUND [7] [24] Send bugs

> reports

>

> >>>> to https://github.com/csound/csound/issues [8] [25]

>

> Discussions of bugs and

>

> >>>> features can be posted here

> >>>>

> >>>> > Csound mailing list

>

> Csound@listserv.heanet.ie [9] [27]

>

>

> https://listserv.heanet.ie/cgi-bin/wa?A0=CSOUND [10] [28] Send bugs

> reports

>

> >>>> to https://github.com/csound/csound/issues [11] [29]

>

> Discussions of bugs and

>

> >>>> features can be posted here

> >>>>

> >>>>

> >>>>

> >>>>

> >>>>

> >>>>

> >>>>

> >>>>

> >>>> Links:

> >>>>

> >>>> ------

> >>>>

> >>>>

> >>>> [1]

>

> https://github.com/csound/csound/blob/develop/BUILD.md#fedora [12]

>

> >>>> [2]

> >>>>

> >>>> mailto:Csound@listserv.heanet.ie [13]

>

> [3]

>

> >>>> https://listserv.heanet.ie/cgi-bin/wa?A0=CSOUND [14]

> >>>>

> >>>>

> >>>> [4]

> >>>>

> >>>> https://github.com/csound/csound/issues [15]

> >>>>

> >>>>

> >>>> [5]

> >>>>

> >>>> mailto:Csound@listserv.heanet.ie [16]

>

> [6]

>

> >>>> https://listserv.heanet.ie/cgi-bin/wa?A0=CSOUND [17]

> >>>>

> >>>>

> >>>> [7]

> >>>>

> >>>> https://github.com/csound/csound/issues [18]

> >>>>

> >>>>

> >>>> [8]

> >>>>

> >>>> mailto:Csound@listserv.heanet.ie [19]

>

> [9]

>

> >>>> https://listserv.heanet.ie/cgi-bin/wa?A0=CSOUND [20]

> >>>>

> >>>>

> >>>> [10]

> >>>>

> >>>> https://github.com/csound/csound/issues [21]

> >>>>

> >>>>

> >>>> [11]

> >>>>

> >>>> mailto:brian@LINUXSYNTHS.COM [22]

> >>>>

> >>>> [12]

>

> mailto:Csound@listserv.heanet.ie [23]

>

> >>>> [13]

>

> https://listserv.heanet.ie/cgi-bin/wa?A0=CSOUND [24]

>

> >>>> [14]

> >>>>

> >>>>

> >>>> https://github.com/csound/csound/issues [25]

> >>>>

> >>>> [15]

> >>>>

> >>>>

> >>>> mailto:brian@LINUXSYNTHS.COM [26]

> >>>>

> >>>> [16]

>

> mailto:Csound@listserv.heanet.ie [27]

>

> >>>> [17]

>

> https://listserv.heanet.ie/cgi-bin/wa?A0=CSOUND [28]

>

> >>>> [18]

> >>>>

> >>>>

> >>>> https://github.com/csound/csound/issues [29]

> >>>>

> >>>> [19]

> >>>>

> >>>>

> >>>> mailto:brian@linuxsynths.com [30]

> >>>>

> >>>> [20]

>

> mailto:Csound@listserv.heanet.ie [31]

>

> >>>> [21]

>

> https://listserv.heanet.ie/cgi-bin/wa?A0=CSOUND [32]

>

> >>>> [22]

> >>>>

> >>>>

> >>>> https://github.com/csound/csound/issues [33]

> >>>>

> >>>> [23]

> >>>>

> >>>>

> >>>> mailto:Csound@listserv.heanet.ie [34]

> >>>>

> >>>> [24]

> >>>>

> >>>>

> >>>> https://listserv.heanet.ie/cgi-bin/wa?A0=CSOUND [35]

>

> [25]

>

> >>>> https://github.com/csound/csound/issues [36]

>

> [26]

>

> >>>> mailto:brian@linuxsynths.com [37]

> >>>>

> >>>> [27]

>

> mailto:Csound@listserv.heanet.ie [38]

>

> >>>> [28]

>

> https://listserv.heanet.ie/cgi-bin/wa?A0=CSOUND [39]

>

> >>>> [29]

> >>>>

> >>>>

> >>>> https://github.com/csound/csound/issues [40]

> >>>>

> >>>>

> >>>>

> >>>>

> >>>> Csound mailing list

> >>>>

> >>>> Csound@listserv.heanet.ie [41]

> >>>>

> >>>>

> >>>> https://listserv.heanet.ie/cgi-bin/wa?A0=CSOUND [42]

>

> Send bugs reports to

>

> >>>> https://github.com/csound/csound/issues

>

> [43]

>

> >>>> Discussions of bugs and features can be posted here

> >>>

> >>> Csound mailing list Csound@listserv.heanet.ie [44]

>

> https://listserv.heanet.ie/cgi-bin/wa?A0=CSOUND [45] Send bugs reports

> to https://github.com/csound/csound/issues [46] Discussions of bugs and

> features can be posted here

>

> >> Csound mailing list

>

> Csound@listserv.heanet.ie [47]

> https://listserv.heanet.ie/cgi-bin/wa?A0=CSOUND [48] Send bugs reports

> to https://github.com/csound/csound/issues [49] Discussions of bugs and

> features can be posted here

>

> > Csound mailing list

>

> Csound@listserv.heanet.ie [51]

> https://listserv.heanet.ie/cgi-bin/wa?A0=CSOUND [52] Send bugs reports

> to https://github.com/csound/csound/issues [53] Discussions of bugs and

> features can be posted here

>

>

>

> Links:

> ------

> [1]

> https://github.com/csound/csound/wiki/CsoundQt-with-Csound6-on-Debian-Ubuntu

> :-a-build-guide [2]

> https://github.com/csound/csound/wiki/Compiling-CsoundQT-for-Fedora-22-w-Pyt

> hon-and-RTmidi-support [3]

> mailto:Csound@listserv.heanet.ie

> [4]

> https://listserv.heanet.ie/cgi-bin/wa?A0=CSOUND

> [5]

> https://github.com/csound/csound/issues

> [6]

> mailto:Csound@listserv.heanet.ie

> [7]

> https://listserv.heanet.ie/cgi-bin/wa?A0=CSOUND

> [8]

> https://github.com/csound/csound/issues

> [9]

> mailto:Csound@listserv.heanet.ie

> [10]

> https://listserv.heanet.ie/cgi-bin/wa?A0=CSOUND

> [11]

> https://github.com/csound/csound/issues

> [12]

> https://github.com/csound/csound/blob/develop/BUILD.md#fedora

> [13]

> mailto:Csound@listserv.heanet.ie

> [14]

> https://listserv.heanet.ie/cgi-bin/wa?A0=CSOUND

> [15]

> https://github.com/csound/csound/issues

> [16]

> mailto:Csound@listserv.heanet.ie

> [17]

> https://listserv.heanet.ie/cgi-bin/wa?A0=CSOUND

> [18]

> https://github.com/csound/csound/issues

> [19]

> mailto:Csound@listserv.heanet.ie

> [20]

> https://listserv.heanet.ie/cgi-bin/wa?A0=CSOUND

> [21]

> https://github.com/csound/csound/issues

> [22]

> mailto:brian@LINUXSYNTHS.COM

> [23] mailto:Csound@listserv.heanet.ie

> [24]

> https://listserv.heanet.ie/cgi-bin/wa?A0=CSOUND

> [25]

> https://github.com/csound/csound/issues

> [26]

> mailto:brian@LINUXSYNTHS.COM

> [27] mailto:Csound@listserv.heanet.ie

> [28]

> https://listserv.heanet.ie/cgi-bin/wa?A0=CSOUND

> [29]

> https://github.com/csound/csound/issues

> [30]

> mailto:brian@linuxsynths.com

> [31] mailto:Csound@listserv.heanet.ie

> [32]

> https://listserv.heanet.ie/cgi-bin/wa?A0=CSOUND

> [33]

> https://github.com/csound/csound/issues

> [34]

> mailto:Csound@listserv.heanet.ie

> [35]

> https://listserv.heanet.ie/cgi-bin/wa?A0=CSOUND

> [36]

> https://github.com/csound/csound/issues

> [37]

> mailto:brian@linuxsynths.com

> [38] mailto:Csound@listserv.heanet.ie

> [39]

> https://listserv.heanet.ie/cgi-bin/wa?A0=CSOUND

> [40]

> https://github.com/csound/csound/issues

> [41]

> mailto:Csound@listserv.heanet.ie

> [42]

> https://listserv.heanet.ie/cgi-bin/wa?A0=CSOUND

> [43]

> https://github.com/csound/csound/issues

> [44]

> mailto:Csound@listserv.heanet.ie

> [45]

> https://listserv.heanet.ie/cgi-bin/wa?A0=CSOUND

> [46]

> https://github.com/csound/csound/issues

> [47]

> mailto:Csound@listserv.heanet.ie

> [48]

> https://listserv.heanet.ie/cgi-bin/wa?A0=CSOUND

> [49]

> https://github.com/csound/csound/issues

> [50]

> mailto:brian@linuxsynths.com

> [51] mailto:Csound@listserv.heanet.ie

> [52]

> https://listserv.heanet.ie/cgi-bin/wa?A0=CSOUND

> [53]

> https://github.com/csound/csound/issues

>

> Csound mailing list

> Csound@listserv.heanet.ie

> https://listserv.heanet.ie/cgi-bin/wa?A0=CSOUND

> Send bugs reports to

> https://github.com/csound/csound/issues

> Discussions of bugs and features can be posted here

 

Csound mailing list Csound@listserv.heanet.ie https://listserv.heanet.ie/cgi-bin/wa?A0=CSOUND Send bugs reports to https://github.com/csound/csound/issues Discussions of bugs and features can be posted here

Hi Rory,

I installed cmake-gui (actually, it's provided in the repos here as "cmake-qt-gui"-- I hope that's a valid replacement..)

I'm actually not sure which directory is the build directory: the csound or cs6make directory?

I selected the csound directory and hit generate and got two options:

CMAKE_BUILD_TYPE and CMAKE_INSTALL_PREFIX

Before I do anything, I wanted to check, because I also got these errors in the status window:

CMake Error: Cannot open file for write: /CMakeCache.txt.tmp

CMake Error: : System Error: Resource temporarily unavailable

CMake Error: Unable to open cache file for save. /CMakeCache.txt

CMake Error: : System Error: Resource temporarily unavailable

CMake Error at /usr/share/cmake-2.8/Modules/CMakeDetermineCompilerId.cmake:99 (file):
file problem creating directory: /CMakeFiles/2.8.12.2/CompilerIdC
Call Stack (most recent call first):
/usr/share/cmake-2.8/Modules/CMakeDetermineCompilerId.cmake:39 (CMAKE_DETERMINE_COMPILER_ID_BUILD)
/usr/share/cmake-2.8/Modules/CMakeDetermineCCompiler.cmake:131 (CMAKE_DETERMINE_COMPILER_ID)
CMakeLists.txt:9 (project)

CMake Error at /usr/share/cmake-2.8/Modules/CMakeDetermineCompilerId.cmake:99 (file):
file problem creating directory: /CMakeFiles/2.8.12.2/CompilerIdC
Call Stack (most recent call first):
/usr/share/cmake-2.8/Modules/CMakeDetermineCompilerId.cmake:39 (CMAKE_DETERMINE_COMPILER_ID_BUILD)
/usr/share/cmake-2.8/Modules/CMakeDetermineCCompiler.cmake:131 (CMAKE_DETERMINE_COMPILER_ID)
CMakeLists.txt:9 (project)

CMake Error at /usr/share/cmake-2.8/Modules/CMakeDetermineCompilerId.cmake:99 (file):
file problem creating directory: /CMakeFiles/2.8.12.2/CompilerIdC
Call Stack (most recent call first):
/usr/share/cmake-2.8/Modules/CMakeDetermineCompilerId.cmake:39 (CMAKE_DETERMINE_COMPILER_ID_BUILD)
/usr/share/cmake-2.8/Modules/CMakeDetermineCCompiler.cmake:131 (CMAKE_DETERMINE_COMPILER_ID)
CMakeLists.txt:9 (project)

CMake Error at /usr/share/cmake-2.8/Modules/CMakeDetermineCompilerId.cmake:469 (file):
file Internal CMake error when trying to open file:
/CMakeFiles/CMakeError.log for writing.
Call Stack (most recent call first):
/usr/share/cmake-2.8/Modules/CMakeDetermineCompilerId.cmake:48 (CMAKE_DETERMINE_COMPILER_ID_VENDOR)
/usr/share/cmake-2.8/Modules/CMakeDetermineCCompiler.cmake:131 (CMAKE_DETERMINE_COMPILER_ID)
CMakeLists.txt:9 (project)

The C compiler identification is unknown

CMake Error: Could not open file for write in copy operation /CMakeFiles/2.8.12.2/CMakeCCompiler.cmake.tmp

CMake Error: : System Error: No such file or directory

CMake Error at /usr/share/cmake-2.8/Modules/CMakeDetermineCCompiler.cmake:186 (configure_file):
configure_file Problem configuring file
Call Stack (most recent call first):
CMakeLists.txt:9 (project)

CMake Error: Could not find cmake module file: /CMakeFiles/2.8.12.2/CMakeCCompiler.cmake

CMake Error at /usr/share/cmake-2.8/Modules/CMakeDetermineCompilerId.cmake:99 (file):
file problem creating directory: /CMakeFiles/2.8.12.2/CompilerIdCXX
Call Stack (most recent call first):
/usr/share/cmake-2.8/Modules/CMakeDetermineCompilerId.cmake:39 (CMAKE_DETERMINE_COMPILER_ID_BUILD)
/usr/share/cmake-2.8/Modules/CMakeDetermineCXXCompiler.cmake:127 (CMAKE_DETERMINE_COMPILER_ID)
CMakeLists.txt:9 (project)

CMake Error at /usr/share/cmake-2.8/Modules/CMakeDetermineCompilerId.cmake:99 (file):
file problem creating directory: /CMakeFiles/2.8.12.2/CompilerIdCXX
Call Stack (most recent call first):
/usr/share/cmake-2.8/Modules/CMakeDetermineCompilerId.cmake:39 (CMAKE_DETERMINE_COMPILER_ID_BUILD)
/usr/share/cmake-2.8/Modules/CMakeDetermineCXXCompiler.cmake:127 (CMAKE_DETERMINE_COMPILER_ID)
CMakeLists.txt:9 (project)

CMake Error at /usr/share/cmake-2.8/Modules/CMakeDetermineCompilerId.cmake:469 (file):
file Internal CMake error when trying to open file:
/CMakeFiles/CMakeError.log for writing.
Call Stack (most recent call first):
/usr/share/cmake-2.8/Modules/CMakeDetermineCompilerId.cmake:48 (CMAKE_DETERMINE_COMPILER_ID_VENDOR)
/usr/share/cmake-2.8/Modules/CMakeDetermineCXXCompiler.cmake:127 (CMAKE_DETERMINE_COMPILER_ID)
CMakeLists.txt:9 (project)

The CXX compiler identification is unknown

CMake Error: Could not open file for write in copy operation /CMakeFiles/2.8.12.2/CMakeCXXCompiler.cmake.tmp

CMake Error: : System Error: No such file or directory

CMake Error at /usr/share/cmake-2.8/Modules/CMakeDetermineCXXCompiler.cmake:185 (configure_file):
configure_file Problem configuring file
Call Stack (most recent call first):
CMakeLists.txt:9 (project)

CMake Error: Could not find cmake module file: /CMakeFiles/2.8.12.2/CMakeCXXCompiler.cmake

Check for working C compiler: /usr/bin/cc

CMake Error at /usr/share/cmake-2.8/Modules/CMakeTestCCompiler.cmake:35 (file):
file Internal CMake error when trying to open file:
/CMakeFiles/CMakeTmp/testCCompiler.c for writing.
Call Stack (most recent call first):
CMakeLists.txt:9 (project)

CMake Error: The source directory "OUTPUT_VARIABLE" does not exist.
Specify --help for usage, or press the help button on the CMake GUI.

CMake Error: Internal CMake error, TryCompile configure of cmake failed

Check for working C compiler: /usr/bin/cc -- broken

CMake Error at /usr/share/cmake-2.8/Modules/CMakeTestCCompiler.cmake:58 (file):
file Internal CMake error when trying to open file:
/CMakeFiles/CMakeError.log for writing.
Call Stack (most recent call first):
CMakeLists.txt:9 (project)

CMake Error at /usr/share/cmake-2.8/Modules/CMakeTestCCompiler.cmake:61 (message):
The C compiler "/usr/bin/cc" is not able to compile a simple test program.

It fails with the following output:





CMake will not be able to correctly generate this project.
Call Stack (most recent call first):
CMakeLists.txt:9 (project)

Configuring incomplete, errors occurred!

CMake Error: Cannot open file for write: /CMakeCache.txt.tmp

CMake Error: : System Error: Permission denied

CMake Error: Unable to open cache file for save. /CMakeCache.txt

CMake Error: : System Error: Permission denied

brian

On Wed, 13 Jan 2016 14:00:38 +0000, Rory Walsh wrote:

If you ran sudo make install you won't need to set the opcode directory. Anyhow, run

sudo apt-get install cmake-gui

from the command line. Then run it

cmake-gui

Then browse for the Csound source and select your build directory. Then hit generate. That will give you full control over what is built and what is not.   

On 13 January 2016 at 12:29, Tarmo Johannes <tarmo.johannes@otsakool.edu.ee> wrote:

Hi,

 

try to find, in which folder are your Csound plugins installed (poably something like /usr/local/lib/csound/plugins ) If you use 32-bit architecture, I guess you need to set in terminal

 

export OPCODE6DIR=/something/plugins

 

before starting Csound.

 

But seems the error is in something else... Maybe there are somewhere leftovers from previous installation and things get messed up?

 

Can you try to run

$ which csound

to see which binary is started and

 

$ldd /usr/local/bin/csound # or wherever is you csound binary

 

to check which libraries are used to see if there is something wrong.

 

I am afraid I have no further idea...

 

tarmo

 

On Wednesday 13 January 2016 12:04:10 you wrote:

> At the moment I'm using just the command line, not CsoundQT.

>

> What

> is the full line I should add to .bashrc and where in the file should I

> paste it?

>

> On Wed, 13 Jan 2016 12:28:17 +0200, Tarmo Johannes wrote:

> > CsoundQt or command line? Can you get some very simple csd work from

>

> command line?

>

> > 64bit is for Csound, how exact numbers it uses, not

>

> architecture. So 32bit system is fine.

>

> > T

> > 13.01.2016 12:23 kirjutas

>

> kuupäeval :

> >> Hi Tarmo,

> >>

> >> Yes, I did sudo ldconfig; I did not

>

> set the OPCODE6DIR64 variable. Is this for 64-bit systems? (mine is

> 32-bit)

>

> >> I installed fltk from source (unzipped the tarball in

>

> the csound directory) and did a re-make, but I still get this type of

>

> error:

> >> 0dBFS level = 32768.0

> >> Csound version 6.07 (double

>

> samples) Jan 12 2016

>

> >> libsndfile-1.0.25

>

> >> UnifiedCSD:

> MonoPolySynthII.csd

>

> >> STARTING FILE

> >> Creating options

> >> Creating

>

> orchestra

>

> >> Creating score

> >> rtmidi: ALSA Raw MIDI module enabled

>

> rtaudio: JACK module enabled

>

> >> define macro unexpected character

>

> )(0x29) awaiting #

>

> >> cannot compile orchestra

> >> end of score.

>

> overall amps: 0.0

>

> >> overall samples out of range: 0

> >> 2 errors in

>

> performance

>

> >> ----

> >>

> >> brian

> >>

> >> On Wed, 13 Jan 2016

>

> 08:34:47 +0200, Tarmo Johannes wrote:

> >>> Hi, some guesses:

> >>>

> >>>

> >>> - did you do

> >>>

> >>> $ sudo ldconfig

> >>>

> >>> to let the system

>

> know about new libraries?

>

> >>> - did you set the OPCODE6DIR64

>

> evironment variable (if you had Csound 5 before, this is needed for

>

> Csound6). Run in terminal before starting csound:

> >>> export

>

> OPCODE6DIR64=/usr/local/lib/csound/plugins64-6.0/

>

> >>> #or where

>

> your Csound6 plugins are installed

>

> >>> or better if you add this

>

> line to $HOME/.bashrc logout and log in again

>

> >>> - are you

>

> perhaps trying it via old CsoundQt? If that was built against Csound5

> you probably need to rebuild CsoundQt as well. See instructions on:

>

>

>

> https://github.com/csound/csound/wiki/CsoundQt-with-Csound6-on-Debian-Ubuntu

> :-a-build-guide [1]

>

>

> https://github.com/csound/csound/wiki/Compiling-CsoundQT-for-Fedora-22-w-Pyt

> hon-and-RTmidi-support [2]

>

> >>> Hope it helps!

> >>>

> >>> tarmo

> >>>

> >>> On Wednesday 13

>

> January 2016 00:02:28 you wrote:

> >>>> No, your efforts have not

>

> been in vain, I guarantee! :)

>

> >>>> I did

>

> indeed build from git, following the instructions in the Debian/Ubuntu

>

> >>>> section. However, since I couldn't build the dependencies, I

>

> installed

>

> >>>> three that I am sure are required: bison, curl and

>

> flex. The Libsndfile

>

> >>>> is installed (in the repos here it is

>

> called libsndfile1, but there is

>

> >>>> also libsndfile-static).

> >>>>

> >>>>

> >>>>

> >>>>

> >>>> Then I followed the build instructions, and

> >>>>

> >>>>

> >>>> all *seemed* to go well. When I go to open an instrument, Csound

>

> starts,

>

> >>>> but then gets an error and stops.

> >>>>

> >>>>

> >>>>

> >>>>

> >>>> So where do I get the cmake-gui and

> >>>>

> >>>> how do I install

>

> it? (sorry for my persistant noobie-ness..)

>

> >>>> brian

> >>>>

> >>>>

> >>>>

> >>>>

> >>>>

> >>>>

> >>>> PS: I'll check back tomorrow, it's

>

> pretty late here now..

>

> >>>> On Tue, 12

> >>>>

> >>>> Jan 2016 22:40:42 +0000, Rory Walsh wrote:

> >>>> > I'm not

>

> sure of the first

>

> >>>> problem but the second sounds

>

> like an issue with the fltk opcodes. You

>

> >>>> built Csound

>

> yourself from the instructions on the Csound git page? I

>

>

> assume you ran cmake at some point to generate your makefiles? Sorry,

>

> >>>> I'm trying to follow what steps you may have taken here!

> >>>>

> >>>> > Anyhow,

> >>>>

> >>>> if you install

>

> cmake-gui and run it and select the Csound source folder

>

>

> along with the build folder, you should get a list of install build

>

> >>>> options. It's here that you can tweak the build settings. But you

>

> did

>

> >>>> build Csound yourself right? Otherwise this email, typed

>

> on a rather

>

> >>>> useless android phone with a screen smaller than

>

> most microorganisms has

>

> >>>> been a complete and utter waste of

>

> time!

>

> >>>> > On 12 Jan 2016 22:27,

> >>>>

> >>>> wrote:

> >>>> >> Hi Rory,

> >>>> >>

> >>>> >>

> >>>> >>

> >>>> >> I'm not

>

> sure I understand. Which folder

>

> >>>> and which command?

> >>>>

> >>>> >> Also, after I do what you said here, do I

> >>>>

> >>>> have to "purge" the old install before doing a make

>

> again?

>

> >>>> >> brian

> >>>> >>

> >>>> >>

> >>>> >>

> >>>> >> On Tue,

>

> 12 Jan 2016 20:49:02 +0000, Rory Walsh wrote:

> >>>> Could be that

>

> you didn't build the fltk opcodes. If you install and run

>

>

> cmake-gui from your Csound build dir you can enable our disable the

>

> >>>> building of any of these opcodes. It may not have built them

>

> breccias

>

> >>>> you dont have fltk installed. Cmake-gui will tell

>

> you more.

>

> >>>> >>> On 12

> >>>>

> >>>> Jan 2016

>

> 20:43, wrote:

> >>>> >>>> Hi again everyone,

> >>>> >>>>

> >>>> >>>>

> >>>> >>>>

> >>>> >>>>

> >>>> >>>> so, the

> >>>>

> >>>> installation of Csound git

>

> version was a success-- but I can't open any

>

> >>>> csound

>

> instruments anymore! I always get some error, each instrument has

>

> >>>> "its own." Examples include: "define macro unexpected character

>

> )(0x29)

>

> >>>> awaiting #" or "error: syntax error, unexpected

>

> INTEGER_TOKEN (token

>

> >>>> "103") from file SawSquareSynth.csd (1)

>

> line 14: >>>FLcolor 103

>

> >>>> Csound mailing list

>

> Csound@listserv.heanet.ie [3] [20]

>

>

> https://listserv.heanet.ie/cgi-bin/wa?A0=CSOUND [4] [21] Send bugs

> reports

>

> >>>> to https://github.com/csound/csound/issues [5] [22]

>

> Discussions of bugs and

>

> >>>> features can be posted here

> >>>>

> >>>> >> Csound mailing list

>

> Csound@listserv.heanet.ie [6] [23]

>

>

> https://listserv.heanet.ie/cgi-bin/wa?A0=CSOUND [7] [24] Send bugs

> reports

>

> >>>> to https://github.com/csound/csound/issues [8] [25]

>

> Discussions of bugs and

>

> >>>> features can be posted here

> >>>>

> >>>> > Csound mailing list

>

> Csound@listserv.heanet.ie [9] [27]

>

>

> https://listserv.heanet.ie/cgi-bin/wa?A0=CSOUND [10] [28] Send bugs

> reports

>

> >>>> to https://github.com/csound/csound/issues [11] [29]

>

> Discussions of bugs and

>

> >>>> features can be posted here

> >>>>

> >>>>

> >>>>

> >>>>

> >>>>

> >>>>

> >>>>

> >>>>

> >>>> Links:

> >>>>

> >>>> ------

> >>>>

> >>>>

> >>>> [1]

>

> https://github.com/csound/csound/blob/develop/BUILD.md#fedora [12]

>

> >>>> [2]

> >>>>

> >>>> mailto:Csound@listserv.heanet.ie [13]

>

> [3]

>

> >>>> https://listserv.heanet.ie/cgi-bin/wa?A0=CSOUND [14]

> >>>>

> >>>>

> >>>> [4]

> >>>>

> >>>> https://github.com/csound/csound/issues [15]

> >>>>

> >>>>

> >>>> [5]

> >>>>

> >>>> mailto:Csound@listserv.heanet.ie [16]

>

> [6]

>

> >>>> https://listserv.heanet.ie/cgi-bin/wa?A0=CSOUND [17]

> >>>>

> >>>>

> >>>> [7]

> >>>>

> >>>> https://github.com/csound/csound/issues [18]

> >>>>

> >>>>

> >>>> [8]

> >>>>

> >>>> mailto:Csound@listserv.heanet.ie [19]

>

> [9]

>

> >>>> https://listserv.heanet.ie/cgi-bin/wa?A0=CSOUND [20]

> >>>>

> >>>>

> >>>> [10]

> >>>>

> >>>> https://github.com/csound/csound/issues [21]

> >>>>

> >>>>

> >>>> [11]

> >>>>

> >>>> mailto:brian@LINUXSYNTHS.COM [22]

> >>>>

> >>>> [12]

>

> mailto:Csound@listserv.heanet.ie [23]

>

> >>>> [13]

>

> https://listserv.heanet.ie/cgi-bin/wa?A0=CSOUND [24]

>

> >>>> [14]

> >>>>

> >>>>

> >>>> https://github.com/csound/csound/issues [25]

> >>>>

> >>>> [15]

> >>>>

> >>>>

> >>>> mailto:brian@LINUXSYNTHS.COM [26]

> >>>>

> >>>> [16]

>

> mailto:Csound@listserv.heanet.ie [27]

>

> >>>> [17]

>

> https://listserv.heanet.ie/cgi-bin/wa?A0=CSOUND [28]

>

> >>>> [18]

> >>>>

> >>>>

> >>>> https://github.com/csound/csound/issues [29]

> >>>>

> >>>> [19]

> >>>>

> >>>>

> >>>> mailto:brian@linuxsynths.com [30]

> >>>>

> >>>> [20]

>

> mailto:Csound@listserv.heanet.ie [31]

>

> >>>> [21]

>

> https://listserv.heanet.ie/cgi-bin/wa?A0=CSOUND [32]

>

> >>>> [22]

> >>>>

> >>>>

> >>>> https://github.com/csound/csound/issues [33]

> >>>>

> >>>> [23]

> >>>>

> >>>>

> >>>> mailto:Csound@listserv.heanet.ie [34]

> >>>>

> >>>> [24]

> >>>>

> >>>>

> >>>> https://listserv.heanet.ie/cgi-bin/wa?A0=CSOUND [35]

>

> [25]

>

> >>>> https://github.com/csound/csound/issues [36]

>

> [26]

>

> >>>> mailto:brian@linuxsynths.com [37]

> >>>>

> >>>> [27]

>

> mailto:Csound@listserv.heanet.ie [38]

>

> >>>> [28]

>

> https://listserv.heanet.ie/cgi-bin/wa?A0=CSOUND [39]

>

> >>>> [29]

> >>>>

> >>>>

> >>>> https://github.com/csound/csound/issues [40]

> >>>>

> >>>>

> >>>>

> >>>>

> >>>> Csound mailing list

> >>>>

> >>>> Csound@listserv.heanet.ie [41]

> >>>>

> >>>>

> >>>> https://listserv.heanet.ie/cgi-bin/wa?A0=CSOUND [42]

>

> Send bugs reports to

>

> >>>> https://github.com/csound/csound/issues

>

> [43]

>

> >>>> Discussions of bugs and features can be posted here

> >>>

> >>> Csound mailing list Csound@listserv.heanet.ie [44]

>

> https://listserv.heanet.ie/cgi-bin/wa?A0=CSOUND [45] Send bugs reports

> to https://github.com/csound/csound/issues [46] Discussions of bugs and

> features can be posted here

>

> >> Csound mailing list

>

> Csound@listserv.heanet.ie [47]

> https://listserv.heanet.ie/cgi-bin/wa?A0=CSOUND [48] Send bugs reports

> to https://github.com/csound/csound/issues [49] Discussions of bugs and

> features can be posted here

>

> > Csound mailing list

>

> Csound@listserv.heanet.ie [51]

> https://listserv.heanet.ie/cgi-bin/wa?A0=CSOUND [52] Send bugs reports

> to https://github.com/csound/csound/issues [53] Discussions of bugs and

> features can be posted here

>

>

>

> Links:

> ------

> [1]

> https://github.com/csound/csound/wiki/CsoundQt-with-Csound6-on-Debian-Ubuntu

> :-a-build-guide [2]

> https://github.com/csound/csound/wiki/Compiling-CsoundQT-for-Fedora-22-w-Pyt

> hon-and-RTmidi-support [3]

> mailto:Csound@listserv.heanet.ie

> [4]

> https://listserv.heanet.ie/cgi-bin/wa?A0=CSOUND

> [5]

> https://github.com/csound/csound/issues

> [6]

> mailto:Csound@listserv.heanet.ie

> [7]

> https://listserv.heanet.ie/cgi-bin/wa?A0=CSOUND

> [8]

> https://github.com/csound/csound/issues

> [9]

> mailto:Csound@listserv.heanet.ie

> [10]

> https://listserv.heanet.ie/cgi-bin/wa?A0=CSOUND

> [11]

> https://github.com/csound/csound/issues

> [12]

> https://github.com/csound/csound/blob/develop/BUILD.md#fedora

> [13]

> mailto:Csound@listserv.heanet.ie

> [14]

> https://listserv.heanet.ie/cgi-bin/wa?A0=CSOUND

> [15]

> https://github.com/csound/csound/issues

> [16]

> mailto:Csound@listserv.heanet.ie

> [17]

> https://listserv.heanet.ie/cgi-bin/wa?A0=CSOUND

> [18]

> https://github.com/csound/csound/issues

> [19]

> mailto:Csound@listserv.heanet.ie

> [20]

> https://listserv.heanet.ie/cgi-bin/wa?A0=CSOUND

> [21]

> https://github.com/csound/csound/issues

> [22]

> mailto:brian@LINUXSYNTHS.COM

> [23] mailto:Csound@listserv.heanet.ie

> [24]

> https://listserv.heanet.ie/cgi-bin/wa?A0=CSOUND

> [25]

> https://github.com/csound/csound/issues

> [26]

> mailto:brian@LINUXSYNTHS.COM

> [27] mailto:Csound@listserv.heanet.ie

> [28]

> https://listserv.heanet.ie/cgi-bin/wa?A0=CSOUND

> [29]

> https://github.com/csound/csound/issues

> [30]

> mailto:brian@linuxsynths.com

> [31] mailto:Csound@listserv.heanet.ie

> [32]

> https://listserv.heanet.ie/cgi-bin/wa?A0=CSOUND

> [33]

> https://github.com/csound/csound/issues

> [34]

> mailto:Csound@listserv.heanet.ie

> [35]

> https://listserv.heanet.ie/cgi-bin/wa?A0=CSOUND

> [36]

> https://github.com/csound/csound/issues

> [37]

> mailto:brian@linuxsynths.com

> [38] mailto:Csound@listserv.heanet.ie

> [39]

> https://listserv.heanet.ie/cgi-bin/wa?A0=CSOUND

> [40]

> https://github.com/csound/csound/issues

> [41]

> mailto:Csound@listserv.heanet.ie

> [42]

> https://listserv.heanet.ie/cgi-bin/wa?A0=CSOUND

> [43]

> https://github.com/csound/csound/issues

> [44]

> mailto:Csound@listserv.heanet.ie

> [45]

> https://listserv.heanet.ie/cgi-bin/wa?A0=CSOUND

> [46]

> https://github.com/csound/csound/issues

> [47]

> mailto:Csound@listserv.heanet.ie

> [48]

> https://listserv.heanet.ie/cgi-bin/wa?A0=CSOUND

> [49]

> https://github.com/csound/csound/issues

> [50]

> mailto:brian@linuxsynths.com

> [51] mailto:Csound@listserv.heanet.ie

> [52]

> https://listserv.heanet.ie/cgi-bin/wa?A0=CSOUND

> [53]

> https://github.com/csound/csound/issues

>

> Csound mailing list

> Csound@listserv.heanet.ie

> https://listserv.heanet.ie/cgi-bin/wa?A0=CSOUND

> Send bugs reports to

> https://github.com/csound/csound/issues

> Discussions of bugs and features can be posted here

 

Csound mailing list Csound@listserv.heanet.ie https://listserv.heanet.ie/cgi-bin/wa?A0=CSOUND Send bugs reports to https://github.com/csound/csound/issues Discussions of bugs and features can be posted here

Csound mailing list Csound@listserv.heanet.ie https://listserv.heanet.ie/cgi-bin/wa?A0=CSOUND Send bugs reports to https://github.com/csound/csound/issues Discussions of bugs and features can be posted here

Always lots to learn..

Do I browse source code or browse build binaries?  I clicked browse binaries and selected the cs6make directory, where I ran make earlier.

The list of things includes many that are "not found," including the fltk library that I also installed in the cs6make directory.

It looks like I have all the right stuff, but in different places..

On Wed, 13 Jan 2016 18:15:15 +0000, Rory Walsh wrote:

The build directory is the directory you run 'make' from. It is not a fixed name. It's simply the directory that you created when trying to build Csound. 

On 13 January 2016 at 18:10, <brian@linuxsynths.com> wrote:

Hi Rory,

I installed cmake-gui (actually, it's provided in the repos here as "cmake-qt-gui"-- I hope that's a valid replacement..)

I'm actually not sure which directory is the build directory: the csound or cs6make directory?

I selected the csound directory and hit generate and got two options:

CMAKE_BUILD_TYPE and CMAKE_INSTALL_PREFIX

Before I do anything, I wanted to check, because I also got these errors in the status window:

 

CMake Error: Cannot open file for write: /CMakeCache.txt.tmp

CMake Error: : System Error: Resource temporarily unavailable

CMake Error: Unable to open cache file for save. /CMakeCache.txt

CMake Error: : System Error: Resource temporarily unavailable

CMake Error at /usr/share/cmake-2.8/Modules/CMakeDetermineCompilerId.cmake:99 (file):
file problem creating directory: /CMakeFiles/2.8.12.2/CompilerIdC
Call Stack (most recent call first):
/usr/share/cmake-2.8/Modules/CMakeDetermineCompilerId.cmake:39 (CMAKE_DETERMINE_COMPILER_ID_BUILD)
/usr/share/cmake-2.8/Modules/CMakeDetermineCCompiler.cmake:131 (CMAKE_DETERMINE_COMPILER_ID)
CMakeLists.txt:9 (project)

CMake Error at /usr/share/cmake-2.8/Modules/CMakeDetermineCompilerId.cmake:99 (file):
file problem creating directory: /CMakeFiles/2.8.12.2/CompilerIdC
Call Stack (most recent call first):
/usr/share/cmake-2.8/Modules/CMakeDetermineCompilerId.cmake:39 (CMAKE_DETERMINE_COMPILER_ID_BUILD)
/usr/share/cmake-2.8/Modules/CMakeDetermineCCompiler.cmake:131 (CMAKE_DETERMINE_COMPILER_ID)
CMakeLists.txt:9 (project)

CMake Error at /usr/share/cmake-2.8/Modules/CMakeDetermineCompilerId.cmake:99 (file):
file problem creating directory: /CMakeFiles/2.8.12.2/CompilerIdC
Call Stack (most recent call first):
/usr/share/cmake-2.8/Modules/CMakeDetermineCompilerId.cmake:39 (CMAKE_DETERMINE_COMPILER_ID_BUILD)
/usr/share/cmake-2.8/Modules/CMakeDetermineCCompiler.cmake:131 (CMAKE_DETERMINE_COMPILER_ID)
CMakeLists.txt:9 (project)

CMake Error at /usr/share/cmake-2.8/Modules/CMakeDetermineCompilerId.cmake:469 (file):
file Internal CMake error when trying to open file:
/CMakeFiles/CMakeError.log for writing.
Call Stack (most recent call first):
/usr/share/cmake-2.8/Modules/CMakeDetermineCompilerId.cmake:48 (CMAKE_DETERMINE_COMPILER_ID_VENDOR)
/usr/share/cmake-2.8/Modules/CMakeDetermineCCompiler.cmake:131 (CMAKE_DETERMINE_COMPILER_ID)
CMakeLists.txt:9 (project)

The C compiler identification is unknown

CMake Error: Could not open file for write in copy operation /CMakeFiles/2.8.12.2/CMakeCCompiler.cmake.tmp

CMake Error: : System Error: No such file or directory

CMake Error at /usr/share/cmake-2.8/Modules/CMakeDetermineCCompiler.cmake:186 (configure_file):
configure_file Problem configuring file
Call Stack (most recent call first):
CMakeLists.txt:9 (project)

CMake Error: Could not find cmake module file: /CMakeFiles/2.8.12.2/CMakeCCompiler.cmake

CMake Error at /usr/share/cmake-2.8/Modules/CMakeDetermineCompilerId.cmake:99 (file):
file problem creating directory: /CMakeFiles/2.8.12.2/CompilerIdCXX
Call Stack (most recent call first):
/usr/share/cmake-2.8/Modules/CMakeDetermineCompilerId.cmake:39 (CMAKE_DETERMINE_COMPILER_ID_BUILD)
/usr/share/cmake-2.8/Modules/CMakeDetermineCXXCompiler.cmake:127 (CMAKE_DETERMINE_COMPILER_ID)
CMakeLists.txt:9 (project)

CMake Error at /usr/share/cmake-2.8/Modules/CMakeDetermineCompilerId.cmake:99 (file):
file problem creating directory: /CMakeFiles/2.8.12.2/CompilerIdCXX
Call Stack (most recent call first):
/usr/share/cmake-2.8/Modules/CMakeDetermineCompilerId.cmake:39 (CMAKE_DETERMINE_COMPILER_ID_BUILD)
/usr/share/cmake-2.8/Modules/CMakeDetermineCXXCompiler.cmake:127 (CMAKE_DETERMINE_COMPILER_ID)
CMakeLists.txt:9 (project)

CMake Error at /usr/share/cmake-2.8/Modules/CMakeDetermineCompilerId.cmake:469 (file):
file Internal CMake error when trying to open file:
/CMakeFiles/CMakeError.log for writing.
Call Stack (most recent call first):
/usr/share/cmake-2.8/Modules/CMakeDetermineCompilerId.cmake:48 (CMAKE_DETERMINE_COMPILER_ID_VENDOR)
/usr/share/cmake-2.8/Modules/CMakeDetermineCXXCompiler.cmake:127 (CMAKE_DETERMINE_COMPILER_ID)
CMakeLists.txt:9 (project)

The CXX compiler identification is unknown

CMake Error: Could not open file for write in copy operation /CMakeFiles/2.8.12.2/CMakeCXXCompiler.cmake.tmp

CMake Error: : System Error: No such file or directory

CMake Error at /usr/share/cmake-2.8/Modules/CMakeDetermineCXXCompiler.cmake:185 (configure_file):
configure_file Problem configuring file
Call Stack (most recent call first):
CMakeLists.txt:9 (project)

CMake Error: Could not find cmake module file: /CMakeFiles/2.8.12.2/CMakeCXXCompiler.cmake

Check for working C compiler: /usr/bin/cc

CMake Error at /usr/share/cmake-2.8/Modules/CMakeTestCCompiler.cmake:35 (file):
file Internal CMake error when trying to open file:
/CMakeFiles/CMakeTmp/testCCompiler.c for writing.
Call Stack (most recent call first):
CMakeLists.txt:9 (project)

CMake Error: The source directory "OUTPUT_VARIABLE" does not exist.
Specify --help for usage, or press the help button on the CMake GUI.

CMake Error: Internal CMake error, TryCompile configure of cmake failed

Check for working C compiler: /usr/bin/cc -- broken

CMake Error at /usr/share/cmake-2.8/Modules/CMakeTestCCompiler.cmake:58 (file):
file Internal CMake error when trying to open file:
/CMakeFiles/CMakeError.log for writing.
Call Stack (most recent call first):
CMakeLists.txt:9 (project)

CMake Error at /usr/share/cmake-2.8/Modules/CMakeTestCCompiler.cmake:61 (message):
The C compiler "/usr/bin/cc" is not able to compile a simple test program.

It fails with the following output:





CMake will not be able to correctly generate this project.
Call Stack (most recent call first):
CMakeLists.txt:9 (project)

Configuring incomplete, errors occurred!

CMake Error: Cannot open file for write: /CMakeCache.txt.tmp

CMake Error: : System Error: Permission denied

CMake Error: Unable to open cache file for save. /CMakeCache.txt

CMake Error: : System Error: Permission denied

 

 

brian

 

On Wed, 13 Jan 2016 14:00:38 +0000, Rory Walsh wrote:

If you ran sudo make install you won't need to set the opcode directory. Anyhow, run

sudo apt-get install cmake-gui

from the command line. Then run it

cmake-gui

Then browse for the Csound source and select your build directory. Then hit generate. That will give you full control over what is built and what is not.   

On 13 January 2016 at 12:29, Tarmo Johannes <tarmo.johannes@otsakool.edu.ee> wrote:

Hi,

 

try to find, in which folder are your Csound plugins installed (poably something like /usr/local/lib/csound/plugins ) If you use 32-bit architecture, I guess you need to set in terminal

 

export OPCODE6DIR=/something/plugins

 

before starting Csound.

 

But seems the error is in something else... Maybe there are somewhere leftovers from previous installation and things get messed up?

 

Can you try to run

$ which csound

to see which binary is started and

 

$ldd /usr/local/bin/csound # or wherever is you csound binary

 

to check which libraries are used to see if there is something wrong.

 

I am afraid I have no further idea...

 

tarmo

 

On Wednesday 13 January 2016 12:04:10 you wrote:

> At the moment I'm using just the command line, not CsoundQT.

>

> What

> is the full line I should add to .bashrc and where in the file should I

> paste it?

>

> On Wed, 13 Jan 2016 12:28:17 +0200, Tarmo Johannes wrote:

> > CsoundQt or command line? Can you get some very simple csd work from

>

> command line?

>

> > 64bit is for Csound, how exact numbers it uses, not

>

> architecture. So 32bit system is fine.

>

> > T

> > 13.01.2016 12:23 kirjutas

>

> kuupäeval :

> >> Hi Tarmo,

> >>

> >> Yes, I did sudo ldconfig; I did not

>

> set the OPCODE6DIR64 variable. Is this for 64-bit systems? (mine is

> 32-bit)

>

> >> I installed fltk from source (unzipped the tarball in

>

> the csound directory) and did a re-make, but I still get this type of

>

> error:

> >> 0dBFS level = 32768.0

> >> Csound version 6.07 (double

>

> samples) Jan 12 2016

>

> >> libsndfile-1.0.25

>

> >> UnifiedCSD:

> MonoPolySynthII.csd

>

> >> STARTING FILE

> >> Creating options

> >> Creating

>

> orchestra

>

> >> Creating score

> >> rtmidi: ALSA Raw MIDI module enabled

>

> rtaudio: JACK module enabled

>

> >> define macro unexpected character

>

> )(0x29) awaiting #

>

> >> cannot compile orchestra

> >> end of score.

>

> overall amps: 0.0

>

> >> overall samples out of range: 0

> >> 2 errors in

>

> performance

>

> >> ----

> >>

> >> brian

> >>

> >> On Wed, 13 Jan 2016

>

> 08:34:47 +0200, Tarmo Johannes wrote:

> >>> Hi, some guesses:

> >>>

> >>>

> >>> - did you do

> >>>

> >>> $ sudo ldconfig

> >>>

> >>> to let the system

>

> know about new libraries?

>

> >>> - did you set the OPCODE6DIR64

>

> evironment variable (if you had Csound 5 before, this is needed for

>

> Csound6). Run in terminal before starting csound:

> >>> export

>

> OPCODE6DIR64=/usr/local/lib/csound/plugins64-6.0/

>

> >>> #or where

>

> your Csound6 plugins are installed

>

> >>> or better if you add this

>

> line to $HOME/.bashrc logout and log in again

>

> >>> - are you

>

> perhaps trying it via old CsoundQt? If that was built against Csound5

> you probably need to rebuild CsoundQt as well. See instructions on:

>

>

>

> https://github.com/csound/csound/wiki/CsoundQt-with-Csound6-on-Debian-Ubuntu

> :-a-build-guide [1]

>

>

> https://github.com/csound/csound/wiki/Compiling-CsoundQT-for-Fedora-22-w-Pyt

> hon-and-RTmidi-support [2]

>

> >>> Hope it helps!

> >>>

> >>> tarmo

> >>>

> >>> On Wednesday 13

>

> January 2016 00:02:28 you wrote:

> >>>> No, your efforts have not

>

> been in vain, I guarantee! :)

>

> >>>> I did

>

> indeed build from git, following the instructions in the Debian/Ubuntu

>

> >>>> section. However, since I couldn't build the dependencies, I

>

> installed

>

> >>>> three that I am sure are required: bison, curl and

>

> flex. The Libsndfile

>

> >>>> is installed (in the repos here it is

>

> called libsndfile1, but there is

>

> >>>> also libsndfile-static).

> >>>>

> >>>>

> >>>>

> >>>>

> >>>> Then I followed the build instructions, and

> >>>>

> >>>>

> >>>> all *seemed* to go well. When I go to open an instrument, Csound

>

> starts,

>

> >>>> but then gets an error and stops.

> >>>>

> >>>>

> >>>>

> >>>>

> >>>> So where do I get the cmake-gui and

> >>>>

> >>>> how do I install

>

> it? (sorry for my persistant noobie-ness..)

>

> >>>> brian

> >>>>

> >>>>

> >>>>

> >>>>

> >>>>

> >>>>

> >>>> PS: I'll check back tomorrow, it's

>

> pretty late here now..

>

> >>>> On Tue, 12

> >>>>

> >>>> Jan 2016 22:40:42 +0000, Rory Walsh wrote:

> >>>> > I'm not

>

> sure of the first

>

> >>>> problem but the second sounds

>

> like an issue with the fltk opcodes. You

>

> >>>> built Csound

>

> yourself from the instructions on the Csound git page? I

>

>

> assume you ran cmake at some point to generate your makefiles? Sorry,

>

> >>>> I'm trying to follow what steps you may have taken here!

> >>>>

> >>>> > Anyhow,

> >>>>

> >>>> if you install

>

> cmake-gui and run it and select the Csound source folder

>

>

> along with the build folder, you should get a list of install build

>

> >>>> options. It's here that you can tweak the build settings. But you

>

> did

>

> >>>> build Csound yourself right? Otherwise this email, typed

>

> on a rather

>

> >>>> useless android phone with a screen smaller than

>

> most microorganisms has

>

> >>>> been a complete and utter waste of

>

> time!

>

> >>>> > On 12 Jan 2016 22:27,

> >>>>

> >>>> wrote:

> >>>> >> Hi Rory,

> >>>> >>

> >>>> >>

> >>>> >>

> >>>> >> I'm not

>

> sure I understand. Which folder

>

> >>>> and which command?

> >>>>

> >>>> >> Also, after I do what you said here, do I

> >>>>

> >>>> have to "purge" the old install before doing a make

>

> again?

>

> >>>> >> brian

> >>>> >>

> >>>> >>

> >>>> >>

> >>>> >> On Tue,

>

> 12 Jan 2016 20:49:02 +0000, Rory Walsh wrote:

> >>>> Could be that

>

> you didn't build the fltk opcodes. If you install and run

>

>

> cmake-gui from your Csound build dir you can enable our disable the

>

> >>>> building of any of these opcodes. It may not have built them

>

> breccias

>

> >>>> you dont have fltk installed. Cmake-gui will tell

>

> you more.

>

> >>>> >>> On 12

> >>>>

> >>>> Jan 2016

>

> 20:43, wrote:

> >>>> >>>> Hi again everyone,

> >>>> >>>>

> >>>> >>>>

> >>>> >>>>

> >>>> >>>>

> >>>> >>>> so, the

> >>>>

> >>>> installation of Csound git

>

> version was a success-- but I can't open any

>

> >>>> csound

>

> instruments anymore! I always get some error, each instrument has

>

> >>>> "its own." Examples include: "define macro unexpected character

>

> )(0x29)

>

> >>>> awaiting #" or "error: syntax error, unexpected

>

> INTEGER_TOKEN (token

>

> >>>> "103") from file SawSquareSynth.csd (1)

>

> line 14: >>>FLcolor 103

>

> >>>> Csound mailing list

>

> Csound@listserv.heanet.ie [3] [20]

>

>

> https://listserv.heanet.ie/cgi-bin/wa?A0=CSOUND [4] [21] Send bugs

> reports

>

> >>>> to https://github.com/csound/csound/issues [5] [22]

>

> Discussions of bugs and

>

> >>>> features can be posted here

> >>>>

> >>>> >> Csound mailing list

>

> Csound@listserv.heanet.ie [6] [23]

>

>

> https://listserv.heanet.ie/cgi-bin/wa?A0=CSOUND [7] [24] Send bugs

> reports

>

> >>>> to https://github.com/csound/csound/issues [8] [25]

>

> Discussions of bugs and

>

> >>>> features can be posted here

> >>>>

> >>>> > Csound mailing list

>

> Csound@listserv.heanet.ie [9] [27]

>

>

> https://listserv.heanet.ie/cgi-bin/wa?A0=CSOUND [10] [28] Send bugs

> reports

>

> >>>> to https://github.com/csound/csound/issues [11] [29]

>

> Discussions of bugs and

>

> >>>> features can be posted here

> >>>>

> >>>>

> >>>>

> >>>>

> >>>>

> >>>>

> >>>>

> >>>>

> >>>> Links:

> >>>>

> >>>> ------

> >>>>

> >>>>

> >>>> [1]

>

> https://github.com/csound/csound/blob/develop/BUILD.md#fedora [12]

>

> >>>> [2]

> >>>>

> >>>> mailto:Csound@listserv.heanet.ie [13]

>

> [3]

>

> >>>> https://listserv.heanet.ie/cgi-bin/wa?A0=CSOUND [14]

> >>>>

> >>>>

> >>>> [4]

> >>>>

> >>>> https://github.com/csound/csound/issues [15]

> >>>>

> >>>>

> >>>> [5]

> >>>>

> >>>> mailto:Csound@listserv.heanet.ie [16]

>

> [6]

>

> >>>> https://listserv.heanet.ie/cgi-bin/wa?A0=CSOUND [17]

> >>>>

> >>>>

> >>>> [7]

> >>>>

> >>>> https://github.com/csound/csound/issues [18]

> >>>>

> >>>>

> >>>> [8]

> >>>>

> >>>> mailto:Csound@listserv.heanet.ie [19]

>

> [9]

>

> >>>> https://listserv.heanet.ie/cgi-bin/wa?A0=CSOUND [20]

> >>>>

> >>>>

> >>>> [10]

> >>>>

> >>>> https://github.com/csound/csound/issues [21]

> >>>>

> >>>>

> >>>> [11]

> >>>>

> >>>> mailto:brian@LINUXSYNTHS.COM [22]

> >>>>

> >>>> [12]

>

> mailto:Csound@listserv.heanet.ie [23]

>

> >>>> [13]

>

> https://listserv.heanet.ie/cgi-bin/wa?A0=CSOUND [24]

>

> >>>> [14]

> >>>>

> >>>>

> >>>> https://github.com/csound/csound/issues [25]

> >>>>

> >>>> [15]

> >>>>

> >>>>

> >>>> mailto:brian@LINUXSYNTHS.COM [26]

> >>>>

> >>>> [16]

>

> mailto:Csound@listserv.heanet.ie [27]

>

> >>>> [17]

>

> https://listserv.heanet.ie/cgi-bin/wa?A0=CSOUND [28]

>

> >>>> [18]

> >>>>

> >>>>

> >>>> https://github.com/csound/csound/issues [29]

> >>>>

> >>>> [19]

> >>>>

> >>>>

> >>>> mailto:brian@linuxsynths.com [30]

> >>>>

> >>>> [20]

>

> mailto:Csound@listserv.heanet.ie [31]

>

> >>>> [21]

>

> https://listserv.heanet.ie/cgi-bin/wa?A0=CSOUND [32]

>

> >>>> [22]

> >>>>

> >>>>

> >>>> https://github.com/csound/csound/issues [33]

> >>>>

> >>>> [23]

> >>>>

> >>>>

> >>>> mailto:Csound@listserv.heanet.ie [34]

> >>>>

> >>>> [24]

> >>>>

> >>>>

> >>>> https://listserv.heanet.ie/cgi-bin/wa?A0=CSOUND [35]

>

> [25]

>

> >>>> https://github.com/csound/csound/issues [36]

>

> [26]

>

> >>>> mailto:brian@linuxsynths.com [37]

> >>>>

> >>>> [27]

>

> mailto:Csound@listserv.heanet.ie [38]

>

> >>>> [28]

>

> https://listserv.heanet.ie/cgi-bin/wa?A0=CSOUND [39]

>

> >>>> [29]

> >>>>

> >>>>

> >>>> https://github.com/csound/csound/issues [40]

> >>>>

> >>>>

> >>>>

> >>>>

> >>>> Csound mailing list

> >>>>

> >>>> Csound@listserv.heanet.ie [41]

> >>>>

> >>>>

> >>>> https://listserv.heanet.ie/cgi-bin/wa?A0=CSOUND [42]

>

> Send bugs reports to

>

> >>>> https://github.com/csound/csound/issues

>

> [43]

>

> >>>> Discussions of bugs and features can be posted here

> >>>

> >>> Csound mailing list Csound@listserv.heanet.ie [44]

>

> https://listserv.heanet.ie/cgi-bin/wa?A0=CSOUND [45] Send bugs reports

> to https://github.com/csound/csound/issues [46] Discussions of bugs and

> features can be posted here

>

> >> Csound mailing list

>

> Csound@listserv.heanet.ie [47]

> https://listserv.heanet.ie/cgi-bin/wa?A0=CSOUND [48] Send bugs reports

> to https://github.com/csound/csound/issues [49] Discussions of bugs and

> features can be posted here

>

> > Csound mailing list

>

> Csound@listserv.heanet.ie [51]

> https://listserv.heanet.ie/cgi-bin/wa?A0=CSOUND [52] Send bugs reports

> to https://github.com/csound/csound/issues [53] Discussions of bugs and

> features can be posted here

>

>

>

> Links:

> ------

> [1]

> https://github.com/csound/csound/wiki/CsoundQt-with-Csound6-on-Debian-Ubuntu

> :-a-build-guide [2]

> https://github.com/csound/csound/wiki/Compiling-CsoundQT-for-Fedora-22-w-Pyt

> hon-and-RTmidi-support [3]

> mailto:Csound@listserv.heanet.ie

> [4]

> https://listserv.heanet.ie/cgi-bin/wa?A0=CSOUND

> [5]

> https://github.com/csound/csound/issues

> [6]

> mailto:Csound@listserv.heanet.ie

> [7]

> https://listserv.heanet.ie/cgi-bin/wa?A0=CSOUND

> [8]

> https://github.com/csound/csound/issues

> [9]

> mailto:Csound@listserv.heanet.ie

> [10]

> https://listserv.heanet.ie/cgi-bin/wa?A0=CSOUND

> [11]

> https://github.com/csound/csound/issues

> [12]

> https://github.com/csound/csound/blob/develop/BUILD.md#fedora

> [13]

> mailto:Csound@listserv.heanet.ie

> [14]

> https://listserv.heanet.ie/cgi-bin/wa?A0=CSOUND

> [15]

> https://github.com/csound/csound/issues

> [16]

> mailto:Csound@listserv.heanet.ie

> [17]

> https://listserv.heanet.ie/cgi-bin/wa?A0=CSOUND

> [18]

> https://github.com/csound/csound/issues

> [19]

> mailto:Csound@listserv.heanet.ie

> [20]

> https://listserv.heanet.ie/cgi-bin/wa?A0=CSOUND

> [21]

> https://github.com/csound/csound/issues

> [22]

> mailto:brian@LINUXSYNTHS.COM

> [23] mailto:Csound@listserv.heanet.ie

> [24]

> https://listserv.heanet.ie/cgi-bin/wa?A0=CSOUND

> [25]

> https://github.com/csound/csound/issues

> [26]

> mailto:brian@LINUXSYNTHS.COM

> [27] mailto:Csound@listserv.heanet.ie

> [28]

> https://listserv.heanet.ie/cgi-bin/wa?A0=CSOUND

> [29]

> https://github.com/csound/csound/issues

> [30]

> mailto:brian@linuxsynths.com

> [31] mailto:Csound@listserv.heanet.ie

> [32]

> https://listserv.heanet.ie/cgi-bin/wa?A0=CSOUND

> [33]

> https://github.com/csound/csound/issues

> [34]

> mailto:Csound@listserv.heanet.ie

> [35]

> https://listserv.heanet.ie/cgi-bin/wa?A0=CSOUND

> [36]

> https://github.com/csound/csound/issues

> [37]

> mailto:brian@linuxsynths.com

> [38] mailto:Csound@listserv.heanet.ie

> [39]

> https://listserv.heanet.ie/cgi-bin/wa?A0=CSOUND

> [40]

> https://github.com/csound/csound/issues

> [41]

> mailto:Csound@listserv.heanet.ie

> [42]

> https://listserv.heanet.ie/cgi-bin/wa?A0=CSOUND

> [43]

> https://github.com/csound/csound/issues

> [44]

> mailto:Csound@listserv.heanet.ie

> [45]

> https://listserv.heanet.ie/cgi-bin/wa?A0=CSOUND

> [46]

> https://github.com/csound/csound/issues

> [47]

> mailto:Csound@listserv.heanet.ie

> [48]

> https://listserv.heanet.ie/cgi-bin/wa?A0=CSOUND

> [49]

> https://github.com/csound/csound/issues

> [50]

> mailto:brian@linuxsynths.com

> [51] mailto:Csound@listserv.heanet.ie

> [52]

> https://listserv.heanet.ie/cgi-bin/wa?A0=CSOUND

> [53]

> https://github.com/csound/csound/issues

>

> Csound mailing list

> Csound@listserv.heanet.ie

> https://listserv.heanet.ie/cgi-bin/wa?A0=CSOUND

> Send bugs reports to

> https://github.com/csound/csound/issues

> Discussions of bugs and features can be posted here

 

Csound mailing list Csound@listserv.heanet.ie https://listserv.heanet.ie/cgi-bin/wa?A0=CSOUND Send bugs reports to https://github.com/csound/csound/issues Discussions of bugs and features can be posted here

Csound mailing list Csound@listserv.heanet.ie https://listserv.heanet.ie/cgi-bin/wa?A0=CSOUND Send bugs reports to https://github.com/csound/csound/issues Discussions of bugs and features can be posted here

 

 

Csound mailing list Csound@listserv.heanet.ie https://listserv.heanet.ie/cgi-bin/wa?A0=CSOUND Send bugs reports to https://github.com/csound/csound/issues Discussions of bugs and features can be posted here

Csound mailing list Csound@listserv.heanet.ie https://listserv.heanet.ie/cgi-bin/wa?A0=CSOUND Send bugs reports to https://github.com/csound/csound/issues Discussions of bugs and features can be posted here