Linux, Csound 5.12 from source:
I remember long ago being warned of getting errors if I built and installed
Csound without removing all traces of a previous version. I take it this is
still the case, because I'm getting the old "glibc detected" error and
seeing a traceback that mentions the Csound5.10.1 folder.
I seem to recall once finding a way to automatically uninstall, but I don't
see it now. Is there such a script somewhere, or do I still need to manually
delete all Csound files on my system?
I've read the wisdom of not installing; maybe that's what I should do, use a
full path?

-Chuckk

Either that, or use package management. Installing into PATH from
source is definitely not The Way To Go®.

On Mon, Jun 7, 2010 at 16:48, Chuckk Hubbard  wrote:
> Linux, Csound 5.12 from source:
> I remember long ago being warned of getting errors if I built and installed
> Csound without removing all traces of a previous version. I take it this is
> still the case, because I'm getting the old "glibc detected" error and
> seeing a traceback that mentions the Csound5.10.1 folder.
> I seem to recall once finding a way to automatically uninstall, but I don't
> see it now. Is there such a script somewhere, or do I still need to manually
> delete all Csound files on my system?
> I've read the wisdom of not installing; maybe that's what I should do, use a
> full path?
>
> -Chuckk
>
> --
> http://www.badmuthahubbard.com
>



-- 

Saludos,
Felipe Sateler


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"

Stuff gone missing in newer releases will never go missing in your
installed copy, leading to inconsistencies that could interact badly
(eg, leaving a broken opcode lib installed). Also, you can never be
sure you have cleanly uninstalled something.

On Mon, Jun 7, 2010 at 20:14, Chuckk Hubbard  wrote:
> Not that I don't trust you, but for my understanding, what could go wrong
> installing into PATH from source? I believe I've done it with other projects
> as well. Not /usr/bin, but /usr/local.
>
> I solved part of my problem: I had "export
> OPCODEDIR=/home/chuckk/Csound5.10.1" in .bashrc!
>
> -Chuckk
>
> On Tue, Jun 8, 2010 at 2:51 AM, Felipe Sateler  wrote:
>>
>> Either that, or use package management. Installing into PATH from
>> source is definitely not The Way To Go®.
>>
>> On Mon, Jun 7, 2010 at 16:48, Chuckk Hubbard 
>> wrote:
>> > Linux, Csound 5.12 from source:
>> > I remember long ago being warned of getting errors if I built and
>> > installed
>> > Csound without removing all traces of a previous version. I take it this
>> > is
>> > still the case, because I'm getting the old "glibc detected" error and
>> > seeing a traceback that mentions the Csound5.10.1 folder.
>> > I seem to recall once finding a way to automatically uninstall, but I
>> > don't
>> > see it now. Is there such a script somewhere, or do I still need to
>> > manually
>> > delete all Csound files on my system?
>> > I've read the wisdom of not installing; maybe that's what I should do,
>> > use a
>> > full path?
>> >
>> > -Chuckk
>> >
>> > --
>> > http://www.badmuthahubbard.com
>> >
>>
>>
>>
>> --
>>
>> Saludos,
>> Felipe Sateler
>>
>>
>> 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"
>>
>
>
>
> --
> http://www.badmuthahubbard.com
>



-- 

Saludos,
Felipe Sateler


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"