Apart from the tutorial itself, what I wanted to point out was that the way asterisk, zaptel and libpri are to be built is different for each project, and this is sub-optimal; and that by building Asterisk as required, you get a linkage error. l.
On Sat, 29 Mar 2008 12:03:59 +0100, Alan Lord <[EMAIL PROTECTED]> wrote: > Lenz wrote: >> Hello list, >> after spending the best part of an afternoon trying to build Asterisk on >> an old EPIA VIA C3, I thought that writing a tutorial would make life >> easier for future compilers: >> >> http://astrecipes.net/index.php?n=356 >> >> I had never compiled Asterisk for a different architecture, and I'm >> pretty >> disappointed at how complex it is - building Zaptel, Libpri and Asterisk >> requires discovering three different procedures, and even passing the >> required architecture to the autoconfig module was not enough for a >> clean >> build - libpthread and libresolv would not link, so you have to add them >> manually. Aybody got an idea of who should be notified of this immediate >> problem, apart for the time-wasteful general compilation procedure? >> >> Thanks >> l. >> >> >> >> > > Hi there, > > I didn't find it too much trouble in a Via C700N system. But I wouldn't > use one of the mainstream distros for the OS. They chew up system > resources just trying to accommodate "any" hardware. > > The solution is to roll-your-own. See this series of articles on my > blog... http://www.theopensourcerer.com/tag/asterisk/ > > Cheers > > Al > -- Loway Research - Home of QueueMetrics http://queuemetrics.com _______________________________________________ -- Bandwidth and Colocation Provided by http://www.api-digital.com -- asterisk-users mailing list To UNSUBSCRIBE or update options visit: http://lists.digium.com/mailman/listinfo/asterisk-users
