asound is ALSA, you will definitely need that. etags you can install or not
as you please - it's not required for Csound to work.

Original Message:
-----------------
From:  iainduncan@telus.net
Date: Sun,  9 May 2004 17:20:58 -0700
To: csound-dev@eartha.mills.edu
Subject: [CSOUND-DEV:4636] Updated Csound 5 compile errors


Ok, to resummarize, all necessary dependencies have been installed or
emerged.
Now custom.py knows where python.h is. I don't think that changed my errors
any
though:

With all options on in SConstruct as per default:

./libcsound.a(main.o)(.text+0x503): In function `csoundCompile':
Top/main.c:423: warning: the use of `tmpnam' is dangerous, better use
`mkstemp'
/usr/lib/gcc-lib/i386-pc-linux-gnu/3.3.2/../../../crt1.o(.text+0x18): In
function `_start':
: undefined reference to `main'
collect2: ld returned 1 exit status
scons: *** [_CsoundVST.so] Error 1
scons: building terminated because of errors.


With CsoundVST turned off:

sh: line 1: etags: command not found
scons: *** [TAGS] Error 127
scons: building terminated because of errors.

With tags turned off:
/usr/lib/gcc-lib/i386-pc-linux-gnu/3.3.2/../../../../i386-pc-linux-gnu/bin/l
d:
cannot find -lasound
collect2: ld returned 1 exit status
scons: *** [cscore] Error 1
scons: building terminated because of errors.


Thanks
Iain



--------------------------------------------------------------------
mail2web - Check your email from the web at
http://mail2web.com/ .

I have alsa installed and working, this I know for sure (I can use aplay, and
other alsa apps). What I don't know is how to make the install work or find it
or whatever. Keep in mind I have next to no idea on how to run these things on
linux. I'd love to get it working to test it, but I guess I need more detail
than is currently in the guide. Any suggestion on what I need to do to make it go? 

Thanks 
Iain

> asound is ALSA, you will definitely need that. etags you can install or not
> as you please - it's not required for Csound to work.
> 
> Original Message:
> -----------------
> From:  iainduncan@telus.net
> Date: Sun,  9 May 2004 17:20:58 -0700
> To: csound-dev@eartha.mills.edu
> Subject: [CSOUND-DEV:4636] Updated Csound 5 compile errors
> 
> 
> Ok, to resummarize, all necessary dependencies have been installed or
> emerged.
> Now custom.py knows where python.h is. I don't think that changed my errors
> any
> though:
> 
> With all options on in SConstruct as per default:
> 
> ./libcsound.a(main.o)(.text+0x503): In function `csoundCompile':
> Top/main.c:423: warning: the use of `tmpnam' is dangerous, better use
> `mkstemp'
> /usr/lib/gcc-lib/i386-pc-linux-gnu/3.3.2/../../../crt1.o(.text+0x18): In
> function `_start':
> : undefined reference to `main'
> collect2: ld returned 1 exit status
> scons: *** [_CsoundVST.so] Error 1
> scons: building terminated because of errors.
> 
> 
> With CsoundVST turned off:
> 
> sh: line 1: etags: command not found
> scons: *** [TAGS] Error 127
> scons: building terminated because of errors.
> 
> With tags turned off:
> /usr/lib/gcc-lib/i386-pc-linux-gnu/3.3.2/../../../../i386-pc-linux-gnu/bin/l
> d:
> cannot find -lasound
> collect2: ld returned 1 exit status
> scons: *** [cscore] Error 1
> scons: building terminated because of errors.
> 
> 
> Thanks
> Iain
> 
> 
> 
> --------------------------------------------------------------------
> mail2web - Check your email from the web at
> http://mail2web.com/ .
> 
> 

Hi,
I'm pretty sure Michael and others have gotten this far, but just wanted to 
check.
I built portaudio with directx by changing the following:
Added in mmsystem.h:
#define _LPCWAVEFORMATEX_DEFINED
in line 1014

And commented out line 1899 in dsound.h:
//typedef struct IDirectSoundFullDuplex *LPDIRECTSOUNDFULLDUPLEX;

This way portaudio builds successfully with directx and all the pa_tests run 
fine with minimum latency of about 40ms.
but... csound5 behaves strangely (with trappedrt.csd). I get a crash after 
calculating the ftables (when audio should start), but csound goes on and on 
compiling, but not producing any sound, and very fast (like it was doing 
offline instead of rt processing).
I've tried different buffer sizes, but that doesn't seem to be the problem.

Any ideas?
Cheers,
Andres

iainduncan@telus.net wrote:

>I have alsa installed and working, this I know for sure (I can use aplay, and
>other alsa apps). What I don't know is how to make the install work or find it
>or whatever. Keep in mind I have next to no idea on how to run these things on
>linux. I'd love to get it working to test it, but I guess I need more detail
>than is currently in the guide. Any suggestion on what I need to do to make it go? 
>  
>
FWIW, i downloaded the portaudio v.19  snapshot from a couple days ago 
and csound5 and tried to compile, and i also encountered the same error 
with ld not find libasound, which is weird because i know the library is 
installed and i'm 99% sure that ld.so.conf includes the path where it's 
located.  this is on redhat 9, with gcc 3.2.2 and alsa 0.98 (? -- 
definitely pre-1.0).  unfortunately my knowledge of c is pretty 
rudimentary and my experience with gcc doesn't extend much beyond 'gcc 
-o helloworld helloworld.c', so my ability to troubleshoot these things 
on their own isn't all that great.

glyn

Hi guys,

Could you do a "locate libasound" and report what you get back?

Thanks,
steven


On Sun, 2004-05-09 at 20:36, glyn wrote:
> iainduncan@telus.net wrote:
> 
> >I have alsa installed and working, this I know for sure (I can use aplay, and
> >other alsa apps). What I don't know is how to make the install work or find it
> >or whatever. Keep in mind I have next to no idea on how to run these things on
> >linux. I'd love to get it working to test it, but I guess I need more detail
> >than is currently in the guide. Any suggestion on what I need to do to make it go? 
> >  
> >
> FWIW, i downloaded the portaudio v.19  snapshot from a couple days ago 
> and csound5 and tried to compile, and i also encountered the same error 
> with ld not find libasound, which is weird because i know the library is 
> installed and i'm 99% sure that ld.so.conf includes the path where it's 
> located.  this is on redhat 9, with gcc 3.2.2 and alsa 0.98 (? -- 
> definitely pre-1.0).  unfortunately my knowledge of c is pretty 
> rudimentary and my experience with gcc doesn't extend much beyond 'gcc 
> -o helloworld helloworld.c', so my ability to troubleshoot these things 
> on their own isn't all that great.
> 
> glyn
> 
>