[asterisk-dev] Asterisk trunk failure to build with zaptel branches/1.4

[Brian Candler]

I am trying to build Asterisk trunk with zaptel branches/1.4, since there is
no zaptel/trunk in Subversion. I'd like to check here before reporting to
bugs.digium.com in case I'm doing something stupid.

This is under CentOS 4.6:
Linux asterisk1 2.6.9-67.0.7.EL #1 Sat Mar 15 06:19:12 EDT 2008 i686 i686 i386 GNU/Linux

The compile of Asterisk is aborting at this point:

...
make[1]: Leaving directory `/home/candlerb/svn/asterisk/trunk/res'
make[1]: Entering directory `/home/candlerb/svn/asterisk/trunk/main'
   [CC] abstract_jb.c -> abstract_jb.o
   [CC] acl.c -> acl.o
   [CC] adsistub.c -> adsistub.o
   [CC] aescrypt.c -> aescrypt.o
   [CC] aeskey.c -> aeskey.o
   [CC] aestab.c -> aestab.o
   [CC] alaw.c -> alaw.o
   [CC] app.c -> app.o
   [CC] ast_expr2.c -> ast_expr2.o
   [CC] ast_expr2f.c -> ast_expr2f.o
   [CC] asterisk.c -> asterisk.o
In file included from /home/candlerb/svn/asterisk/trunk/include/asterisk/zapata.h:42,
                 from asterisk.c:125:
/usr/include/zaptel/zaptel.h:419: error: syntax error before "__s32"
/usr/include/zaptel/zaptel.h:420: error: syntax error before ':' token
/usr/include/zaptel/zaptel.h:954: error: syntax error before "__s32"
/usr/include/zaptel/zaptel.h:961: error: field `params' has incomplete type
make[1]: *** [asterisk.o] Error 1
make[1]: Leaving directory `/home/candlerb/svn/asterisk/trunk/main'
make: *** [main] Error 2

I'm building like this:

cd ~/svn/zaptel/branches
rm -rf 1.4
svn co http://svn.digium.com/svn/zaptel/branches/1.4
cd 1.4
./configure
make   # completes without errors
sudo make install

cd ~/svn/libpri
rm -rf trunk
svn co http://svn.digium.com/svn/libpri/trunk
cd trunk
make   # completes without errors
sudo make install

cd ~/svn/asterisk/trunk
rm -rf trunk
svn co http://svn.digium.com/svn/asterisk/trunk
cd trunk
./configure --enable-dev-mode
make menuselect  # enable DONT_OPTIMIZE, save with F12
make

At this point I get the error shown above.

Any ideas on how I should proceed?

Thanks,

Brian.