Is there any reason why not to unbundle libsrtp? I found this because portage reports: * QA Notice: Package has poor programming practices which may compile * fine but exhibit random runtime failures. * third_party/libsrtp/src/crypto/include/datatypes.h:418:4: warning: implicit declaration of function ‘ntohl’ * third_party/libsrtp/src/srtp/ekt.c:238:3: warning: implicit declaration of function ‘htons’ * third_party/libsrtp/src/crypto/include/datatypes.h:418:4: warning: implicit declaration of function ‘ntohl’ * third_party/libsrtp/src/crypto/cipher/aes_icm.c:313:5: warning: implicit declaration of function ‘htonl’ * third_party/libsrtp/src/crypto/cipher/aes_icm.c:347:3: warning: implicit declaration of function ‘htons’ * third_party/libsrtp/src/crypto/include/datatypes.h:418:4: warning: implicit declaration of function ‘ntohl’ * third_party/libsrtp/src/crypto/include/datatypes.h:418:4: warning: implicit declaration of function ‘ntohl’ * third_party/libsrtp/src/crypto/include/datatypes.h:418:4: warning: implicit declaration of function ‘ntohl’ * third_party/libsrtp/src/srtp/srtp.c:604:4: warning: implicit declaration of function ‘htonl’ * third_party/libsrtp/src/srtp/srtp.c:808:8: warning: implicit declaration of function ‘ntohs’ * third_party/libsrtp/src/crypto/include/datatypes.h:418:4: warning: implicit declaration of function ‘ntohl’ * third_party/libsrtp/src/crypto/include/datatypes.h:418:4: warning: implicit declaration of function ‘ntohl’
Upstream bug tracking SRTP implementation: http://crbug.com/53986 Chromium tends to bundle libraries up front. Un-bundling is a an afterthought.
Upstream never implemented anything that actually uses this library. http://groups.google.com/a/chromium.org/group/chromium-dev/browse_thread/thread/3166cb689a366b6f A commit just landed to remove it. http://src.chromium.org/viewvc/chrome?view=rev&revision=85092
(In reply to comment #2) > Upstream never implemented anything that actually uses this library. > > http://groups.google.com/a/chromium.org/group/chromium-dev/browse_thread/ > thread/3166cb689a366b6f > > A commit just landed to remove it. > > http://src.chromium.org/viewvc/chrome?view=rev&revision=85092 They restored it, e.g. http://codereview.chromium.org/9223031 I'm working on an upstream fix.
Fixed in chromium-25.0.1323.1.