From: Jeremy McNamara Date: Wed, 26 May 2004 19:28:14 +0000 (+0000) Subject: explain a proper upgrade sequence (lowering the signal-to-noise ratio again) X-Git-Tag: 1.0.0-rc1~372 X-Git-Url: http://git.ipfire.org/cgi-bin/gitweb.cgi?a=commitdiff_plain;h=728cceca7e0dc0e3ec409e6b7de143d6fd1c963f;p=thirdparty%2Fasterisk.git explain a proper upgrade sequence (lowering the signal-to-noise ratio again) git-svn-id: https://origsvn.digium.com/svn/asterisk/trunk@3081 65c4cc65-6c06-0410-ace0-fbb531ad65f3 --- diff --git a/channels/h323/README b/channels/h323/README index eec7e2b8dc..7f39cf6d36 100755 --- a/channels/h323/README +++ b/channels/h323/README @@ -78,11 +78,20 @@ We recomend puting the above directives into your /etc/profile so you do not have to remember to export those values every time you want to recompile. -If you still have trouble please contact 'JerJer' in #Asterisk on -irc.freenode.net or send and email to jj@nufone.net + +Note Upgrading Asterisk: + +After you cvs update (or make update) Asterisk you have to go into +asterisk/channels/h323 and issue a make clean, before compiling the +rest of asterisk. Doing this process every time you upgrade Asterisk +will ensure a sane build. + + +If you are still having trouble contact 'JerJer' in #Asterisk on +irc.freenode.net or send reasonable debug information to support@nufone.net. If you happen to be lucky enough to segfault this code please run a -backtrace and send me the gory details. Segmentation faults are not +backtrace and send me the gory details. Segmentation faults are not tolerated, no matter what Distro you run! bt example: