Thanks to everyone who replied.

This is great news ;).

I'll get the thing upgraded tonight (when it's quiet).

Thanks again.


-----Original Message-----
From: asterisk-users-boun...@lists.digium.com 
[mailto:asterisk-users-boun...@lists.digium.com] On Behalf Of Ryan Wagoner
Sent: 26 July 2010 16:04
To: Asterisk Users Mailing List - Non-Commercial Discussion
Subject: Re: [asterisk-users] 'dirty' upgrade of 1.4


When you run make, it compiles the binaries in the src directory. Once it is 
done compiling stop asterisk. Running make install will copy the compiled 
binaries into their respective folders on your system. Then just start 
asterisk. If you need to revert, stop asterisk, run make install in the old src 
directory, then start asterisk.

Ryan

On Mon, Jul 26, 2010 at 9:45 AM, Andrew Thomas <a...@datavox.co.uk> wrote:
> Hi Danny,
>
> I understand (and welcome) the separate src directories.  This would 
> allow me to 'revert' should I feel the need (assuming I can just 
> re-compile over each one).  I just need to know if I can re-compile 
> over the existing first.
>
> Thanks for your reply.
>
>
>
> -----Original Message-----
> From: asterisk-users-boun...@lists.digium.com
> [mailto:asterisk-users-boun...@lists.digium.com] On Behalf Of Danny 
> Nicholas
> Sent: 26 July 2010 14:15
> To: 'Asterisk Users Mailing List - Non-Commercial Discussion'
> Subject: Re: [asterisk-users] 'dirty' upgrade of 1.4
>
>
>>From: asterisk-users-boun...@lists.digium.com [mailto:asterisk-users-
>>Subject: [asterisk-users] 'dirty' upgrade of 1.4
>
>>Apologies if this has been asked before.
>
>>Does anyone know if I can simply recompile * 1.4.34 over 1.4.24.1?
>
>>Ie. perform an upgrade from 1.4.24.1 to 1.4.34 by just rebuilding the
> source files for 1.4.34 over the top of the existing 1.4.24.1 files.
>
>>Also, will I need to stop * to perform this routine - or can I just
> 'upgrade' and then do a * 'restart'?
>
> Question 1 - unless you are "un-tarring" to a specific directory, you 
> would have /usr/local/src/asterisk-1.4.24.1 and 
> /usr/local/src/asterisk-1.4.34 segregated source trees.
>
> Question 2 - you don't "have" to stop asterisk, but you should (best
> practice?) since installing a new release usually involves 
> removing/replacing the .so files in /usr/lib/asterisk/modules.
>
>
>
> -- 
> _____________________________________________________________________
> -- 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
>
> -- 
> _____________________________________________________________________
> -- 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
>

-- 
_____________________________________________________________________
-- 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

-- 
_____________________________________________________________________
-- 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