> > I hate to say it, but I see so many people quote error messages that > > read "xxxx.c line nnn" and then ask "what's up?". You really need > to > > also post the lines of code around "nnn" so we can read them. > > the lines numbers depend on when you did the CVS checkout. We > > all have different working code code. > Well, we have to allow users that aren't C programmers to report bugs > and copy possible error messages, don't we? Many different people are > needed in an open source project, not all have to be programmers. > Documentation, testing and marketing is important as well.
You don't need to know a lot about programming to cut and past lines out of a file. You don't have to fix the problem. But it would help a lot if you could identify _which_ line the error is comming from. I don't read Greek but I bet I could find the 12th line on page 72 in some Greek book. But I assumed anyone who's attempting to port Asterisk to BSD would know about C and the BSD system. Ports like that, mostly require a bit of programming. I expect you will need to re-write 1/3rd of the code in the zaptel directory. No way would any of that stuff work on BSD. > > And, I did look at the specific line in the source and could just > note > that it was beyond my knowledge to understand it and fix it ;-( > ===== Chris Albertson Home: 310-376-1029 [EMAIL PROTECTED] Cell: 310-990-7550 Office: 310-336-5189 [EMAIL PROTECTED] KG6OMK __________________________________ Do you Yahoo!? Exclusive Video Premiere - Britney Spears http://launch.yahoo.com/promos/britneyspears/ _______________________________________________ Asterisk-Users mailing list [EMAIL PROTECTED] http://lists.digium.com/mailman/listinfo/asterisk-users
