At 12:23 PM 7/24/2010, you wrote:
>At 10:01 AM 7/24/2010, you wrote:
> >The version of gcc is most definitely related to this problem, 
> although it is
> >the linker that is the problem.  My recommendation for solving this problem
> >is to use 'make menuselect' to eliminate any modules that you do not wish
> >to load, then ensure modules that you definitely want (app_stack,
> >app_voicemail) are selected.  Follow that up by eliminating all "noload"
> >statements from /etc/asterisk/modules.conf and Asterisk should load fine.
>
>I wonder if this is a problem with my old modules.conf. I'll rename
>it and see if that clears up the problem.


So I changed modules.conf to only include the line "autoload=yes" and 
lo and behold 1.8 is happily up and running so all I might suggest is 
a a warning about checking modules.conf if you get odd unexpected 
errors when upgrading to 1.8.

Is it worth my figuring out which noload lines caused my problem or 
is that enough information to clear up the question?  I'm happy to do 
it, but it doesn't seem like it would actually be useful information.

Ira


-- 
_____________________________________________________________________
-- Bandwidth and Colocation Provided by http://www.api-digital.com --
New to Asterisk? Join us for a live introductory webinar every Thurs:
               http://www.asterisk.org/hello

asterisk-users mailing list
To UNSUBSCRIBE or update options visit:
   http://lists.digium.com/mailman/listinfo/asterisk-users

Reply via email to