[asterisk-users] More Zaptel build problems

Kristian Kielhofner kris at krisk.org
Tue Sep 12 07:50:39 MST 2006

Kristian Kielhofner wrote:
> Hello everyone,
>     I am trying to build zaptel 1.2.9 for AstLinux.  I have already done 
> an svn export of the 1.2.9 tag, so I am not experiencing the "missing 
> octastic issue".
>     However, I am having a funny problem.  The zaptel.log that I have 
> attached tells the full story, but I'll give you a synopsis...
> - Because I need to cross compile and the Zaptel Makefile does not 
> really have a concept of CC/HOSTCC, I have to build the "makefw 
> gendigits tor2fw.h radfw.h" targets with my HOSTCC - gcc.  I then build 
> the rest of zaptel using the "normal" uclibc cross compiler.  This has 
> always worked until now.
> - AstLinux doesn't have hotplug, so I have to define 
> HOTPLUG_FIRMWARE=no.  This means that vpm450m.c has to include 
> vpm450m_fw.h which, as shown in the compiler output attached, has some 
> syntax errors:
> /home/kris/projects/astlinux-trunk/build_i586/zaptel-1.2.9/wct4xxp/vpm450m_fw.h:1: 
> error: syntax error before '/' token
> In file included from 
> /home/kris/projects/astlinux-trunk/build_i586/zaptel-1.2.9/wct4xxp/vpm450m.c:16: 
> /home/kris/projects/astlinux-trunk/build_i586/zaptel-1.2.9/wct4xxp/vpm450m_fw.h:1:75: 
> too many decimal points in number
> /home/kris/projects/astlinux-trunk/build_i586/zaptel-1.2.9/wct4xxp/vpm450m.c: 
> In function `init_vpm450m':
> /home/kris/projects/astlinux-trunk/build_i586/zaptel-1.2.9/wct4xxp/vpm450m.c:405: 
> error: `vpm450m_fw' undeclared (first use in this function)
> /home/kris/projects/astlinux-trunk/build_i586/zaptel-1.2.9/wct4xxp/vpm450m.c:405: 
> error: (Each undeclared identifier is reported only once
> /home/kris/projects/astlinux-trunk/build_i586/zaptel-1.2.9/wct4xxp/vpm450m.c:405: 
> error: for each function it appears in.)
>     My guess is that my hack of building makefw and friends might not 
> work anymore...  Or maybe this is some kind of strange bug.  Any ideas?
> Thanks!
> -- 
> Kristian Kielhofner

Kristian (replying to my own post),

	It seems that this error was from fw2h.c putting the full pathname in 
the generated vpm450m_fw.h.  Although I just spent 20 minutes making my 
own patch, it seems that it was fixed a while ago in r1458.  Woo hoo 

Kristian Kielhofner

More information about the asterisk-users mailing list