[App_rpt-users] Compile Errors

Jim Duuuude telesistant at hotmail.com
Thu Jul 4 16:49:33 EDT 2013


OFficially, I will "neither deny nor confirm" that... :-) :-)

And yeah, libpri *REALLY* isnt necessary, but I always added it
for completeness. 

Jim


> Date: Thu, 4 Jul 2013 15:45:33 -0500
> Subject: Re: [App_rpt-users] Compile Errors
> From: robert at n5qm.com
> To: telesistant at hotmail.com
> CC: app_rpt-users at ohnosec.org
> 
> Jim,
> 
> So, you have compiled using a 3.x kernel using dahdi?  Did you compile
> libpri as well, or is it even necessary since we aren't using PRI
> signaling?
> 
> Robert
> N5QM
> 
> On Thu, Jul 4, 2013 at 3:29 PM, Jim Duuuude <telesistant at hotmail.com> wrote:
> > ahhhhh.. sure...
> >
> > If you wanna "go where do man has gone before" (or not many, actually),
> > I have included a very minimal patch set which will "fix" DAHDI so that
> > it actually works, and you can try using DAHDI instead...
> >
> > Jim
> >
> >> Date: Thu, 4 Jul 2013 15:11:08 -0500
> >> From: robert at n5qm.com
> >> CC: app_rpt-users at ohnosec.org
> >
> >> Subject: Re: [App_rpt-users] Compile Errors
> >>
> >> I guess I should have researched that before I tried huh? lol
> >>
> >> Robert
> >> N5QM
> >>
> >> On Thu, Jul 4, 2013 at 2:37 PM, Jim Duuuude <telesistant at hotmail.com>
> >> wrote:
> >> > I guess that's not GIGANTICALLY surprising, since Zaptel isn't even
> >> > CAPABLE of being compiled under a 3.X kernel, since there was a
> >> > major change in the ioctl() functionality in the driver stuff.
> >> >
> >> > Jim
> >> >
> >> >> Date: Thu, 4 Jul 2013 11:58:44 -0500
> >> >> From: robert at n5qm.com
> >> >> To: app_rpt-users at ohnosec.org
> >> >> Subject: Re: [App_rpt-users] Compile Errors
> >> >
> >> >>
> >> >> This appears to be an issue trying to compile against the 3.2 kernel.
> >> >> I tried on a 2.6 kernel and the issues were gone.
> >> >>
> >> >> Robert
> >> >> N5QM
> >> >>
> >> >> On Sun, Jun 30, 2013 at 6:05 PM, Robert Garcia <robert at n5qm.com> wrote:
> >> >> > Guys,
> >> >> >
> >> >> > I am working on compiling app_rpt for another platform using the
> >> >> > sources from svn and following the makefile. It looks like I am going
> >> >> > to need some help as I am already stuck at configuring zaptel. lol
> >> >> >
> >> >> > gcc -o menuselect menuselect.o strcompat.o menuselect_stub.o
> >> >> > mxml/libmxml.a mxml/libmxml.a
> >> >> > make[2]: Leaving directory `/home/tc/zaptel/menuselect'
> >> >> > make[1]: Leaving directory `/home/tc/zaptel/menuselect'
> >> >> >
> >> >> > ***********************************************************
> >> >> > The existing menuselect.makeopts file did not specify
> >> >> > that 'zttool' should not be included. However, either some
> >> >> > dependencies for this module were not found or a
> >> >> > conflict exists.
> >> >> >
> >> >> > Either run 'make menuselect' or remove the existing
> >> >> > menuselect.makeopts file to resolve this issue.
> >> >> > ***********************************************************
> >> >> >
> >> >> > make: *** [menuselect.makeopts] Error 255
> >> >> >
> >> >> > I then nuked the menuselect.makeopts per the error and tried again, I
> >> >> > get a little further before receiving this error.
> >> >> >
> >> >> > make -C /lib/modules/3.0.21-tinycore/build ARCH=i386
> >> >> > SUBDIRS=/usr/src/zaptel/kernel HOTPLUG_FIRMWARE=yes
> >> >> > KBUILD_OBJ_M="zaptel.o ztdummy.o ztdynamic.o zttranscode.o " modules
> >> >> > make[2]: Entering directory
> >> >> > `/usr/local/src/linux-headers-3.0.21-tinycore'
> >> >> > CC [M] /usr/src/zaptel/kernel/zaptel-base.o
> >> >> > In file included from /usr/src/zaptel/kernel/zaptel-base.c:37:0:
> >> >> > /usr/src/zaptel/kernel/zconfig.h:26:28: fatal error:
> >> >> > linux/autoconf.h:
> >> >> > No such file or directory
> >> >> > compilation terminated.
> >> >> > make[3]: *** [/usr/src/zaptel/kernel/zaptel-base.o] Error 1
> >> >> > make[2]: *** [_module_/usr/src/zaptel/kernel] Error 2
> >> >> > make[2]: Leaving directory
> >> >> > `/usr/local/src/linux-headers-3.0.21-tinycore'
> >> >> > make[1]: *** [modules] Error 2
> >> >> > make[1]: Leaving directory `/usr/src/zaptel'
> >> >> > make: *** [all] Error 2
> >> >> > make: Leaving directory `/usr/src/zaptel'
> >> >> >
> >> >> > Oddly, the linux/autoconf.h file is there, so I'm not sure what path
> >> >> > is the base. I "fixed" that by providing an absolute path to the
> >> >> > autoconf.h file. Then I tried again and received this.
> >> >> >
> >> >> > make -C /lib/modules/3.0.21-tinycore/build ARCH=i386
> >> >> > SUBDIRS=/usr/src/zaptel/kernel HOTPLUG_FIRMWARE=yes
> >> >> > KBUILD_OBJ_M="zaptel.o ztdummy.o ztdynamic.o zttranscode.o " modules
> >> >> > make[2]: Entering directory
> >> >> > `/usr/local/src/linux-headers-3.0.21-tinycore'
> >> >> > CC [M] /usr/src/zaptel/kernel/zaptel-base.o
> >> >> > /usr/src/zaptel/kernel/zaptel-base.c: In function 'zt_rbs_sethook':
> >> >> > /usr/src/zaptel/kernel/zaptel-base.c:2160:2: warning: suggest
> >> >> > parentheses around operand of '!' or change '&' to '&&' or '!' to '~'
> >> >> > [-Wparentheses]
> >> >> > /usr/src/zaptel/kernel/zaptel-base.c: At top level:
> >> >> > /usr/src/zaptel/kernel/zaptel-base.c:7650:2: error: unknown field
> >> >> > 'ioctl' specified in initializer
> >> >> > /usr/src/zaptel/kernel/zaptel-base.c:7650:2: warning: initialization
> >> >> > from incompatible pointer type [enabled by default]
> >> >> > /usr/src/zaptel/kernel/zaptel-base.c:7650:2: warning: (near
> >> >> > initialization for 'zt_fops.fsync') [enabled by default]
> >> >> > make[3]: *** [/usr/src/zaptel/kernel/zaptel-base.o] Error 1
> >> >> > make[2]: *** [_module_/usr/src/zaptel/kernel] Error 2
> >> >> > make[2]: Leaving directory
> >> >> > `/usr/local/src/linux-headers-3.0.21-tinycore'
> >> >> > make[1]: *** [modules] Error 2
> >> >> > make[1]: Leaving directory `/usr/src/zaptel'
> >> >> > make: *** [all] Error 2
> >> >> > make: Leaving directory `/usr/src/zaptel'
> >> >> >
> >> >> > Any ideas on how I can get past this?
> >> >> >
> >> >> > Robert
> >> >> > N5QM
> >> >> _______________________________________________
> >> >> App_rpt-users mailing list
> >> >> App_rpt-users at ohnosec.org
> >> >> http://ohnosec.org/cgi-bin/mailman/listinfo/app_rpt-users
> >> _______________________________________________
> >> App_rpt-users mailing list
> >> App_rpt-users at ohnosec.org
> >> http://ohnosec.org/cgi-bin/mailman/listinfo/app_rpt-users
 		 	   		  
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.allstarlink.org/pipermail/app_rpt-users/attachments/20130704/267eb64d/attachment.html>


More information about the App_rpt-users mailing list