Re: [Astlinux-users] Asterisk 1.4 branch

[<gl...@gm...>]

Niksa,

What patch for zaptel from Digium are you talking about ? Can you post the =
url ?

On 5/8/07, Niksa Baldun <nik...@lu...> wrote:
> Kristian,
>
> thanks a lot for the clarification. However, I asure I wouldn0t do any of
> this if it wasn't necessary.
>
> You say you are working on zaptel, but I didn't have a problem with it. I
> used the latest version (+patch) from Digium's site and it compiled fine.
> However, asterisk wouldn't let me compile chan_zap until I changed the pa=
ths
> in asterisk.mk, I am quite certain of that.
>
> As for chan_misdn, it should work with 1.4, in fact it is a part of 1.4, =
and
> very important for European users like myself.
>
> Anyway, I am trying to learn more about inner workings of Asterisk and
> Astlinux, so I don't mind putting in a little time. If I make some progre=
ss
> I will share it, of course.
>
> Niksa Baldun
>
>
> Kristian Kielhofner wrote:
> On 5/8/07, Niksa Baldun <nik...@lu...> wrote:

>  Well, I've been at it all day, so I don't remember all the details.
> For
those packages that wouldn't compile, I checked which was the latest
> version
and updated the version number in the corresponding .mk file. I also
> updated
zaptel (I had to remove existing patch files and put the one I found
> on
Digium server). I had to change paths in asterisk.mk file so that
> configure
script would look for zaptel and libpri in correct
> places
(--with-pri=3D$(BUILD_DIR)/libpri-1.4.0
--with-zaptel=3D$(BUILD_DIR)/zaptel
--with-tonezone=3D$(BUILD_DIR)/zaptel).

> Also, there was some code in asterisk.mk that would always execute, even
> if
asterisk had already been built. For a lack of a better solution, I
> just
removed it temporarily.

 If there was anything else, I can't remember
> it now. Anyway, this is
obviously a work in progress, things like chan_misdn
> and spandsp are broken,
and who knows what else. I am sure Kristian and
> Darrick are rather busy, so
I wanted to work on this myself, I was just
> wandering what is the best way
to proceed.
 Niksa Baldun


> Niksa,

 I'd hate to see you do work that you don't have to do...

 The
> asterisk-beta branch should be well synced with trunk for
packages OTHER
> than libpri, zaptel, and asterisk. I just merged the
latest stuff from trunk
> into it. There weren't any significant
package updates.

 I build
> asterisk-beta about as often as I build trunk on the same
systems using the
> same methods. There aren't any more quirks than
there are in trunk -
> everything is identical EXCEPT for the asterisk,
zaptel, and libpri
> packages. Even so all of those build fine on my
systems...

 The latest
> zaptel does not build but I am working on that.

 Using --with-* and
> referencing ($BUILD_DIR) is not correct. The
necessary libraries and headers
> are copied to the proper locations in
$(STAGING_DIR) for Asterisk to find
> them. It might work for you, but
what is there now should work and is more
> correct. If you have to
hack this (or anything else), we should find out why
> and fix the real
problem.

 As far as add on packages like spandsp,
> chan_misdn, etc... They
will be supported:

a) Once Asterisk 1.4 itself has
> had enough testing
b) Once the packages themselves support Asterisk 1.4 we
> can update
our packages to use versions that might actually have a chance
> of
working
c) In some cases, they might not even be needed with Asterisk
> 1.4
(like app_conference)


>
> -------------------------------------------------------------------------
> This SF.net email is sponsored by DB2 Express
> Download DB2 Express C - the FREE version of DB2 express and take
> control of your XML. No limits. Just data. Click to get it now.
> http://sourceforge.net/powerbar/db2/
> _______________________________________________
> Astlinux-users mailing list
> Ast...@li...
> https://lists.sourceforge.net/lists/listinfo/astlinux-users
>
> Donations to support AstLinux are graciously accepted via PayPal to
> pa...@kr....
>


--=20
Guilherme Loch G=F3es

MSN:gl...@gm...
(48) 99115299