On 12/27/07, Jeremy A <[EMAIL PROTECTED]> wrote: > > Running on Centos 5.1 system and processing sipXmediaLib updated just > prior with svn update at around 0900UT Dec 27 > I get the following errors. > > Any suggestions? NB Just prior to this I compiled the latest svn > releases for sipXportLib, sipXsdpLib and sipXtackLib without problem. > > autoreconf -fi > /usr/share/aclocal/speex.m4:10: warning: underquoted definition of > XIPH_PATH_SPEEX > run info '(automake)Extending aclocal' > or see > http://sources.redhat.com/automake/automake.html#Extending-aclocal > /usr/share/aclocal/speex.m4:10: warning: underquoted definition of > XIPH_PATH_SPEEX > run info '(automake)Extending aclocal' > or see > http://sources.redhat.com/automake/automake.html#Extending-aclocal > /usr/share/aclocal/speex.m4:10: warning: underquoted definition of > XIPH_PATH_SPEEX > run info '(automake)Extending aclocal' > or see > http://sources.redhat.com/automake/automake.html#Extending-aclocal > configure.ac:46: error: possibly undefined macro: AC_TYPE_INT16_T > If this token and others are legitimate, please use > m4_pattern_allow. > See the Autoconf documentation. > configure.ac:47: error: possibly undefined macro: AC_TYPE_INT32_T > configure.ac:48: error: possibly undefined macro: AC_TYPE_INT8_T > configure.ac:49: error: possibly undefined macro: AC_TYPE_UINT8_T > autoreconf: /usr/bin/autoconf failed with exit status: 1
Hmm... This is an issue with speex's m4 macros... I have not run across these errors. I can say that they were no doubt introduced last week with sipXmediaLib configure changes I added -- those changes involved sub-configuring speex automatically when you autoreconf , and configure sipXmediaLib. I still need to make some changes to this, in addition to getting to the bottom of these errors. Can you provide me some more information? What versions of the autotools do you have installed? autoconf and automake. Separately (referring to a previous email by Keith Kryziat) , how do I > enable the new Topology graph by compiler flags? Which flags are > required and where? Is there any API level documentation on the graph use? The compiler flags I was referring to in the previous post were: ENABLE_TOPOLOGY_FLOWGRAPH_INTERFACE_FACTORY DISABLE_DEFAULT_PHONE_MEDIA_INTERFACE_FACTORY These preprocessor definitions are only needed during the compilation of sipXmediaLib. Just define both of these when compiling sipXmediaLib, and you'll be using the new flowgraph. All of our documentation is contained within the classes themselves -- we try to be as verbose as possible with the doxygen documentation and with comments in the code. In general, using the new flowgraph will work just as the old one did. It's just more flexible when one wants to get down and dirty and add new resources. -- Keith Kyzivat SIPez LLC. SIP VoIP, IM and Presence Consulting http://www.SIPez.com tel: +1 (617) 273-4000
_______________________________________________ sipxtapi-dev mailing list [email protected] List Archive: http://list.sipfoundry.org/archive/sipxtapi-dev/
