ccrtp-devel
[Top][All Lists]
Advanced

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

[Ccrtp-devel] Fixes for compiling ccrtp 1.5.1 on Mac OS X


From: Nicholas J Humfrey
Subject: [Ccrtp-devel] Fixes for compiling ccrtp 1.5.1 on Mac OS X
Date: Thu, 13 Sep 2007 17:34:13 +0100

Hello,

I have just been compiling and testing ccrtp on Mac OS X. Only one problem really, three files include <malloc.h>, which does not exist on Mac OS X.

./src/ccrtp/crypto/gcrypt/gcryptAesSrtp.cxx:#include <malloc.h>
./src/ccrtp/crypto/gcrypt/InitializeGcrypt.cxx:#include <malloc.h>
./src/ccrtp/crypto/openssl/AesSrtp.cxx:#include <malloc.h>

Changing them to #include <stdlib.h> fixes the problem.

After that everything seems to compile/run fine :)


nick.



[hwickabab:/tmp/ccrtp-1.5.1/demo] njh% ./rtphello
This is rtphello, a very simple test program for ccRTP.
Strike [Enter] when you are fed up with it.
Hello, Tx (address@hidden ...
Rx (64babac0): 481d62cf): localhost is waiting for salutes in port 8362... localhost is going to salute perself through Rx (64babac0): The queue is active.
127.0.0.1...
Tx (481d62cf): Transmitting salutes to port 8362...
Tx (481d62cf): The queue is active.
Tx (481d62cf): sending salute no 0, at 17:16:24...
Rx (64babac0): [receiving at 17:16:24]: Hello, brave gnu world (#0)!
Tx (481d62cf): sending salute no 1, at 17:16:25...
Rx (64babac0): [receiving at 17:16:25]: Hello, brave gnu world (#1)!
Tx (481d62cf): sending salute no 2, at 17:16:26...
Rx (64babac0): [receiving at 17:16:26]: Hello, brave gnu world (#2)!
Tx (481d62cf): sending salute no 3, at 17:16:27...
Rx (64babac0): [receiving at 17:16:27]: Hello, brave gnu world (#3)!
Tx (481d62cf): sending salute no 4, at 17:16:28...
Rx (64babac0): [receiving at 17:16:28]: Hello, brave gnu world (#4)!
Tx (481d62cf): sending salute no 5, at 17:16:29...
Rx (64babac0): [receiving at 17:16:29]: Hello, brave gnu world (#5)!
cTx (481d62cf): sending salute no 6, at 17:16:30...
Rx (64babac0): [receiving at 17:16:30]: Hello, brave gnu world (#6)!






reply via email to

[Prev in Thread] Current Thread [Next in Thread]