Re: pkg/44257 (comms/asterisk18 fails to build on DragonFly)

On Tue, Dec 21, 2010 at 11:55:01AM +0000, John Nemeth wrote:
> The following reply was made to PR pkg/44257; it has been noted by GNATS.
>
> From: jnemeth%CornerstoneService.ca@localhost (John Nemeth)
> To: Francois Tigeot <ftigeot%wolfpond.org@localhost>,
> gnats-bugs%NetBSD.org@localhost
> Cc: pkgsrc-bugs%NetBSD.org@localhost
> Subject: Re: pkg/44257 (comms/asterisk18 fails to build on DragonFly)
> Date: Tue, 21 Dec 2010 03:50:41 -0800
>
> Thanks for doing this. Although I create and maintain the
> Asterisk packages for my own purposes, it is still really nice to
> see others using them.
You're welcome.
Although I'm only a would-be user for now, I figured I could at least
attempt to fix the build before playing with Asterisk.
> } > channels/chan_usbradio.c
> } > channels/chan_dahdi.c
> } I'm unsure; they don't seem to be compiled by default.
>
> chan_usbradio appears to be an interface to a ham (amateur)
> radio. I haven't used or tested it. chan_dahdi is unusable on
> NetBSD. DAHDI (Digium hardware drivers) has been ported to FreeBSD.
> [...]
> However, given that DragonFlyBSD
> was spun off of FreeBSD not that long ago, it might not be as big
> a chore to port it to DragonFlyBSD if you want to take a stab at
> it. If you're successful and create a package, I can add it to
> pkgsrc for you, but I can't really offer any assistance beyond
> basic help with creating a package.
Thanks for the offer, but I don't have any experience with hardware
drivers so I'll pass for now.
Besides, it has already been seven years since DragonFly was forked
from FreeBSD and I believe there was significant changes in some part
of the driver API (locking stuff for SMP comes to mind).
> I'm doing a test build right now with all the patches. Once my
> test build is complete (in the morning) I'll commit the changes and ask
> you to do a test build.
Sure. I'll happily test the new state of things.
--
Francois Tigeot