Dear List,

I'm in the process of building csound from source at the moment. I'm 
using 64-bit linux (Ubuntu Studio).

The only option I really wanted to enable was "useDouble".

I've managed to get csound to compile, with only one hitch - it was 
failing due to an error (msgfmt not found) so, after Google'ing, I 
installed GNU gettext. I don't know if this should go in the manual in 
the "building csound" section.

Then it seemed to compile correctly. I couldn't find the instructions 
for installing, so I executed ./install.py - I hope this was the right 
thing to do, it doesn't say in the "building csound" manual page.

I then realised I needed to compile with the option 
"dynamicCsoundLibrary=1", if I wanted to link to it with the C API, so I 
enabled that and tried again.

Now it seemed to work - but csound was crashing when called from the 
host app, saying it couldn't load the #include files - csound seemed to 
expect them to be relative to the CURRENT directory, rather than the 
directory where the main input csd is stored. This worked fine with 
csound 5.12.

To test with a simpler csd, I used a slightly modified midiin.csd (the 
manual example). It failed with the error "printks not initialised", 
again this worked fine with 5.12.

I tried building with "buildNewParser=0", and now everything works, BUT 
I'm getting a LOT of text on the screen. I redirected the output to a 
file, it's 310720 lines long!!!!

The first part is standard csound output. Then it starts doing this:

groups: sr = 44100
modified opcod: =.r
treqd i, tfound c
xincod = 0
treqd r, tfound r
sr  =.r 44100
LINE 10:
groups: ksmps = 64
modified opcod: =.r
treqd i, tfound c
xincod = 0
treqd r, tfound r
ksmps   =.r 64

and later in the file there's quite a lot of this:

135 0x1326300   (nil)   (nil)   0x1329630   0x131f020   (nil)   1   -1.0
136 0x1329630   (nil)   (nil)   0x132c820   0x1326300   (nil)   1   -1.0
137 0x132c820   (nil)   (nil)   0x132fad0   0x1329630   (nil)   1   -1.0
138 0x132fad0   (nil)   (nil)   0x1330e50   0x132c820   (nil)   1   -1.0
139 0x1330e50   (nil)   (nil)   0x1331fb0   0x132fad0   (nil)   1   -1.0


And so on and so on...
Once it's finished splurging to the screen (or file), it actually works 
fine.

I'm assuming I need to set an option somewhere in compilation, but I 
don't really know which... In fact I'd really like a fairly standard set 
of options, I don't really need any of the more peculiar opcodes at the 
moment, just doubles and dynamic library.

Thanks in advance,

Joe

Dear list,

I already sent this same message with a different subject a few days ago 
- please ignore if you read it already. However, as I haven't yet had a 
reply I thought I'd ask again, just in case anyone can help me! 
Basically I'm still in the same situation, I've tried a few other 
options but to no avail.

Joe

On 13/03/11 21:01, Joseph Sanger wrote:
> Dear List,
>
> I'm in the process of building csound from source at the moment. I'm 
> using 64-bit linux (Ubuntu Studio).
>
> The only option I really wanted to enable was "useDouble".
>
> I've managed to get csound to compile, with only one hitch - it was 
> failing due to an error (msgfmt not found) so, after Google'ing, I 
> installed GNU gettext. I don't know if this should go in the manual in 
> the "building csound" section.
>
> Then it seemed to compile correctly. I couldn't find the instructions 
> for installing, so I executed ./install.py - I hope this was the right 
> thing to do, it doesn't say in the "building csound" manual page.
>
> I then realised I needed to compile with the option 
> "dynamicCsoundLibrary=1", if I wanted to link to it with the C API, so 
> I enabled that and tried again.
>
> Now it seemed to work - but csound was crashing when called from the 
> host app, saying it couldn't load the #include files - csound seemed 
> to expect them to be relative to the CURRENT directory, rather than 
> the directory where the main input csd is stored. This worked fine 
> with csound 5.12.
>
> To test with a simpler csd, I used a slightly modified midiin.csd (the 
> manual example). It failed with the error "printks not initialised", 
> again this worked fine with 5.12.
>
> I tried building with "buildNewParser=0", and now everything works, 
> BUT I'm getting a LOT of text on the screen. I redirected the output 
> to a file, it's 310720 lines long!!!!
>
> The first part is standard csound output. Then it starts doing this:
>
> groups: sr = 44100
> modified opcod: =.r
> treqd i, tfound c
> xincod = 0
> treqd r, tfound r
> sr  =.r 44100
> LINE 10:
> groups: ksmps = 64
> modified opcod: =.r
> treqd i, tfound c
> xincod = 0
> treqd r, tfound r
> ksmps   =.r 64
>
> and later in the file there's quite a lot of this:
>
> 135 0x1326300   (nil)   (nil)   0x1329630   0x131f020   (nil)   1   -1.0
> 136 0x1329630   (nil)   (nil)   0x132c820   0x1326300   (nil)   1   -1.0
> 137 0x132c820   (nil)   (nil)   0x132fad0   0x1329630   (nil)   1   -1.0
> 138 0x132fad0   (nil)   (nil)   0x1330e50   0x132c820   (nil)   1   -1.0
> 139 0x1330e50   (nil)   (nil)   0x1331fb0   0x132fad0   (nil)   1   -1.0
>
>
> And so on and so on...
> Once it's finished splurging to the screen (or file), it actually 
> works fine.
>
> I'm assuming I need to set an option somewhere in compilation, but I 
> don't really know which... In fact I'd really like a fairly standard 
> set of options, I don't really need any of the more peculiar opcodes 
> at the moment, just doubles and dynamic library.
>
> Thanks in advance,
>
> Joe
>
>
>

I did see your post but didn't have time to respond. Are you sure that
you have OPCODEDIR set to the correct location? check with 'echo
$OPCODEDIR' from the terminal. This should have been done
automatically by install.py but you should double check just in case.

On top of this I don't see how your host app would crash because it
can't see include files, your host app wouldn't build if the compiler
couldn't find the include files.

Finally, after building Csound can you run Csound with a simple csd
from the command line from within your Csound build directory? If you
can then we know Csound is ok and the problem is most likely something
to do with OPCODEDIR.

Rory.



On 16 March 2011 00:10, Joseph Sanger  wrote:
> Dear list,
>
> I already sent this same message with a different subject a few days ago -
> please ignore if you read it already. However, as I haven't yet had a reply
> I thought I'd ask again, just in case anyone can help me! Basically I'm
> still in the same situation, I've tried a few other options but to no avail.
>
> Joe
>
> On 13/03/11 21:01, Joseph Sanger wrote:
>>
>> Dear List,
>>
>> I'm in the process of building csound from source at the moment. I'm using
>> 64-bit linux (Ubuntu Studio).
>>
>> The only option I really wanted to enable was "useDouble".
>>
>> I've managed to get csound to compile, with only one hitch - it was
>> failing due to an error (msgfmt not found) so, after Google'ing, I installed
>> GNU gettext. I don't know if this should go in the manual in the "building
>> csound" section.
>>
>> Then it seemed to compile correctly. I couldn't find the instructions for
>> installing, so I executed ./install.py - I hope this was the right thing to
>> do, it doesn't say in the "building csound" manual page.
>>
>> I then realised I needed to compile with the option
>> "dynamicCsoundLibrary=1", if I wanted to link to it with the C API, so I
>> enabled that and tried again.
>>
>> Now it seemed to work - but csound was crashing when called from the host
>> app, saying it couldn't load the #include files - csound seemed to expect
>> them to be relative to the CURRENT directory, rather than the directory
>> where the main input csd is stored. This worked fine with csound 5.12.
>>
>> To test with a simpler csd, I used a slightly modified midiin.csd (the
>> manual example). It failed with the error "printks not initialised", again
>> this worked fine with 5.12.
>>
>> I tried building with "buildNewParser=0", and now everything works, BUT
>> I'm getting a LOT of text on the screen. I redirected the output to a file,
>> it's 310720 lines long!!!!
>>
>> The first part is standard csound output. Then it starts doing this:
>>
>> groups: sr = 44100
>> modified opcod: =.r
>> treqd i, tfound c
>> xincod = 0
>> treqd r, tfound r
>> sr  =.r 44100
>> LINE 10:
>> groups: ksmps = 64
>> modified opcod: =.r
>> treqd i, tfound c
>> xincod = 0
>> treqd r, tfound r
>> ksmps   =.r 64
>>
>> and later in the file there's quite a lot of this:
>>
>> 135 0x1326300   (nil)   (nil)   0x1329630   0x131f020   (nil)   1   -1.0
>> 136 0x1329630   (nil)   (nil)   0x132c820   0x1326300   (nil)   1   -1.0
>> 137 0x132c820   (nil)   (nil)   0x132fad0   0x1329630   (nil)   1   -1.0
>> 138 0x132fad0   (nil)   (nil)   0x1330e50   0x132c820   (nil)   1   -1.0
>> 139 0x1330e50   (nil)   (nil)   0x1331fb0   0x132fad0   (nil)   1   -1.0
>>
>>
>> And so on and so on...
>> Once it's finished splurging to the screen (or file), it actually works
>> fine.
>>
>> I'm assuming I need to set an option somewhere in compilation, but I don't
>> really know which... In fact I'd really like a fairly standard set of
>> options, I don't really need any of the more peculiar opcodes at the moment,
>> just doubles and dynamic library.
>>
>> Thanks in advance,
>>
>> Joe
>>
>>
>>
>
>
> --
> Joseph Sanger
> Blueberry Eikaiwa
> www.bbeikaiwa.com
>
>
>
> Send bugs reports to the Sourceforge bug tracker
>           https://sourceforge.net/tracker/?group_id=81968&atid=564599
> Discussions of bugs and features can be posted here
> To unsubscribe, send email sympa@lists.bath.ac.uk with body "unsubscribe
> csound"
>
>


Send bugs reports to the Sourceforge bug tracker
            https://sourceforge.net/tracker/?group_id=81968&atid=564599
Discussions of bugs and features can be posted here
To unsubscribe, send email sympa@lists.bath.ac.uk with body "unsubscribe csound"

Hello, thanks for the quick reply,

Well - I did set OPCODEDIR64, and the whole thing works fine if I set 
"buildNewParser=0" - except I get an enormous amount of text on the 
screen. However, I will double check later when I get home from work.

Joe

On 16/03/11 09:37, Rory Walsh wrote:
> I did see your post but didn't have time to respond. Are you sure that
> you have OPCODEDIR set to the correct location? check with 'echo
> $OPCODEDIR' from the terminal. This should have been done
> automatically by install.py but you should double check just in case.
>
> On top of this I don't see how your host app would crash because it
> can't see include files, your host app wouldn't build if the compiler
> couldn't find the include files.
>
> Finally, after building Csound can you run Csound with a simple csd
> from the command line from within your Csound build directory? If you
> can then we know Csound is ok and the problem is most likely something
> to do with OPCODEDIR.
>
> Rory.
>
>
>
> On 16 March 2011 00:10, Joseph Sanger  wrote:
>> Dear list,
>>
>> I already sent this same message with a different subject a few days ago -
>> please ignore if you read it already. However, as I haven't yet had a reply
>> I thought I'd ask again, just in case anyone can help me! Basically I'm
>> still in the same situation, I've tried a few other options but to no avail.
>>
>> Joe
>>
>> On 13/03/11 21:01, Joseph Sanger wrote:
>>> Dear List,
>>>
>>> I'm in the process of building csound from source at the moment. I'm using
>>> 64-bit linux (Ubuntu Studio).
>>>
>>> The only option I really wanted to enable was "useDouble".
>>>
>>> I've managed to get csound to compile, with only one hitch - it was
>>> failing due to an error (msgfmt not found) so, after Google'ing, I installed
>>> GNU gettext. I don't know if this should go in the manual in the "building
>>> csound" section.
>>>
>>> Then it seemed to compile correctly. I couldn't find the instructions for
>>> installing, so I executed ./install.py - I hope this was the right thing to
>>> do, it doesn't say in the "building csound" manual page.
>>>
>>> I then realised I needed to compile with the option
>>> "dynamicCsoundLibrary=1", if I wanted to link to it with the C API, so I
>>> enabled that and tried again.
>>>
>>> Now it seemed to work - but csound was crashing when called from the host
>>> app, saying it couldn't load the #include files - csound seemed to expect
>>> them to be relative to the CURRENT directory, rather than the directory
>>> where the main input csd is stored. This worked fine with csound 5.12.
>>>
>>> To test with a simpler csd, I used a slightly modified midiin.csd (the
>>> manual example). It failed with the error "printks not initialised", again
>>> this worked fine with 5.12.
>>>
>>> I tried building with "buildNewParser=0", and now everything works, BUT
>>> I'm getting a LOT of text on the screen. I redirected the output to a file,
>>> it's 310720 lines long!!!!
>>>
>>> The first part is standard csound output. Then it starts doing this:
>>>
>>> groups: sr = 44100
>>> modified opcod: =.r
>>> treqd i, tfound c
>>> xincod = 0
>>> treqd r, tfound r
>>> sr  =.r 44100
>>> LINE 10:
>>> groups: ksmps = 64
>>> modified opcod: =.r
>>> treqd i, tfound c
>>> xincod = 0
>>> treqd r, tfound r
>>> ksmps   =.r 64
>>>
>>> and later in the file there's quite a lot of this:
>>>
>>> 135 0x1326300   (nil)   (nil)   0x1329630   0x131f020   (nil)   1   -1.0
>>> 136 0x1329630   (nil)   (nil)   0x132c820   0x1326300   (nil)   1   -1.0
>>> 137 0x132c820   (nil)   (nil)   0x132fad0   0x1329630   (nil)   1   -1.0
>>> 138 0x132fad0   (nil)   (nil)   0x1330e50   0x132c820   (nil)   1   -1.0
>>> 139 0x1330e50   (nil)   (nil)   0x1331fb0   0x132fad0   (nil)   1   -1.0
>>>
>>>
>>> And so on and so on...
>>> Once it's finished splurging to the screen (or file), it actually works
>>> fine.
>>>
>>> I'm assuming I need to set an option somewhere in compilation, but I don't
>>> really know which... In fact I'd really like a fairly standard set of
>>> options, I don't really need any of the more peculiar opcodes at the moment,
>>> just doubles and dynamic library.
>>>
>>> Thanks in advance,
>>>
>>> Joe
>>>
>>>
>>>
>>
>> --
>> Joseph Sanger
>> Blueberry Eikaiwa
>> www.bbeikaiwa.com
>>
>>
>>
>> Send bugs reports to the Sourceforge bug tracker
>>            https://sourceforge.net/tracker/?group_id=81968&atid=564599
>> Discussions of bugs and features can be posted here
>> To unsubscribe, send email sympa@lists.bath.ac.uk with body "unsubscribe
>> csound"
>>
>>
>
> Send bugs reports to the Sourceforge bug tracker
>              https://sourceforge.net/tracker/?group_id=81968&atid=564599
> Discussions of bugs and features can be posted here
> To unsubscribe, send email sympa@lists.bath.ac.uk with body "unsubscribe csound"
>

If you get a chance try building with the normal parser again and
we'll take it from there.

On 16 March 2011 01:09, Joseph Sanger  wrote:
> Hello, thanks for the quick reply,
>
> Well - I did set OPCODEDIR64, and the whole thing works fine if I set
> "buildNewParser=0" - except I get an enormous amount of text on the screen.
> However, I will double check later when I get home from work.
>
> Joe
>
> On 16/03/11 09:37, Rory Walsh wrote:
>>
>> I did see your post but didn't have time to respond. Are you sure that
>> you have OPCODEDIR set to the correct location? check with 'echo
>> $OPCODEDIR' from the terminal. This should have been done
>> automatically by install.py but you should double check just in case.
>>
>> On top of this I don't see how your host app would crash because it
>> can't see include files, your host app wouldn't build if the compiler
>> couldn't find the include files.
>>
>> Finally, after building Csound can you run Csound with a simple csd
>> from the command line from within your Csound build directory? If you
>> can then we know Csound is ok and the problem is most likely something
>> to do with OPCODEDIR.
>>
>> Rory.
>>
>>
>>
>> On 16 March 2011 00:10, Joseph Sanger  wrote:
>>>
>>> Dear list,
>>>
>>> I already sent this same message with a different subject a few days ago
>>> -
>>> please ignore if you read it already. However, as I haven't yet had a
>>> reply
>>> I thought I'd ask again, just in case anyone can help me! Basically I'm
>>> still in the same situation, I've tried a few other options but to no
>>> avail.
>>>
>>> Joe
>>>
>>> On 13/03/11 21:01, Joseph Sanger wrote:
>>>>
>>>> Dear List,
>>>>
>>>> I'm in the process of building csound from source at the moment. I'm
>>>> using
>>>> 64-bit linux (Ubuntu Studio).
>>>>
>>>> The only option I really wanted to enable was "useDouble".
>>>>
>>>> I've managed to get csound to compile, with only one hitch - it was
>>>> failing due to an error (msgfmt not found) so, after Google'ing, I
>>>> installed
>>>> GNU gettext. I don't know if this should go in the manual in the
>>>> "building
>>>> csound" section.
>>>>
>>>> Then it seemed to compile correctly. I couldn't find the instructions
>>>> for
>>>> installing, so I executed ./install.py - I hope this was the right thing
>>>> to
>>>> do, it doesn't say in the "building csound" manual page.
>>>>
>>>> I then realised I needed to compile with the option
>>>> "dynamicCsoundLibrary=1", if I wanted to link to it with the C API, so I
>>>> enabled that and tried again.
>>>>
>>>> Now it seemed to work - but csound was crashing when called from the
>>>> host
>>>> app, saying it couldn't load the #include files - csound seemed to
>>>> expect
>>>> them to be relative to the CURRENT directory, rather than the directory
>>>> where the main input csd is stored. This worked fine with csound 5.12.
>>>>
>>>> To test with a simpler csd, I used a slightly modified midiin.csd (the
>>>> manual example). It failed with the error "printks not initialised",
>>>> again
>>>> this worked fine with 5.12.
>>>>
>>>> I tried building with "buildNewParser=0", and now everything works, BUT
>>>> I'm getting a LOT of text on the screen. I redirected the output to a
>>>> file,
>>>> it's 310720 lines long!!!!
>>>>
>>>> The first part is standard csound output. Then it starts doing this:
>>>>
>>>> groups: sr = 44100
>>>> modified opcod: =.r
>>>> treqd i, tfound c
>>>> xincod = 0
>>>> treqd r, tfound r
>>>> sr  =.r 44100
>>>> LINE 10:
>>>> groups: ksmps = 64
>>>> modified opcod: =.r
>>>> treqd i, tfound c
>>>> xincod = 0
>>>> treqd r, tfound r
>>>> ksmps   =.r 64
>>>>
>>>> and later in the file there's quite a lot of this:
>>>>
>>>> 135 0x1326300   (nil)   (nil)   0x1329630   0x131f020   (nil)   1   -1.0
>>>> 136 0x1329630   (nil)   (nil)   0x132c820   0x1326300   (nil)   1   -1.0
>>>> 137 0x132c820   (nil)   (nil)   0x132fad0   0x1329630   (nil)   1   -1.0
>>>> 138 0x132fad0   (nil)   (nil)   0x1330e50   0x132c820   (nil)   1   -1.0
>>>> 139 0x1330e50   (nil)   (nil)   0x1331fb0   0x132fad0   (nil)   1   -1.0
>>>>
>>>>
>>>> And so on and so on...
>>>> Once it's finished splurging to the screen (or file), it actually works
>>>> fine.
>>>>
>>>> I'm assuming I need to set an option somewhere in compilation, but I
>>>> don't
>>>> really know which... In fact I'd really like a fairly standard set of
>>>> options, I don't really need any of the more peculiar opcodes at the
>>>> moment,
>>>> just doubles and dynamic library.
>>>>
>>>> Thanks in advance,
>>>>
>>>> Joe
>>>>
>>>>
>>>>
>>>
>>> --
>>> Joseph Sanger
>>> Blueberry Eikaiwa
>>> www.bbeikaiwa.com
>>>
>>>
>>>
>>> Send bugs reports to the Sourceforge bug tracker
>>>           https://sourceforge.net/tracker/?group_id=81968&atid=564599
>>> Discussions of bugs and features can be posted here
>>> To unsubscribe, send email sympa@lists.bath.ac.uk with body "unsubscribe
>>> csound"
>>>
>>>
>>
>> Send bugs reports to the Sourceforge bug tracker
>>             https://sourceforge.net/tracker/?group_id=81968&atid=564599
>> Discussions of bugs and features can be posted here
>> To unsubscribe, send email sympa@lists.bath.ac.uk with body "unsubscribe
>> csound"
>>
>
>
> --
> Joseph Sanger
> Blueberry Eikaiwa
> www.bbeikaiwa.com
>
>
>
> Send bugs reports to the Sourceforge bug tracker
>           https://sourceforge.net/tracker/?group_id=81968&atid=564599
> Discussions of bugs and features can be posted here
> To unsubscribe, send email sympa@lists.bath.ac.uk with body "unsubscribe
> csound"
>
>


Send bugs reports to the Sourceforge bug tracker
            https://sourceforge.net/tracker/?group_id=81968&atid=564599
Discussions of bugs and features can be posted here
To unsubscribe, send email sympa@lists.bath.ac.uk with body "unsubscribe csound"

OK, I'll do that tonight. By "normal" do you mean new, or old?

On 16/03/11 10:13, Rory Walsh wrote:
> If you get a chance try building with the normal parser again and
> we'll take it from there.
>
> On 16 March 2011 01:09, Joseph Sanger  wrote:
>> Hello, thanks for the quick reply,
>>
>> Well - I did set OPCODEDIR64, and the whole thing works fine if I set
>> "buildNewParser=0" - except I get an enormous amount of text on the screen.
>> However, I will double check later when I get home from work.
>>
>> Joe
>>
>> On 16/03/11 09:37, Rory Walsh wrote:
>>> I did see your post but didn't have time to respond. Are you sure that
>>> you have OPCODEDIR set to the correct location? check with 'echo
>>> $OPCODEDIR' from the terminal. This should have been done
>>> automatically by install.py but you should double check just in case.
>>>
>>> On top of this I don't see how your host app would crash because it
>>> can't see include files, your host app wouldn't build if the compiler
>>> couldn't find the include files.
>>>
>>> Finally, after building Csound can you run Csound with a simple csd
>>> from the command line from within your Csound build directory? If you
>>> can then we know Csound is ok and the problem is most likely something
>>> to do with OPCODEDIR.
>>>
>>> Rory.
>>>
>>>
>>>
>>> On 16 March 2011 00:10, Joseph Sanger    wrote:
>>>> Dear list,
>>>>
>>>> I already sent this same message with a different subject a few days ago
>>>> -
>>>> please ignore if you read it already. However, as I haven't yet had a
>>>> reply
>>>> I thought I'd ask again, just in case anyone can help me! Basically I'm
>>>> still in the same situation, I've tried a few other options but to no
>>>> avail.
>>>>
>>>> Joe
>>>>
>>>> On 13/03/11 21:01, Joseph Sanger wrote:
>>>>> Dear List,
>>>>>
>>>>> I'm in the process of building csound from source at the moment. I'm
>>>>> using
>>>>> 64-bit linux (Ubuntu Studio).
>>>>>
>>>>> The only option I really wanted to enable was "useDouble".
>>>>>
>>>>> I've managed to get csound to compile, with only one hitch - it was
>>>>> failing due to an error (msgfmt not found) so, after Google'ing, I
>>>>> installed
>>>>> GNU gettext. I don't know if this should go in the manual in the
>>>>> "building
>>>>> csound" section.
>>>>>
>>>>> Then it seemed to compile correctly. I couldn't find the instructions
>>>>> for
>>>>> installing, so I executed ./install.py - I hope this was the right thing
>>>>> to
>>>>> do, it doesn't say in the "building csound" manual page.
>>>>>
>>>>> I then realised I needed to compile with the option
>>>>> "dynamicCsoundLibrary=1", if I wanted to link to it with the C API, so I
>>>>> enabled that and tried again.
>>>>>
>>>>> Now it seemed to work - but csound was crashing when called from the
>>>>> host
>>>>> app, saying it couldn't load the #include files - csound seemed to
>>>>> expect
>>>>> them to be relative to the CURRENT directory, rather than the directory
>>>>> where the main input csd is stored. This worked fine with csound 5.12.
>>>>>
>>>>> To test with a simpler csd, I used a slightly modified midiin.csd (the
>>>>> manual example). It failed with the error "printks not initialised",
>>>>> again
>>>>> this worked fine with 5.12.
>>>>>
>>>>> I tried building with "buildNewParser=0", and now everything works, BUT
>>>>> I'm getting a LOT of text on the screen. I redirected the output to a
>>>>> file,
>>>>> it's 310720 lines long!!!!
>>>>>
>>>>> The first part is standard csound output. Then it starts doing this:
>>>>>
>>>>> groups: sr = 44100
>>>>> modified opcod: =.r
>>>>> treqd i, tfound c
>>>>> xincod = 0
>>>>> treqd r, tfound r
>>>>> sr  =.r 44100
>>>>> LINE 10:
>>>>> groups: ksmps = 64
>>>>> modified opcod: =.r
>>>>> treqd i, tfound c
>>>>> xincod = 0
>>>>> treqd r, tfound r
>>>>> ksmps   =.r 64
>>>>>
>>>>> and later in the file there's quite a lot of this:
>>>>>
>>>>> 135 0x1326300   (nil)   (nil)   0x1329630   0x131f020   (nil)   1   -1.0
>>>>> 136 0x1329630   (nil)   (nil)   0x132c820   0x1326300   (nil)   1   -1.0
>>>>> 137 0x132c820   (nil)   (nil)   0x132fad0   0x1329630   (nil)   1   -1.0
>>>>> 138 0x132fad0   (nil)   (nil)   0x1330e50   0x132c820   (nil)   1   -1.0
>>>>> 139 0x1330e50   (nil)   (nil)   0x1331fb0   0x132fad0   (nil)   1   -1.0
>>>>>
>>>>>
>>>>> And so on and so on...
>>>>> Once it's finished splurging to the screen (or file), it actually works
>>>>> fine.
>>>>>
>>>>> I'm assuming I need to set an option somewhere in compilation, but I
>>>>> don't
>>>>> really know which... In fact I'd really like a fairly standard set of
>>>>> options, I don't really need any of the more peculiar opcodes at the
>>>>> moment,
>>>>> just doubles and dynamic library.
>>>>>
>>>>> Thanks in advance,
>>>>>
>>>>> Joe
>>>>>
>>>>>
>>>>>
>>>> --
>>>> Joseph Sanger
>>>> Blueberry Eikaiwa
>>>> www.bbeikaiwa.com
>>>>
>>>>
>>>>
>>>> Send bugs reports to the Sourceforge bug tracker
>>>>            https://sourceforge.net/tracker/?group_id=81968&atid=564599
>>>> Discussions of bugs and features can be posted here
>>>> To unsubscribe, send email sympa@lists.bath.ac.uk with body "unsubscribe
>>>> csound"
>>>>
>>>>
>>> Send bugs reports to the Sourceforge bug tracker
>>>              https://sourceforge.net/tracker/?group_id=81968&atid=564599
>>> Discussions of bugs and features can be posted here
>>> To unsubscribe, send email sympa@lists.bath.ac.uk with body "unsubscribe
>>> csound"
>>>
>>
>> --
>> Joseph Sanger
>> Blueberry Eikaiwa
>> www.bbeikaiwa.com
>>
>>
>>
>> Send bugs reports to the Sourceforge bug tracker
>>            https://sourceforge.net/tracker/?group_id=81968&atid=564599
>> Discussions of bugs and features can be posted here
>> To unsubscribe, send email sympa@lists.bath.ac.uk with body "unsubscribe
>> csound"
>>
>>
>
> Send bugs reports to the Sourceforge bug tracker
>              https://sourceforge.net/tracker/?group_id=81968&atid=564599
> Discussions of bugs and features can be posted here
> To unsubscribe, send email sympa@lists.bath.ac.uk with body "unsubscribe csound"
>

Just try to build with default settings. If some packages are missing
apt-get install them until it builds without any errors. Then try
running Csound from the build directory. It should run fine. Setting
up your environment variables could be another story, although for the
most part install.py should work Ok. You were running it as root yeah?

On 16 March 2011 01:19, Joseph Sanger  wrote:
> OK, I'll do that tonight. By "normal" do you mean new, or old?
>
> On 16/03/11 10:13, Rory Walsh wrote:
>>
>> If you get a chance try building with the normal parser again and
>> we'll take it from there.
>>
>> On 16 March 2011 01:09, Joseph Sanger  wrote:
>>>
>>> Hello, thanks for the quick reply,
>>>
>>> Well - I did set OPCODEDIR64, and the whole thing works fine if I set
>>> "buildNewParser=0" - except I get an enormous amount of text on the
>>> screen.
>>> However, I will double check later when I get home from work.
>>>
>>> Joe
>>>
>>> On 16/03/11 09:37, Rory Walsh wrote:
>>>>
>>>> I did see your post but didn't have time to respond. Are you sure that
>>>> you have OPCODEDIR set to the correct location? check with 'echo
>>>> $OPCODEDIR' from the terminal. This should have been done
>>>> automatically by install.py but you should double check just in case.
>>>>
>>>> On top of this I don't see how your host app would crash because it
>>>> can't see include files, your host app wouldn't build if the compiler
>>>> couldn't find the include files.
>>>>
>>>> Finally, after building Csound can you run Csound with a simple csd
>>>> from the command line from within your Csound build directory? If you
>>>> can then we know Csound is ok and the problem is most likely something
>>>> to do with OPCODEDIR.
>>>>
>>>> Rory.
>>>>
>>>>
>>>>
>>>> On 16 March 2011 00:10, Joseph Sanger    wrote:
>>>>>
>>>>> Dear list,
>>>>>
>>>>> I already sent this same message with a different subject a few days
>>>>> ago
>>>>> -
>>>>> please ignore if you read it already. However, as I haven't yet had a
>>>>> reply
>>>>> I thought I'd ask again, just in case anyone can help me! Basically I'm
>>>>> still in the same situation, I've tried a few other options but to no
>>>>> avail.
>>>>>
>>>>> Joe
>>>>>
>>>>> On 13/03/11 21:01, Joseph Sanger wrote:
>>>>>>
>>>>>> Dear List,
>>>>>>
>>>>>> I'm in the process of building csound from source at the moment. I'm
>>>>>> using
>>>>>> 64-bit linux (Ubuntu Studio).
>>>>>>
>>>>>> The only option I really wanted to enable was "useDouble".
>>>>>>
>>>>>> I've managed to get csound to compile, with only one hitch - it was
>>>>>> failing due to an error (msgfmt not found) so, after Google'ing, I
>>>>>> installed
>>>>>> GNU gettext. I don't know if this should go in the manual in the
>>>>>> "building
>>>>>> csound" section.
>>>>>>
>>>>>> Then it seemed to compile correctly. I couldn't find the instructions
>>>>>> for
>>>>>> installing, so I executed ./install.py - I hope this was the right
>>>>>> thing
>>>>>> to
>>>>>> do, it doesn't say in the "building csound" manual page.
>>>>>>
>>>>>> I then realised I needed to compile with the option
>>>>>> "dynamicCsoundLibrary=1", if I wanted to link to it with the C API, so
>>>>>> I
>>>>>> enabled that and tried again.
>>>>>>
>>>>>> Now it seemed to work - but csound was crashing when called from the
>>>>>> host
>>>>>> app, saying it couldn't load the #include files - csound seemed to
>>>>>> expect
>>>>>> them to be relative to the CURRENT directory, rather than the
>>>>>> directory
>>>>>> where the main input csd is stored. This worked fine with csound 5.12.
>>>>>>
>>>>>> To test with a simpler csd, I used a slightly modified midiin.csd (the
>>>>>> manual example). It failed with the error "printks not initialised",
>>>>>> again
>>>>>> this worked fine with 5.12.
>>>>>>
>>>>>> I tried building with "buildNewParser=0", and now everything works,
>>>>>> BUT
>>>>>> I'm getting a LOT of text on the screen. I redirected the output to a
>>>>>> file,
>>>>>> it's 310720 lines long!!!!
>>>>>>
>>>>>> The first part is standard csound output. Then it starts doing this:
>>>>>>
>>>>>> groups: sr = 44100
>>>>>> modified opcod: =.r
>>>>>> treqd i, tfound c
>>>>>> xincod = 0
>>>>>> treqd r, tfound r
>>>>>> sr  =.r 44100
>>>>>> LINE 10:
>>>>>> groups: ksmps = 64
>>>>>> modified opcod: =.r
>>>>>> treqd i, tfound c
>>>>>> xincod = 0
>>>>>> treqd r, tfound r
>>>>>> ksmps   =.r 64
>>>>>>
>>>>>> and later in the file there's quite a lot of this:
>>>>>>
>>>>>> 135 0x1326300   (nil)   (nil)   0x1329630   0x131f020   (nil)   1
>>>>>> -1.0
>>>>>> 136 0x1329630   (nil)   (nil)   0x132c820   0x1326300   (nil)   1
>>>>>> -1.0
>>>>>> 137 0x132c820   (nil)   (nil)   0x132fad0   0x1329630   (nil)   1
>>>>>> -1.0
>>>>>> 138 0x132fad0   (nil)   (nil)   0x1330e50   0x132c820   (nil)   1
>>>>>> -1.0
>>>>>> 139 0x1330e50   (nil)   (nil)   0x1331fb0   0x132fad0   (nil)   1
>>>>>> -1.0
>>>>>>
>>>>>>
>>>>>> And so on and so on...
>>>>>> Once it's finished splurging to the screen (or file), it actually
>>>>>> works
>>>>>> fine.
>>>>>>
>>>>>> I'm assuming I need to set an option somewhere in compilation, but I
>>>>>> don't
>>>>>> really know which... In fact I'd really like a fairly standard set of
>>>>>> options, I don't really need any of the more peculiar opcodes at the
>>>>>> moment,
>>>>>> just doubles and dynamic library.
>>>>>>
>>>>>> Thanks in advance,
>>>>>>
>>>>>> Joe
>>>>>>
>>>>>>
>>>>>>
>>>>> --
>>>>> Joseph Sanger
>>>>> Blueberry Eikaiwa
>>>>> www.bbeikaiwa.com
>>>>>
>>>>>
>>>>>
>>>>> Send bugs reports to the Sourceforge bug tracker
>>>>>           https://sourceforge.net/tracker/?group_id=81968&atid=564599
>>>>> Discussions of bugs and features can be posted here
>>>>> To unsubscribe, send email sympa@lists.bath.ac.uk with body
>>>>> "unsubscribe
>>>>> csound"
>>>>>
>>>>>
>>>> Send bugs reports to the Sourceforge bug tracker
>>>>             https://sourceforge.net/tracker/?group_id=81968&atid=564599
>>>> Discussions of bugs and features can be posted here
>>>> To unsubscribe, send email sympa@lists.bath.ac.uk with body "unsubscribe
>>>> csound"
>>>>
>>>
>>> --
>>> Joseph Sanger
>>> Blueberry Eikaiwa
>>> www.bbeikaiwa.com
>>>
>>>
>>>
>>> Send bugs reports to the Sourceforge bug tracker
>>>           https://sourceforge.net/tracker/?group_id=81968&atid=564599
>>> Discussions of bugs and features can be posted here
>>> To unsubscribe, send email sympa@lists.bath.ac.uk with body "unsubscribe
>>> csound"
>>>
>>>
>>
>> Send bugs reports to the Sourceforge bug tracker
>>             https://sourceforge.net/tracker/?group_id=81968&atid=564599
>> Discussions of bugs and features can be posted here
>> To unsubscribe, send email sympa@lists.bath.ac.uk with body "unsubscribe
>> csound"
>>
>
>
> --
> Joseph Sanger
> Blueberry Eikaiwa
> www.bbeikaiwa.com
>
>
>
> Send bugs reports to the Sourceforge bug tracker
>           https://sourceforge.net/tracker/?group_id=81968&atid=564599
> Discussions of bugs and features can be posted here
> To unsubscribe, send email sympa@lists.bath.ac.uk with body "unsubscribe
> csound"
>
>


Send bugs reports to the Sourceforge bug tracker
            https://sourceforge.net/tracker/?group_id=81968&atid=564599
Discussions of bugs and features can be posted here
To unsubscribe, send email sympa@lists.bath.ac.uk with body "unsubscribe csound"

Thank you - I will do as you say. BTW I was indeed running install.py as 
root.

On 16/03/11 10:34, Rory Walsh wrote:
> Just try to build with default settings. If some packages are missing
> apt-get install them until it builds without any errors. Then try
> running Csound from the build directory. It should run fine. Setting
> up your environment variables could be another story, although for the
> most part install.py should work Ok. You were running it as root yeah?
>
> On 16 March 2011 01:19, Joseph Sanger  wrote:
>> OK, I'll do that tonight. By "normal" do you mean new, or old?
>>
>> On 16/03/11 10:13, Rory Walsh wrote:
>>> If you get a chance try building with the normal parser again and
>>> we'll take it from there.
>>>
>>> On 16 March 2011 01:09, Joseph Sanger    wrote:
>>>> Hello, thanks for the quick reply,
>>>>
>>>> Well - I did set OPCODEDIR64, and the whole thing works fine if I set
>>>> "buildNewParser=0" - except I get an enormous amount of text on the
>>>> screen.
>>>> However, I will double check later when I get home from work.
>>>>
>>>> Joe
>>>>
>>>> On 16/03/11 09:37, Rory Walsh wrote:
>>>>> I did see your post but didn't have time to respond. Are you sure that
>>>>> you have OPCODEDIR set to the correct location? check with 'echo
>>>>> $OPCODEDIR' from the terminal. This should have been done
>>>>> automatically by install.py but you should double check just in case.
>>>>>
>>>>> On top of this I don't see how your host app would crash because it
>>>>> can't see include files, your host app wouldn't build if the compiler
>>>>> couldn't find the include files.
>>>>>
>>>>> Finally, after building Csound can you run Csound with a simple csd
>>>>> from the command line from within your Csound build directory? If you
>>>>> can then we know Csound is ok and the problem is most likely something
>>>>> to do with OPCODEDIR.
>>>>>
>>>>> Rory.
>>>>>
>>>>>
>>>>>
>>>>> On 16 March 2011 00:10, Joseph Sanger      wrote:
>>>>>> Dear list,
>>>>>>
>>>>>> I already sent this same message with a different subject a few days
>>>>>> ago
>>>>>> -
>>>>>> please ignore if you read it already. However, as I haven't yet had a
>>>>>> reply
>>>>>> I thought I'd ask again, just in case anyone can help me! Basically I'm
>>>>>> still in the same situation, I've tried a few other options but to no
>>>>>> avail.
>>>>>>
>>>>>> Joe
>>>>>>
>>>>>> On 13/03/11 21:01, Joseph Sanger wrote:
>>>>>>> Dear List,
>>>>>>>
>>>>>>> I'm in the process of building csound from source at the moment. I'm
>>>>>>> using
>>>>>>> 64-bit linux (Ubuntu Studio).
>>>>>>>
>>>>>>> The only option I really wanted to enable was "useDouble".
>>>>>>>
>>>>>>> I've managed to get csound to compile, with only one hitch - it was
>>>>>>> failing due to an error (msgfmt not found) so, after Google'ing, I
>>>>>>> installed
>>>>>>> GNU gettext. I don't know if this should go in the manual in the
>>>>>>> "building
>>>>>>> csound" section.
>>>>>>>
>>>>>>> Then it seemed to compile correctly. I couldn't find the instructions
>>>>>>> for
>>>>>>> installing, so I executed ./install.py - I hope this was the right
>>>>>>> thing
>>>>>>> to
>>>>>>> do, it doesn't say in the "building csound" manual page.
>>>>>>>
>>>>>>> I then realised I needed to compile with the option
>>>>>>> "dynamicCsoundLibrary=1", if I wanted to link to it with the C API, so
>>>>>>> I
>>>>>>> enabled that and tried again.
>>>>>>>
>>>>>>> Now it seemed to work - but csound was crashing when called from the
>>>>>>> host
>>>>>>> app, saying it couldn't load the #include files - csound seemed to
>>>>>>> expect
>>>>>>> them to be relative to the CURRENT directory, rather than the
>>>>>>> directory
>>>>>>> where the main input csd is stored. This worked fine with csound 5.12.
>>>>>>>
>>>>>>> To test with a simpler csd, I used a slightly modified midiin.csd (the
>>>>>>> manual example). It failed with the error "printks not initialised",
>>>>>>> again
>>>>>>> this worked fine with 5.12.
>>>>>>>
>>>>>>> I tried building with "buildNewParser=0", and now everything works,
>>>>>>> BUT
>>>>>>> I'm getting a LOT of text on the screen. I redirected the output to a
>>>>>>> file,
>>>>>>> it's 310720 lines long!!!!
>>>>>>>
>>>>>>> The first part is standard csound output. Then it starts doing this:
>>>>>>>
>>>>>>> groups: sr = 44100
>>>>>>> modified opcod: =.r
>>>>>>> treqd i, tfound c
>>>>>>> xincod = 0
>>>>>>> treqd r, tfound r
>>>>>>> sr  =.r 44100
>>>>>>> LINE 10:
>>>>>>> groups: ksmps = 64
>>>>>>> modified opcod: =.r
>>>>>>> treqd i, tfound c
>>>>>>> xincod = 0
>>>>>>> treqd r, tfound r
>>>>>>> ksmps   =.r 64
>>>>>>>
>>>>>>> and later in the file there's quite a lot of this:
>>>>>>>
>>>>>>> 135 0x1326300   (nil)   (nil)   0x1329630   0x131f020   (nil)   1
>>>>>>> -1.0
>>>>>>> 136 0x1329630   (nil)   (nil)   0x132c820   0x1326300   (nil)   1
>>>>>>> -1.0
>>>>>>> 137 0x132c820   (nil)   (nil)   0x132fad0   0x1329630   (nil)   1
>>>>>>> -1.0
>>>>>>> 138 0x132fad0   (nil)   (nil)   0x1330e50   0x132c820   (nil)   1
>>>>>>> -1.0
>>>>>>> 139 0x1330e50   (nil)   (nil)   0x1331fb0   0x132fad0   (nil)   1
>>>>>>> -1.0
>>>>>>>
>>>>>>>
>>>>>>> And so on and so on...
>>>>>>> Once it's finished splurging to the screen (or file), it actually
>>>>>>> works
>>>>>>> fine.
>>>>>>>
>>>>>>> I'm assuming I need to set an option somewhere in compilation, but I
>>>>>>> don't
>>>>>>> really know which... In fact I'd really like a fairly standard set of
>>>>>>> options, I don't really need any of the more peculiar opcodes at the
>>>>>>> moment,
>>>>>>> just doubles and dynamic library.
>>>>>>>
>>>>>>> Thanks in advance,
>>>>>>>
>>>>>>> Joe
>>>>>>>
>>>>>>>
>>>>>>>
>>>>>> --
>>>>>> Joseph Sanger
>>>>>> Blueberry Eikaiwa
>>>>>> www.bbeikaiwa.com
>>>>>>
>>>>>>
>>>>>>
>>>>>> Send bugs reports to the Sourceforge bug tracker
>>>>>>            https://sourceforge.net/tracker/?group_id=81968&atid=564599
>>>>>> Discussions of bugs and features can be posted here
>>>>>> To unsubscribe, send email sympa@lists.bath.ac.uk with body
>>>>>> "unsubscribe
>>>>>> csound"
>>>>>>
>>>>>>
>>>>> Send bugs reports to the Sourceforge bug tracker
>>>>>              https://sourceforge.net/tracker/?group_id=81968&atid=564599
>>>>> Discussions of bugs and features can be posted here
>>>>> To unsubscribe, send email sympa@lists.bath.ac.uk with body "unsubscribe
>>>>> csound"
>>>>>
>>>> --
>>>> Joseph Sanger
>>>> Blueberry Eikaiwa
>>>> www.bbeikaiwa.com
>>>>
>>>>
>>>>
>>>> Send bugs reports to the Sourceforge bug tracker
>>>>            https://sourceforge.net/tracker/?group_id=81968&atid=564599
>>>> Discussions of bugs and features can be posted here
>>>> To unsubscribe, send email sympa@lists.bath.ac.uk with body "unsubscribe
>>>> csound"
>>>>
>>>>
>>> Send bugs reports to the Sourceforge bug tracker
>>>              https://sourceforge.net/tracker/?group_id=81968&atid=564599
>>> Discussions of bugs and features can be posted here
>>> To unsubscribe, send email sympa@lists.bath.ac.uk with body "unsubscribe
>>> csound"
>>>
>>
>> --
>> Joseph Sanger
>> Blueberry Eikaiwa
>> www.bbeikaiwa.com
>>
>>
>>
>> Send bugs reports to the Sourceforge bug tracker
>>            https://sourceforge.net/tracker/?group_id=81968&atid=564599
>> Discussions of bugs and features can be posted here
>> To unsubscribe, send email sympa@lists.bath.ac.uk with body "unsubscribe
>> csound"
>>
>>
>
> Send bugs reports to the Sourceforge bug tracker
>              https://sourceforge.net/tracker/?group_id=81968&atid=564599
> Discussions of bugs and features can be posted here
> To unsubscribe, send email sympa@lists.bath.ac.uk with body "unsubscribe csound"
>

Hi,

There's a really cool trick on Debian based systems to get all csound
dependencies at once, which is:

apt-get build-dep csound

This will get all the packages needed and you can build right away
even enabling all the bells and whistles.

Cheers,
Andres

On Wed, Mar 16, 2011 at 1:34 AM, Rory Walsh  wrote:
> Just try to build with default settings. If some packages are missing
> apt-get install them until it builds without any errors. Then try
> running Csound from the build directory. It should run fine. Setting
> up your environment variables could be another story, although for the
> most part install.py should work Ok. You were running it as root yeah?
>
> On 16 March 2011 01:19, Joseph Sanger  wrote:
>> OK, I'll do that tonight. By "normal" do you mean new, or old?
>>
>> On 16/03/11 10:13, Rory Walsh wrote:
>>>
>>> If you get a chance try building with the normal parser again and
>>> we'll take it from there.
>>>
>>> On 16 March 2011 01:09, Joseph Sanger  wrote:
>>>>
>>>> Hello, thanks for the quick reply,
>>>>
>>>> Well - I did set OPCODEDIR64, and the whole thing works fine if I set
>>>> "buildNewParser=0" - except I get an enormous amount of text on the
>>>> screen.
>>>> However, I will double check later when I get home from work.
>>>>
>>>> Joe
>>>>
>>>> On 16/03/11 09:37, Rory Walsh wrote:
>>>>>
>>>>> I did see your post but didn't have time to respond. Are you sure that
>>>>> you have OPCODEDIR set to the correct location? check with 'echo
>>>>> $OPCODEDIR' from the terminal. This should have been done
>>>>> automatically by install.py but you should double check just in case.
>>>>>
>>>>> On top of this I don't see how your host app would crash because it
>>>>> can't see include files, your host app wouldn't build if the compiler
>>>>> couldn't find the include files.
>>>>>
>>>>> Finally, after building Csound can you run Csound with a simple csd
>>>>> from the command line from within your Csound build directory? If you
>>>>> can then we know Csound is ok and the problem is most likely something
>>>>> to do with OPCODEDIR.
>>>>>
>>>>> Rory.
>>>>>
>>>>>
>>>>>
>>>>> On 16 March 2011 00:10, Joseph Sanger    wrote:
>>>>>>
>>>>>> Dear list,
>>>>>>
>>>>>> I already sent this same message with a different subject a few days
>>>>>> ago
>>>>>> -
>>>>>> please ignore if you read it already. However, as I haven't yet had a
>>>>>> reply
>>>>>> I thought I'd ask again, just in case anyone can help me! Basically I'm
>>>>>> still in the same situation, I've tried a few other options but to no
>>>>>> avail.
>>>>>>
>>>>>> Joe
>>>>>>
>>>>>> On 13/03/11 21:01, Joseph Sanger wrote:
>>>>>>>
>>>>>>> Dear List,
>>>>>>>
>>>>>>> I'm in the process of building csound from source at the moment. I'm
>>>>>>> using
>>>>>>> 64-bit linux (Ubuntu Studio).
>>>>>>>
>>>>>>> The only option I really wanted to enable was "useDouble".
>>>>>>>
>>>>>>> I've managed to get csound to compile, with only one hitch - it was
>>>>>>> failing due to an error (msgfmt not found) so, after Google'ing, I
>>>>>>> installed
>>>>>>> GNU gettext. I don't know if this should go in the manual in the
>>>>>>> "building
>>>>>>> csound" section.
>>>>>>>
>>>>>>> Then it seemed to compile correctly. I couldn't find the instructions
>>>>>>> for
>>>>>>> installing, so I executed ./install.py - I hope this was the right
>>>>>>> thing
>>>>>>> to
>>>>>>> do, it doesn't say in the "building csound" manual page.
>>>>>>>
>>>>>>> I then realised I needed to compile with the option
>>>>>>> "dynamicCsoundLibrary=1", if I wanted to link to it with the C API, so
>>>>>>> I
>>>>>>> enabled that and tried again.
>>>>>>>
>>>>>>> Now it seemed to work - but csound was crashing when called from the
>>>>>>> host
>>>>>>> app, saying it couldn't load the #include files - csound seemed to
>>>>>>> expect
>>>>>>> them to be relative to the CURRENT directory, rather than the
>>>>>>> directory
>>>>>>> where the main input csd is stored. This worked fine with csound 5.12.
>>>>>>>
>>>>>>> To test with a simpler csd, I used a slightly modified midiin.csd (the
>>>>>>> manual example). It failed with the error "printks not initialised",
>>>>>>> again
>>>>>>> this worked fine with 5.12.
>>>>>>>
>>>>>>> I tried building with "buildNewParser=0", and now everything works,
>>>>>>> BUT
>>>>>>> I'm getting a LOT of text on the screen. I redirected the output to a
>>>>>>> file,
>>>>>>> it's 310720 lines long!!!!
>>>>>>>
>>>>>>> The first part is standard csound output. Then it starts doing this:
>>>>>>>
>>>>>>> groups: sr = 44100
>>>>>>> modified opcod: =.r
>>>>>>> treqd i, tfound c
>>>>>>> xincod = 0
>>>>>>> treqd r, tfound r
>>>>>>> sr  =.r 44100
>>>>>>> LINE 10:
>>>>>>> groups: ksmps = 64
>>>>>>> modified opcod: =.r
>>>>>>> treqd i, tfound c
>>>>>>> xincod = 0
>>>>>>> treqd r, tfound r
>>>>>>> ksmps   =.r 64
>>>>>>>
>>>>>>> and later in the file there's quite a lot of this:
>>>>>>>
>>>>>>> 135 0x1326300   (nil)   (nil)   0x1329630   0x131f020   (nil)   1
>>>>>>> -1.0
>>>>>>> 136 0x1329630   (nil)   (nil)   0x132c820   0x1326300   (nil)   1
>>>>>>> -1.0
>>>>>>> 137 0x132c820   (nil)   (nil)   0x132fad0   0x1329630   (nil)   1
>>>>>>> -1.0
>>>>>>> 138 0x132fad0   (nil)   (nil)   0x1330e50   0x132c820   (nil)   1
>>>>>>> -1.0
>>>>>>> 139 0x1330e50   (nil)   (nil)   0x1331fb0   0x132fad0   (nil)   1
>>>>>>> -1.0
>>>>>>>
>>>>>>>
>>>>>>> And so on and so on...
>>>>>>> Once it's finished splurging to the screen (or file), it actually
>>>>>>> works
>>>>>>> fine.
>>>>>>>
>>>>>>> I'm assuming I need to set an option somewhere in compilation, but I
>>>>>>> don't
>>>>>>> really know which... In fact I'd really like a fairly standard set of
>>>>>>> options, I don't really need any of the more peculiar opcodes at the
>>>>>>> moment,
>>>>>>> just doubles and dynamic library.
>>>>>>>
>>>>>>> Thanks in advance,
>>>>>>>
>>>>>>> Joe
>>>>>>>
>>>>>>>
>>>>>>>
>>>>>> --
>>>>>> Joseph Sanger
>>>>>> Blueberry Eikaiwa
>>>>>> www.bbeikaiwa.com
>>>>>>
>>>>>>
>>>>>>
>>>>>> Send bugs reports to the Sourceforge bug tracker
>>>>>>           https://sourceforge.net/tracker/?group_id=81968&atid=564599
>>>>>> Discussions of bugs and features can be posted here
>>>>>> To unsubscribe, send email sympa@lists.bath.ac.uk with body
>>>>>> "unsubscribe
>>>>>> csound"
>>>>>>
>>>>>>
>>>>> Send bugs reports to the Sourceforge bug tracker
>>>>>             https://sourceforge.net/tracker/?group_id=81968&atid=564599
>>>>> Discussions of bugs and features can be posted here
>>>>> To unsubscribe, send email sympa@lists.bath.ac.uk with body "unsubscribe
>>>>> csound"
>>>>>
>>>>
>>>> --
>>>> Joseph Sanger
>>>> Blueberry Eikaiwa
>>>> www.bbeikaiwa.com
>>>>
>>>>
>>>>
>>>> Send bugs reports to the Sourceforge bug tracker
>>>>           https://sourceforge.net/tracker/?group_id=81968&atid=564599
>>>> Discussions of bugs and features can be posted here
>>>> To unsubscribe, send email sympa@lists.bath.ac.uk with body "unsubscribe
>>>> csound"
>>>>
>>>>
>>>
>>> Send bugs reports to the Sourceforge bug tracker
>>>             https://sourceforge.net/tracker/?group_id=81968&atid=564599
>>> Discussions of bugs and features can be posted here
>>> To unsubscribe, send email sympa@lists.bath.ac.uk with body "unsubscribe
>>> csound"
>>>
>>
>>
>> --
>> Joseph Sanger
>> Blueberry Eikaiwa
>> www.bbeikaiwa.com
>>
>>
>>
>> Send bugs reports to the Sourceforge bug tracker
>>           https://sourceforge.net/tracker/?group_id=81968&atid=564599
>> Discussions of bugs and features can be posted here
>> To unsubscribe, send email sympa@lists.bath.ac.uk with body "unsubscribe
>> csound"
>>
>>
>
>
> Send bugs reports to the Sourceforge bug tracker
>            https://sourceforge.net/tracker/?group_id=81968&atid=564599
> Discussions of bugs and features can be posted here
> To unsubscribe, send email sympa@lists.bath.ac.uk with body "unsubscribe csound"
>
>


Send bugs reports to the Sourceforge bug tracker
            https://sourceforge.net/tracker/?group_id=81968&atid=564599
Discussions of bugs and features can be posted here
To unsubscribe, send email sympa@lists.bath.ac.uk with body "unsubscribe csound"

Thank you - that's very useful. I'll try it later.

On 16/03/11 16:38, Andres Cabrera wrote:
> Hi,
>
> There's a really cool trick on Debian based systems to get all csound
> dependencies at once, which is:
>
> apt-get build-dep csound
>
> This will get all the packages needed and you can build right away
> even enabling all the bells and whistles.
>
> Cheers,
> Andres
>
> On Wed, Mar 16, 2011 at 1:34 AM, Rory Walsh  wrote:
>> Just try to build with default settings. If some packages are missing
>> apt-get install them until it builds without any errors. Then try
>> running Csound from the build directory. It should run fine. Setting
>> up your environment variables could be another story, although for the
>> most part install.py should work Ok. You were running it as root yeah?
>>
>> On 16 March 2011 01:19, Joseph Sanger  wrote:
>>> OK, I'll do that tonight. By "normal" do you mean new, or old?
>>>
>>> On 16/03/11 10:13, Rory Walsh wrote:
>>>> If you get a chance try building with the normal parser again and
>>>> we'll take it from there.
>>>>
>>>> On 16 March 2011 01:09, Joseph Sanger    wrote:
>>>>> Hello, thanks for the quick reply,
>>>>>
>>>>> Well - I did set OPCODEDIR64, and the whole thing works fine if I set
>>>>> "buildNewParser=0" - except I get an enormous amount of text on the
>>>>> screen.
>>>>> However, I will double check later when I get home from work.
>>>>>
>>>>> Joe
>>>>>
>>>>> On 16/03/11 09:37, Rory Walsh wrote:
>>>>>> I did see your post but didn't have time to respond. Are you sure that
>>>>>> you have OPCODEDIR set to the correct location? check with 'echo
>>>>>> $OPCODEDIR' from the terminal. This should have been done
>>>>>> automatically by install.py but you should double check just in case.
>>>>>>
>>>>>> On top of this I don't see how your host app would crash because it
>>>>>> can't see include files, your host app wouldn't build if the compiler
>>>>>> couldn't find the include files.
>>>>>>
>>>>>> Finally, after building Csound can you run Csound with a simple csd
>>>>>> from the command line from within your Csound build directory? If you
>>>>>> can then we know Csound is ok and the problem is most likely something
>>>>>> to do with OPCODEDIR.
>>>>>>
>>>>>> Rory.
>>>>>>
>>>>>>
>>>>>>
>>>>>> On 16 March 2011 00:10, Joseph Sanger      wrote:
>>>>>>> Dear list,
>>>>>>>
>>>>>>> I already sent this same message with a different subject a few days
>>>>>>> ago
>>>>>>> -
>>>>>>> please ignore if you read it already. However, as I haven't yet had a
>>>>>>> reply
>>>>>>> I thought I'd ask again, just in case anyone can help me! Basically I'm
>>>>>>> still in the same situation, I've tried a few other options but to no
>>>>>>> avail.
>>>>>>>
>>>>>>> Joe
>>>>>>>
>>>>>>> On 13/03/11 21:01, Joseph Sanger wrote:
>>>>>>>> Dear List,
>>>>>>>>
>>>>>>>> I'm in the process of building csound from source at the moment. I'm
>>>>>>>> using
>>>>>>>> 64-bit linux (Ubuntu Studio).
>>>>>>>>
>>>>>>>> The only option I really wanted to enable was "useDouble".
>>>>>>>>
>>>>>>>> I've managed to get csound to compile, with only one hitch - it was
>>>>>>>> failing due to an error (msgfmt not found) so, after Google'ing, I
>>>>>>>> installed
>>>>>>>> GNU gettext. I don't know if this should go in the manual in the
>>>>>>>> "building
>>>>>>>> csound" section.
>>>>>>>>
>>>>>>>> Then it seemed to compile correctly. I couldn't find the instructions
>>>>>>>> for
>>>>>>>> installing, so I executed ./install.py - I hope this was the right
>>>>>>>> thing
>>>>>>>> to
>>>>>>>> do, it doesn't say in the "building csound" manual page.
>>>>>>>>
>>>>>>>> I then realised I needed to compile with the option
>>>>>>>> "dynamicCsoundLibrary=1", if I wanted to link to it with the C API, so
>>>>>>>> I
>>>>>>>> enabled that and tried again.
>>>>>>>>
>>>>>>>> Now it seemed to work - but csound was crashing when called from the
>>>>>>>> host
>>>>>>>> app, saying it couldn't load the #include files - csound seemed to
>>>>>>>> expect
>>>>>>>> them to be relative to the CURRENT directory, rather than the
>>>>>>>> directory
>>>>>>>> where the main input csd is stored. This worked fine with csound 5.12.
>>>>>>>>
>>>>>>>> To test with a simpler csd, I used a slightly modified midiin.csd (the
>>>>>>>> manual example). It failed with the error "printks not initialised",
>>>>>>>> again
>>>>>>>> this worked fine with 5.12.
>>>>>>>>
>>>>>>>> I tried building with "buildNewParser=0", and now everything works,
>>>>>>>> BUT
>>>>>>>> I'm getting a LOT of text on the screen. I redirected the output to a
>>>>>>>> file,
>>>>>>>> it's 310720 lines long!!!!
>>>>>>>>
>>>>>>>> The first part is standard csound output. Then it starts doing this:
>>>>>>>>
>>>>>>>> groups: sr = 44100
>>>>>>>> modified opcod: =.r
>>>>>>>> treqd i, tfound c
>>>>>>>> xincod = 0
>>>>>>>> treqd r, tfound r
>>>>>>>> sr  =.r 44100
>>>>>>>> LINE 10:
>>>>>>>> groups: ksmps = 64
>>>>>>>> modified opcod: =.r
>>>>>>>> treqd i, tfound c
>>>>>>>> xincod = 0
>>>>>>>> treqd r, tfound r
>>>>>>>> ksmps   =.r 64
>>>>>>>>
>>>>>>>> and later in the file there's quite a lot of this:
>>>>>>>>
>>>>>>>> 135 0x1326300   (nil)   (nil)   0x1329630   0x131f020   (nil)   1
>>>>>>>> -1.0
>>>>>>>> 136 0x1329630   (nil)   (nil)   0x132c820   0x1326300   (nil)   1
>>>>>>>> -1.0
>>>>>>>> 137 0x132c820   (nil)   (nil)   0x132fad0   0x1329630   (nil)   1
>>>>>>>> -1.0
>>>>>>>> 138 0x132fad0   (nil)   (nil)   0x1330e50   0x132c820   (nil)   1
>>>>>>>> -1.0
>>>>>>>> 139 0x1330e50   (nil)   (nil)   0x1331fb0   0x132fad0   (nil)   1
>>>>>>>> -1.0
>>>>>>>>
>>>>>>>>
>>>>>>>> And so on and so on...
>>>>>>>> Once it's finished splurging to the screen (or file), it actually
>>>>>>>> works
>>>>>>>> fine.
>>>>>>>>
>>>>>>>> I'm assuming I need to set an option somewhere in compilation, but I
>>>>>>>> don't
>>>>>>>> really know which... In fact I'd really like a fairly standard set of
>>>>>>>> options, I don't really need any of the more peculiar opcodes at the
>>>>>>>> moment,
>>>>>>>> just doubles and dynamic library.
>>>>>>>>
>>>>>>>> Thanks in advance,
>>>>>>>>
>>>>>>>> Joe
>>>>>>>>
>>>>>>>>
>>>>>>>>
>>>>>>> --
>>>>>>> Joseph Sanger
>>>>>>> Blueberry Eikaiwa
>>>>>>> www.bbeikaiwa.com
>>>>>>>
>>>>>>>
>>>>>>>
>>>>>>> Send bugs reports to the Sourceforge bug tracker
>>>>>>>            https://sourceforge.net/tracker/?group_id=81968&atid=564599
>>>>>>> Discussions of bugs and features can be posted here
>>>>>>> To unsubscribe, send email sympa@lists.bath.ac.uk with body
>>>>>>> "unsubscribe
>>>>>>> csound"
>>>>>>>
>>>>>>>
>>>>>> Send bugs reports to the Sourceforge bug tracker
>>>>>>              https://sourceforge.net/tracker/?group_id=81968&atid=564599
>>>>>> Discussions of bugs and features can be posted here
>>>>>> To unsubscribe, send email sympa@lists.bath.ac.uk with body "unsubscribe
>>>>>> csound"
>>>>>>
>>>>> --
>>>>> Joseph Sanger
>>>>> Blueberry Eikaiwa
>>>>> www.bbeikaiwa.com
>>>>>
>>>>>
>>>>>
>>>>> Send bugs reports to the Sourceforge bug tracker
>>>>>            https://sourceforge.net/tracker/?group_id=81968&atid=564599
>>>>> Discussions of bugs and features can be posted here
>>>>> To unsubscribe, send email sympa@lists.bath.ac.uk with body "unsubscribe
>>>>> csound"
>>>>>
>>>>>
>>>> Send bugs reports to the Sourceforge bug tracker
>>>>              https://sourceforge.net/tracker/?group_id=81968&atid=564599
>>>> Discussions of bugs and features can be posted here
>>>> To unsubscribe, send email sympa@lists.bath.ac.uk with body "unsubscribe
>>>> csound"
>>>>
>>>
>>> --
>>> Joseph Sanger
>>> Blueberry Eikaiwa
>>> www.bbeikaiwa.com
>>>
>>>
>>>
>>> Send bugs reports to the Sourceforge bug tracker
>>>            https://sourceforge.net/tracker/?group_id=81968&atid=564599
>>> Discussions of bugs and features can be posted here
>>> To unsubscribe, send email sympa@lists.bath.ac.uk with body "unsubscribe
>>> csound"
>>>
>>>
>>
>> Send bugs reports to the Sourceforge bug tracker
>>             https://sourceforge.net/tracker/?group_id=81968&atid=564599
>> Discussions of bugs and features can be posted here
>> To unsubscribe, send email sympa@lists.bath.ac.uk with body "unsubscribe csound"
>>
>>
>
> Send bugs reports to the Sourceforge bug tracker
>              https://sourceforge.net/tracker/?group_id=81968&atid=564599
> Discussions of bugs and features can be posted here
> To unsubscribe, send email sympa@lists.bath.ac.uk with body "unsubscribe csound"
>