On Sat, Aug 02, 2003 at 09:47:04PM -0500, Mark Spencer wrote:
> > i managed to tweak and compile 99% of the code with -Wall -Werror.
> > (this is a standard porting method i use).
>
> Yes, I am definitely a HUGE fan of -Wall, although I"ve gotten burned by
> -Werror unfortunately, so against my ow
> apparently digium will release the specs for their hardware under NDA,
> so i'll try to encourage some BSD-like hardware/kernel people to poke at
> more substantial support of hardware.
With fully Open Source drivers already available, I'm not sure what other
information you would need on our ha
I've been taking some portability fixes already in the direction of
FreeBSD. Right now the best method would likely be to submit the patches
via the Asterisk bug tracker at http://bugs.digium.com.
Only a few people outside of Digium have CVS write permission, and
especially for something like thi
On Sat, Aug 02, 2003 at 12:29:03PM -0500, Tilghman Lesher wrote:
> > my comments were more related to the fact that while you can set some
> > things in the Makefile, there are a number of places in the code
> > which use static strings (ignoring the Makefile).
> >
> > so saying "The location for t
On Saturday 02 August 2003 12:14, Jim Mercer wrote:
> On Sat, Aug 02, 2003 at 11:59:53AM -0500, Tilghman Lesher wrote:
> > On Saturday 02 August 2003 11:16, Jim Mercer wrote:
> > > and i have some ideas about making the build process a little
> > > less linux specific (ie. putting configs in
> > >
On Sat, Aug 02, 2003 at 11:59:53AM -0500, Tilghman Lesher wrote:
> On Saturday 02 August 2003 11:16, Jim Mercer wrote:
> > i've ported asterisk to FreeBSD without hardware support.
> > work is moving forward on a BSD ztdummy driver.
>
> Good work.
apparently digium will release the specs for thei
On Saturday 02 August 2003 11:16, Jim Mercer wrote:
> i've ported asterisk to FreeBSD without hardware support.
> work is moving forward on a BSD ztdummy driver.
Good work.
> in the process of the porting, i've found a number of instances where
> there were un-initialized variables and various co
i've ported asterisk to FreeBSD without hardware support.
work is moving forward on a BSD ztdummy driver.
in the process of the porting, i've found a number of instances where
there were un-initialized variables and various cosmetic changes, which
are OS independent issues.
then there are a numb
On Sat, 2003-08-02 at 00:11, [EMAIL PROTECTED] wrote:
> > checking for tgetent in -ltermcap... no
> > checking for tgetent in -ltinfo... no
> > checking for tgetent in -lcurses... no
> > checking for tgetent in -lncurses... no
> > configure: error: termcap support not found
>
>
> which part of th
