I'm running 64-bit, and it now appears to work for me. At least, it loads without complaining. I uninstalled and deleted the build directory and re-un-tarred. On building again, I ran 'ldd _csnd.so' in the build directory and I saw 'libcsound.so.5.1 -> not found'. After sudo scons install, ldd /path/to/_csnd.so returns libcsound.so.5.1 and its correct path, and now python appears to load it. I think maybe one of the files wasn't clearing from the build directory; I initially didn't select the interface option, so perhaps it had something to do with one file being left over from the previous build and the other being built fresh? -Chuckk On Sun, May 11, 2008 at 8:21 PM, victor wrote: > I don't have any problems building Csound in my Fedora systems. > I never install anything, by the way, just point the relevant > environment vars to my build dir. I suppose it's the installation > script that needs to be looked at. > > But I have heard of build issues on 64bit OSs, however since > I don't have such boxes, I can't test things. > > Victor > > > > ---- Original Message ----- From: "Dave Phillips" > > To: > Sent: Sunday, May 11, 2008 4:07 PM > Subject: [Csnd] Re: Python API questions time > > > > > > > victor wrote: > > > > > Well, there you go, that's your problem... > > > > > > > > > > It isn't. > > > > > > > > On Sun, May 11, 2008 at 1:52 PM, victor > wrote: > > > > > > > > > See if _csnd.so is linked to libcsnd.so.5.1, use ldd > > > > > > > > > > ldd _csnd.so > > > > > > > > > > > > > > Confusion rules here. My build of Csound 5.08 generated a file named > _csnd.so, it is not linked to anything. The file libcsnd.so.5.1 is found in > > OPCODEDIR64, and it too is not linked to any other object (other than > itself). > > > > dlphilp@64studio:~/src/csound5.08$ ls -l *csnd.s* > > -rwxr-xr-x 1 dlphilp dlphilp 2368739 2008-03-24 17:11 _csnd.so > > lrwxrwxrwx 1 dlphilp dlphilp 14 2008-03-24 17:11 libcsnd.so -> > libcsnd.so.5.1 > > -rwxr-xr-x 1 dlphilp dlphilp 1108221 2008-03-24 13:00 libcsnd.so.5.1 > > > > dlphilp@64studio:/usr/local/lib/csound/plugins64$ ls -l libcsnd* > > -rwxr-xr-x 1 root staff 292624 2008-03-24 17:14 libcsnd.so > > lrwxrwxrwx 1 root staff 10 2008-05-08 15:57 libcsnd.so.5.1 -> > libcsnd.so > > > > dlphilp@64studio:/usr/lib/python2.5/site-packages$ ls -l *snd* > > -rw-r--r-- 1 root root 129045 2008-03-24 17:10 csnd.py > > > > dlphilp@64studio:/usr/local/lib$ ls -l *csnd* > > lrwxrwxrwx 1 root staff 14 2008-05-08 15:53 libcsnd.so -> > libcsnd.so.5.1 > > -rwxr-xr-x 1 root staff 292624 2008-05-08 15:53 libcsnd.so.5.1 > > > > Items dated 2008-05-08 were added/linked after reading the advice from > this list. > > > > > > I'm still waiting for answers to these questions: > > > > Exactly what Csound files ought to be in the Python site-packages > directory ? > > > > Does ImproSculpt support a double-precision build of Csound ? (Sorry, > Oeyvind, I still need to verify that trapped.py and the other examples will > work too). > > > > No fear, I'm not whinging, I know that everyone is busy. But I think that > some problems would be resolved if we knew just what's supposed to go where. > Btw, perhaps in future the compile process could add a build directory and > store its compiled files there ? The current situation creates a pretty > messy top directory. Csound is currently the only program I build that still > does that. I suppose it's not a big deal, but it would certainly reduce the > clutter. > > > > Best, > > > > dp > > > > > > > > Send bugs reports to this list. > > To unsubscribe, send email sympa@lists.bath.ac.uk with body "unsubscribe > csound" > > > > > > Send bugs reports to this list. > To unsubscribe, send email sympa@lists.bath.ac.uk with body "unsubscribe > csound" > -- http://www.badmuthahubbard.com