*** Re-sending this so it gets on-list -- I was sending this from a non-list approved address originally ***
*nod* I did find in the NEWS file in autoconf gits, and in their source release tarballs that macros that check for C99 types (e.g. AC_TYPE_INTXX_T, etc) were added in 2.59c. I just bumped up the required autoconf as specified in the AC_PREREQ call -- that should catch these errors and indicate what is needed without confusion -- I specified it to require 2.60, as I was not sure if AC_PREREQ macro could handle the releases with alpha characters in them i.e. 'c'. -- this change is contained in r10431. The thing I am confused about is: 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 sipXmediaLib/configure.ac lines 46-49 in r10430 (and actually, any revision) does not call any of the listed AC_TYPE macros... I'm still confused. I originally was thinking that it was speex that was doing this, but alas, I don't see speex using them either... We *should* be using them (checking for C99 integer types) as we are indeed now using them (since this past summer), but I see no evidence that we are using them now -- so I'm not sure where these errors are cropping up.. Re: PKG_CHECK_MODULES -- I'm trying to figure out a good way to see if these macros are defined, and complaining that we require some pkg-config to be installed in that case. From what I can see -- our use of PKG_PROG_PKG_CONFIG *should* do this for us, and catch that case, but alas, it seems it doesn't entirely work properly -- something should catch the fact that you had pkg-config installed in a different place... hum.. -- So, do you think this means that we require a pkg-config that is > 0.15, and definitely > 0.22? or, based on your odd install (having two versions installed, both in different places), that we cannot tell anything from this? the PKG_XXX_XXX macros are all usually installed in /usr/share/aclocal/pkg.m4 -- so I'm guessing that you may have had PATH set to find pkg-config 0.15, but the m4 macros used were the newly installed 0.22 ones -- so the 0.22 macros were accessing the 0.15 pkg-config executable -- which perhaps could cause some confusion. Then again, it looks like the pkg.m4 macros are not updated very often -- so it seems that it may be likely that they did not change between 0.15 and 0.22. On 12/27/07, [EMAIL PROTECTED] <[EMAIL PROTECTED]> wrote: > > 1.About the autoconf 2.59 error, the error comes with my autoconf 2.59-5. > But I find that autoconf 2.59c ships with the new AC_TYPE_INT16_T etc. > macro. I think 2.59c should work. > > 2.About the PKG_CHECK_MODULES error, it seems again my fault. > My original pkg-config was 0.15. And I upgraded it to 0.22. But I didn't > notice the new pkg-config was installed to /usr/local/ not to /usr. > > The PKG_CHECK_MODULES is a macro in pkg.m4 of 0.22 pkg-config which its > location is /usr/local/share/aclocal/. But configure script looks for > pkg.m4 at /usr/share/aclocal/. > > So I copy /usr/local/share/aclocal/pkg.m4 to /usr/share/aclocal/, > everything works well now. > > 3.Report another thing: > > RHEL4's bash is 3.0-19.2. And it doesn't recognize the expression > configure script: > > CFLAG+="BLA...BLA...BLA..." > > After I upgraded bash to 3.2.33. It works well. > > 在2007-12-26，"Alexander Chemeris" <[EMAIL PROTECTED]> 写道： > > On 12/25/07, wsycqyz < > [EMAIL PROTECTED]> wrote: > > ----> So I upgrade autoconf to 2.60 and run autoreconf -fi. The error > > doesn't come out. Is upgrading to 2.60 OK? > > > > Then I run ./configure, and this comes out: > > checking for libspandsp >= 0.0.2pre26... not found > > checking if speex dsp usage is enabled... no > > ./configure: line 26449: syntax error near unexpected token `SPEEX,' > > ./configure: line 26449: ` PKG_CHECK_MODULES(SPEEX,' > > > > ---->I guess this problem is about the version of automake, autoconf and > > aclocal. May be I was wrong. Any idea? Thanks! > > No, this seems like a problem with our configure scripts. They does not > check is pkg-config is present on build system or not. You could either > comment out checking for speex in configure.ac or install pkg-config. > > -- > Regards, > Alexander Chemeris. > > SIPez LLC. > SIP VoIP, IM and Presence Consulting > > http://www.SIPez.com > tel: +1 (617) 273-4000 > > -- Keith Kyzivat SIPez LLC. SIP VoIP, IM and Presence Consulting http://www.SIPez.com tel: +1 (617) 273-4000 -- 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/
