Greetings,

I've set up a new 64-bit Arch Linux system on which I compiled Csound 
5.13.0 yesterday with no troubles during the build. However, the 
install.py file does not like Python 2.7. Apparently all print 
statements need updated to a new syntax, but even after making the 
changes the installer failed at installing the check for an older 
version of Csound and at installing the uninstall-csound utility. Also, 
the script would not create the required directories, I had to manually 
create those directories.

Has anyone else used install.py with Python 2.7, and if so, how did you 
get it working ? Uninstalling Csound manually is a royal pain, I'd like 
to use the script instead.

I also have a problem with libcsound64 when working with AVSynthesis but 
I need to do more research before making a report.

TIA,

dp


------------------------------------------------------------------------------
BlackBerry® DevCon Americas, Oct. 18-20, San Francisco, CA
http://p.sf.net/sfu/rim-devcon-copy2
_______________________________________________
Csound-devel mailing list
Csound-devel@lists.sourceforge.net

Did you try running with python2.6, or is this command not available?

Victor
On 18 Sep 2011, at 14:43, Dave Phillips wrote:

> Greetings,
>
> I've set up a new 64-bit Arch Linux system on which I compiled Csound
> 5.13.0 yesterday with no troubles during the build. However, the
> install.py file does not like Python 2.7. Apparently all print
> statements need updated to a new syntax, but even after making the
> changes the installer failed at installing the check for an older
> version of Csound and at installing the uninstall-csound utility.  
> Also,
> the script would not create the required directories, I had to  
> manually
> create those directories.
>
> Has anyone else used install.py with Python 2.7, and if so, how did  
> you
> get it working ? Uninstalling Csound manually is a royal pain, I'd  
> like
> to use the script instead.
>
> I also have a problem with libcsound64 when working with AVSynthesis  
> but
> I need to do more research before making a report.
>
> TIA,
>
> dp
>
>
> ------------------------------------------------------------------------------
> BlackBerry® DevCon Americas, Oct. 18-20, San Francisco, CA
> http://p.sf.net/sfu/rim-devcon-copy2
> _______________________________________________
> Csound-devel mailing list
> Csound-devel@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/csound-devel

Dr Victor Lazzarini
Senior Lecturer
Dept. of Music
NUI Maynooth Ireland
tel.: +353 1 708 3545
Victor dot Lazzarini AT nuim dot ie




------------------------------------------------------------------------------
BlackBerry® DevCon Americas, Oct. 18-20, San Francisco, CA
http://p.sf.net/sfu/rim-devcon-copy2
_______________________________________________
Csound-devel mailing list
Csound-devel@lists.sourceforge.net

Victor Lazzarini wrote:
> Did you try running with python2.6, or is this command not available?
>
>   

Hi Victor,

It's probably available, but I wanted to run with the default system's 
components. Since Arch installs 2.7 by default I wondered if/how 
install.py could accommodate that version. I'll install 2.6 and give it 
another run.

In the meanwhile I resolved the issue with libscound64 and AVS. It was 
an old issue, resolved with buildNewParser=0.

Best,

dp


------------------------------------------------------------------------------
BlackBerry® DevCon Americas, Oct. 18-20, San Francisco, CA
http://p.sf.net/sfu/rim-devcon-copy2
_______________________________________________
Csound-devel mailing list
Csound-devel@lists.sourceforge.net

If you can provide some error messages we can probably try to ship a  
install.py for 2.7.

Victor


On 18 Sep 2011, at 16:57, Dave Phillips wrote:

> Victor Lazzarini wrote:
>> Did you try running with python2.6, or is this command not available?
>>
>>
>
> Hi Victor,
>
> It's probably available, but I wanted to run with the default system's
> components. Since Arch installs 2.7 by default I wondered if/how
> install.py could accommodate that version. I'll install 2.6 and give  
> it
> another run.
>
> In the meanwhile I resolved the issue with libscound64 and AVS. It was
> an old issue, resolved with buildNewParser=0.
>
> Best,
>
> dp
>
>
> ------------------------------------------------------------------------------
> BlackBerry® DevCon Americas, Oct. 18-20, San Francisco, CA
> http://p.sf.net/sfu/rim-devcon-copy2
> _______________________________________________
> Csound-devel mailing list
> Csound-devel@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/csound-devel

Dr Victor Lazzarini
Senior Lecturer
Dept. of Music
NUI Maynooth Ireland
tel.: +353 1 708 3545
Victor dot Lazzarini AT nuim dot ie




------------------------------------------------------------------------------
BlackBerry® DevCon Americas, Oct. 18-20, San Francisco, CA
http://p.sf.net/sfu/rim-devcon-copy2
_______________________________________________
Csound-devel mailing list
Csound-devel@lists.sourceforge.net

> In the meanwhile I resolved the issue with libscound64 and AVS. It was
> an old issue, resolved with buildNewParser=0.
>

Any more details?  I am not aware of any problems with the new parser at
present -- or is this old sources?

==John ff


------------------------------------------------------------------------------
BlackBerry® DevCon Americas, Oct. 18-20, San Francisco, CA
http://p.sf.net/sfu/rim-devcon-copy2
_______________________________________________
Csound-devel mailing list
Csound-devel@lists.sourceforge.net

I've updated install.py with the new syntax in GIT, but I can't test  
it here now. Can you?

Victor
On 18 Sep 2011, at 16:57, Dave Phillips wrote:

> Victor Lazzarini wrote:
>> Did you try running with python2.6, or is this command not available?
>>
>>
>
> Hi Victor,
>
> It's probably available, but I wanted to run with the default system's
> components. Since Arch installs 2.7 by default I wondered if/how
> install.py could accommodate that version. I'll install 2.6 and give  
> it
> another run.
>
> In the meanwhile I resolved the issue with libscound64 and AVS. It was
> an old issue, resolved with buildNewParser=0.
>
> Best,
>
> dp
>
>
> ------------------------------------------------------------------------------
> BlackBerry® DevCon Americas, Oct. 18-20, San Francisco, CA
> http://p.sf.net/sfu/rim-devcon-copy2
> _______________________________________________
> Csound-devel mailing list
> Csound-devel@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/csound-devel

Dr Victor Lazzarini
Senior Lecturer
Dept. of Music
NUI Maynooth Ireland
tel.: +353 1 708 3545
Victor dot Lazzarini AT nuim dot ie




------------------------------------------------------------------------------
BlackBerry® DevCon Americas, Oct. 18-20, San Francisco, CA
http://p.sf.net/sfu/rim-devcon-copy2
_______________________________________________
Csound-devel mailing list
Csound-devel@lists.sourceforge.net

Victor Lazzarini wrote:
> I've updated install.py with the new syntax in GIT, but I can't test  
> it here now. Can you?
>
>   

Hi Victor,

Thanks, I'll get it and test it in a few minutes. I'm switching systems 
on the same machine, it'll be a while before I report.

Best,

dp


------------------------------------------------------------------------------
BlackBerry® DevCon Americas, Oct. 18-20, San Francisco, CA
http://p.sf.net/sfu/rim-devcon-copy2
_______________________________________________
Csound-devel mailing list
Csound-devel@lists.sourceforge.net

jpff@cs.bath.ac.uk wrote:
>> In the meanwhile I resolved the issue with libscound64 and AVS. It was
>> an old issue, resolved with buildNewParser=0.
>>
>>     
>
> Any more details?  I am not aware of any problems with the new parser at
> present -- or is this old sources?
>
>   

Hi John,

Sources are from the latest SF tarball. I reported the same problem in 
April of this year. Unfortunately there's not much to report beyond the 
Java error logs produced by AVSynthesis. I've attached one, hopefully 
it'll make it through the filters.

Best,

dp