Menu
▾
▴
astlinux-users
|
From: Niksa B. <nik...@lu...> - 2007-05-08 07:05:48
|
After much trouble I managed to compile 1.4 branch (asterisk-beta). Some packages wouldn't compile (I had to update them to newer versions), and also there were some problems with asterisk.mk file. I am willing to work on this more, but I was wandering if it would be better to use the latest stable branch as a template, and incorporate Asterisk 1.4 there. I assume it is more up to date. Thanks. -- Niksa Baldun |
|
From: <gl...@gm...> - 2007-05-08 12:42:07
|
Niksa, What changes do you made to make it work with the asterisk-beta branch ? On 5/8/07, Niksa Baldun <nik...@lu...> wrote: > After much trouble I managed to compile 1.4 branch (asterisk-beta). Some > packages wouldn't compile (I had to update them to newer versions), and > also there were some problems with asterisk.mk file. > > I am willing to work on this more, but I was wandering if it would be > better to use the latest stable branch as a template, and incorporate > Asterisk 1.4 there. I assume it is more up to date. > > Thanks. > > -- > Niksa Baldun > > > > ------------------------------------------------------------------------- > 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 paypa= l...@kr.... > --=20 Guilherme Loch G=F3es MSN:gl...@gm... (48) 99115299 |
|
From: Niksa B. <nik...@lu...> - 2007-05-08 14:08:26
|
<!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN">
<html>
<head>
<meta content="text/html;charset=ISO-8859-1" http-equiv="Content-Type">
<title></title>
</head>
<body bgcolor="#ffffff" text="#000000">
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=$(BUILD_DIR)/libpri-1.4.0
--with-zaptel=$(BUILD_DIR)/zaptel --with-tonezone=$(BUILD_DIR)/zaptel).<br>
<br>
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.<br>
<br>
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.<br>
<pre class="moz-signature" cols="72">Niksa Baldun
</pre>
<br>
Guilherme Góes wrote:
<blockquote
cite="mid...@ma..."
type="cite">
<pre wrap="">Niksa,
What changes do you made to make it work with the asterisk-beta branch ?
On 5/8/07, Niksa Baldun <a class="moz-txt-link-rfc2396E" href="mailto:nik...@lu..."><nik...@lu...></a> wrote:
</pre>
<blockquote type="cite">
<pre wrap="">After much trouble I managed to compile 1.4 branch (asterisk-beta). Some
packages wouldn't compile (I had to update them to newer versions), and
also there were some problems with asterisk.mk file.
I am willing to work on this more, but I was wandering if it would be
better to use the latest stable branch as a template, and incorporate
Asterisk 1.4 there. I assume it is more up to date.
Thanks.
--
Niksa Baldun
-------------------------------------------------------------------------
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.
<a class="moz-txt-link-freetext" href="http://sourceforge.net/powerbar/db2/">http://sourceforge.net/powerbar/db2/</a>
_______________________________________________
Astlinux-users mailing list
<a class="moz-txt-link-abbreviated" href="mailto:Ast...@li...">Ast...@li...</a>
<a class="moz-txt-link-freetext" href="https://lists.sourceforge.net/lists/listinfo/astlinux-users">https://lists.sourceforge.net/lists/listinfo/astlinux-users</a>
Donations to support AstLinux are graciously accepted via PayPal to <a class="moz-txt-link-abbreviated" href="mailto:pa...@kr...">pa...@kr...</a>.
</pre>
</blockquote>
<pre wrap=""><!---->
</pre>
</blockquote>
</body>
</html>
|
|
From: Niksa B. <nik...@lu...> - 2007-05-08 17:24:35
|
<!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN">
<html>
<head>
<meta content="text/html;charset=ISO-8859-1" http-equiv="Content-Type">
<title></title>
</head>
<body bgcolor="#ffffff" text="#000000">
Kristian,<br>
<br>
thanks a lot for the clarification. However, I asure I wouldn0t do any
of this if it wasn't necessary.<br>
<br>
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 paths in asterisk.mk, I am quite certain of that.<br>
<br>
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.<br>
<br>
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
progress I will share it, of course.<br>
<br>
<pre class="moz-signature" cols="72">Niksa Baldun
</pre>
<br>
<br>
Kristian Kielhofner wrote:
<blockquote
cite="mid...@ma..."
type="cite">
<pre wrap="">On 5/8/07, Niksa Baldun <a class="moz-txt-link-rfc2396E" href="mailto:nik...@lu..."><nik...@lu...></a> wrote:
</pre>
<blockquote type="cite">
<pre wrap=""> 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=$(BUILD_DIR)/libpri-1.4.0
--with-zaptel=$(BUILD_DIR)/zaptel
--with-tonezone=$(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
</pre>
</blockquote>
<pre wrap=""><!---->
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)
</pre>
</blockquote>
</body>
</html>
|
|
From: Niksa B. <nik...@lu...> - 2007-05-08 19:04:02
|
<!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN"> <html> <head> <meta content="text/html;charset=ISO-8859-1" http-equiv="Content-Type"> <title></title> </head> <body bgcolor="#ffffff" text="#000000"> <a class="moz-txt-link-freetext" href="ftp://ftp.digium.com/pub/zaptel/releases/zaptel-1.4.2.tar.gz">ftp://ftp.digium.com/pub/zaptel/releases/zaptel-1.4.2.tar.gz</a><br> <a class="moz-txt-link-freetext" href="ftp://ftp.digium.com/pub/zaptel/releases/zaptel-1.4.2-patch.gz">ftp://ftp.digium.com/pub/zaptel/releases/zaptel-1.4.2-patch.gz</a><br> <br> <pre class="moz-signature" cols="72">Niksa Baldun </pre> <br> Guilherme Góes wrote: <blockquote cite="mid...@ma..." type="cite"> <pre wrap="">Niksa, What patch for zaptel from Digium are you talking about ? Can you post the url ? On 5/8/07, Niksa Baldun <a class="moz-txt-link-rfc2396E" href="mailto:nik...@lu..."><nik...@lu...></a> wrote: </pre> <blockquote type="cite"> <pre wrap="">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 paths 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 progress I will share it, of course. Niksa Baldun Kristian Kielhofner wrote: On 5/8/07, Niksa Baldun <a class="moz-txt-link-rfc2396E" href="mailto:nik...@lu..."><nik...@lu...></a> wrote: </pre> </blockquote> <pre wrap=""><!----> </pre> <blockquote type="cite"> <pre wrap=""> Well, I've been at it all day, so I don't remember all the details. For </pre> </blockquote> <pre wrap=""><!---->those packages that wouldn't compile, I checked which was the latest </pre> <blockquote type="cite"> <pre wrap="">version </pre> </blockquote> <pre wrap=""><!---->and updated the version number in the corresponding .mk file. I also </pre> <blockquote type="cite"> <pre wrap="">updated </pre> </blockquote> <pre wrap=""><!---->zaptel (I had to remove existing patch files and put the one I found </pre> <blockquote type="cite"> <pre wrap="">on </pre> </blockquote> <pre wrap=""><!---->Digium server). I had to change paths in asterisk.mk file so that </pre> <blockquote type="cite"> <pre wrap="">configure </pre> </blockquote> <pre wrap=""><!---->script would look for zaptel and libpri in correct </pre> <blockquote type="cite"> <pre wrap="">places </pre> </blockquote> <pre wrap=""><!---->(--with-pri=$(BUILD_DIR)/libpri-1.4.0 --with-zaptel=$(BUILD_DIR)/zaptel --with-tonezone=$(BUILD_DIR)/zaptel). </pre> <blockquote type="cite"> <pre wrap="">Also, there was some code in asterisk.mk that would always execute, even if </pre> </blockquote> <pre wrap=""><!---->asterisk had already been built. For a lack of a better solution, I </pre> <blockquote type="cite"> <pre wrap="">just </pre> </blockquote> <pre wrap=""><!---->removed it temporarily. If there was anything else, I can't remember </pre> <blockquote type="cite"> <pre wrap="">it now. Anyway, this is </pre> </blockquote> <pre wrap=""><!---->obviously a work in progress, things like chan_misdn </pre> <blockquote type="cite"> <pre wrap="">and spandsp are broken, </pre> </blockquote> <pre wrap=""><!---->and who knows what else. I am sure Kristian and </pre> <blockquote type="cite"> <pre wrap="">Darrick are rather busy, so </pre> </blockquote> <pre wrap=""><!---->I wanted to work on this myself, I was just </pre> <blockquote type="cite"> <pre wrap="">wandering what is the best way </pre> </blockquote> <pre wrap=""><!---->to proceed. Niksa Baldun </pre> <blockquote type="cite"> <pre wrap="">Niksa, </pre> </blockquote> <pre wrap=""><!----> I'd hate to see you do work that you don't have to do... The </pre> <blockquote type="cite"> <pre wrap="">asterisk-beta branch should be well synced with trunk for </pre> </blockquote> <pre wrap=""><!---->packages OTHER </pre> <blockquote type="cite"> <pre wrap="">than libpri, zaptel, and asterisk. I just merged the </pre> </blockquote> <pre wrap=""><!---->latest stuff from trunk </pre> <blockquote type="cite"> <pre wrap="">into it. There weren't any significant </pre> </blockquote> <pre wrap=""><!---->package updates. I build </pre> <blockquote type="cite"> <pre wrap="">asterisk-beta about as often as I build trunk on the same </pre> </blockquote> <pre wrap=""><!---->systems using the </pre> <blockquote type="cite"> <pre wrap="">same methods. There aren't any more quirks than </pre> </blockquote> <pre wrap=""><!---->there are in trunk - </pre> <blockquote type="cite"> <pre wrap="">everything is identical EXCEPT for the asterisk, </pre> </blockquote> <pre wrap=""><!---->zaptel, and libpri </pre> <blockquote type="cite"> <pre wrap="">packages. Even so all of those build fine on my </pre> </blockquote> <pre wrap=""><!---->systems... The latest </pre> <blockquote type="cite"> <pre wrap="">zaptel does not build but I am working on that. </pre> </blockquote> <pre wrap=""><!----> Using --with-* and </pre> <blockquote type="cite"> <pre wrap="">referencing ($BUILD_DIR) is not correct. The </pre> </blockquote> <pre wrap=""><!---->necessary libraries and headers </pre> <blockquote type="cite"> <pre wrap="">are copied to the proper locations in </pre> </blockquote> <pre wrap=""><!---->$(STAGING_DIR) for Asterisk to find </pre> <blockquote type="cite"> <pre wrap="">them. It might work for you, but </pre> </blockquote> <pre wrap=""><!---->what is there now should work and is more </pre> <blockquote type="cite"> <pre wrap="">correct. If you have to </pre> </blockquote> <pre wrap=""><!---->hack this (or anything else), we should find out why </pre> <blockquote type="cite"> <pre wrap="">and fix the real </pre> </blockquote> <pre wrap=""><!---->problem. As far as add on packages like spandsp, </pre> <blockquote type="cite"> <pre wrap="">chan_misdn, etc... They </pre> </blockquote> <pre wrap=""><!---->will be supported: a) Once Asterisk 1.4 itself has </pre> <blockquote type="cite"> <pre wrap="">had enough testing </pre> </blockquote> <pre wrap=""><!---->b) Once the packages themselves support Asterisk 1.4 we </pre> <blockquote type="cite"> <pre wrap="">can update </pre> </blockquote> <pre wrap=""><!---->our packages to use versions that might actually have a chance </pre> <blockquote type="cite"> <pre wrap="">of </pre> </blockquote> <pre wrap=""><!---->working c) In some cases, they might not even be needed with Asterisk </pre> <blockquote type="cite"> <pre wrap="">1.4 </pre> </blockquote> <pre wrap=""><!---->(like app_conference) </pre> <blockquote type="cite"> <pre wrap="">------------------------------------------------------------------------- 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. <a class="moz-txt-link-freetext" href="http://sourceforge.net/powerbar/db2/">http://sourceforge.net/powerbar/db2/</a> _______________________________________________ Astlinux-users mailing list <a class="moz-txt-link-abbreviated" href="mailto:Ast...@li...">Ast...@li...</a> <a class="moz-txt-link-freetext" href="https://lists.sourceforge.net/lists/listinfo/astlinux-users">https://lists.sourceforge.net/lists/listinfo/astlinux-users</a> Donations to support AstLinux are graciously accepted via PayPal to <a class="moz-txt-link-abbreviated" href="mailto:pa...@kr...">pa...@kr...</a>. </pre> </blockquote> <pre wrap=""><!----> </pre> </blockquote> </body> </html> |
|
From: Kristian K. <kri...@gm...> - 2007-05-08 14:40:49
|
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=$(BUILD_DIR)/libpri-1.4.0 > --with-zaptel=$(BUILD_DIR)/zaptel > --with-tonezone=$(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) -- Kristian Kielhofner |
|
From: <gl...@gm...> - 2007-05-08 18:00:06
|
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 |
|
From: <gl...@gm...> - 2007-05-08 19:27:29
|
Can you send me your asterisk, libpri and zaptel dirs ? On 5/8/07, Niksa Baldun <nik...@lu...> wrote: > ftp://ftp.digium.com/pub/zaptel/releases/zaptel-1.4.2.tar.gz > ftp://ftp.digium.com/pub/zaptel/releases/zaptel-1.4.2-patch.gz > > Niksa Baldun > > Guilherme G=F3es wrote: > 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 paths 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 progress 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.... > > > ------------------------------------------------------------------------- > 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 |
|
From: Niksa B. <nik...@lu...> - 2007-05-08 20:26:45
|
<!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN">
<html>
<head>
<meta content="text/html;charset=ISO-8859-1" http-equiv="Content-Type">
<title></title>
</head>
<body bgcolor="#ffffff" text="#000000">
Well, sure, but there is not much point. I already explained the
modifications I made, and they are not that extensive. If you really
want it, I'll send them tomorrow when I am back at work. But I am just
learning this stuff, so this is probably not the best way to do things,
as Kristian pointed out.<br>
<pre class="moz-signature" cols="72">Niksa Baldun
</pre>
<br>
<br>
Guilherme Góes wrote:
<blockquote
cite="mid...@ma..."
type="cite">
<pre wrap="">Can you send me your asterisk, libpri and zaptel dirs ?
On 5/8/07, Niksa Baldun <a class="moz-txt-link-rfc2396E" href="mailto:nik...@lu..."><nik...@lu...></a> wrote:
</pre>
<blockquote type="cite">
<pre wrap=""><a class="moz-txt-link-freetext" href="ftp://ftp.digium.com/pub/zaptel/releases/zaptel-1.4.2.tar.gz">ftp://ftp.digium.com/pub/zaptel/releases/zaptel-1.4.2.tar.gz</a>
<a class="moz-txt-link-freetext" href="ftp://ftp.digium.com/pub/zaptel/releases/zaptel-1.4.2-patch.gz">ftp://ftp.digium.com/pub/zaptel/releases/zaptel-1.4.2-patch.gz</a>
Niksa Baldun
Guilherme Góes wrote:
Niksa,
</pre>
</blockquote>
<pre wrap=""><!---->
What patch for zaptel from Digium are you talking about ? Can you
</pre>
<blockquote type="cite">
<pre wrap="">post the url ?
</pre>
</blockquote>
<pre wrap=""><!---->
On 5/8/07, Niksa Baldun <a class="moz-txt-link-rfc2396E" href="mailto:nik...@lu..."><nik...@lu...></a> wrote:
</pre>
<blockquote type="cite">
<pre wrap="">Kristian,
</pre>
</blockquote>
<pre wrap=""><!---->
thanks a lot for the clarification. However, I asure I wouldn0t
</pre>
<blockquote type="cite">
<pre wrap="">do any of
</pre>
</blockquote>
<pre wrap=""><!---->this if it wasn't necessary.
You say you are working on zaptel,
</pre>
<blockquote type="cite">
<pre wrap="">but I didn't have a problem with it. I
</pre>
</blockquote>
<pre wrap=""><!---->used the latest version (+patch) from
</pre>
<blockquote type="cite">
<pre wrap="">Digium's site and it compiled fine.
</pre>
</blockquote>
<pre wrap=""><!---->However, asterisk wouldn't let me
</pre>
<blockquote type="cite">
<pre wrap="">compile chan_zap until I changed the paths
</pre>
</blockquote>
<pre wrap=""><!---->in asterisk.mk, I am quite
</pre>
<blockquote type="cite">
<pre wrap="">certain of that.
</pre>
</blockquote>
<pre wrap=""><!---->
As for chan_misdn, it should work with 1.4, in fact it is
</pre>
<blockquote type="cite">
<pre wrap="">a part of 1.4, and
</pre>
</blockquote>
<pre wrap=""><!---->very important for European users like myself.
Anyway, I
</pre>
<blockquote type="cite">
<pre wrap="">am trying to learn more about inner workings of Asterisk and
</pre>
</blockquote>
<pre wrap=""><!---->Astlinux, so I
</pre>
<blockquote type="cite">
<pre wrap="">don't mind putting in a little time. If I make some progress
</pre>
</blockquote>
<pre wrap=""><!---->I will share
</pre>
<blockquote type="cite">
<pre wrap="">it, of course.
</pre>
</blockquote>
<pre wrap=""><!---->
Niksa Baldun
Kristian Kielhofner wrote:
On 5/8/07, Niksa
</pre>
<blockquote type="cite">
<pre wrap="">Baldun <a class="moz-txt-link-rfc2396E" href="mailto:nik...@lu..."><nik...@lu...></a> wrote:
</pre>
</blockquote>
<pre wrap=""><!---->
</pre>
<blockquote type="cite">
<pre wrap=""> Well, I've been at it all day, so I don't remember all the details.
</pre>
</blockquote>
<pre wrap=""><!---->For
</pre>
<blockquote type="cite">
<pre wrap="">those packages that wouldn't compile, I checked which was the latest
</pre>
</blockquote>
<pre wrap=""><!---->
</pre>
<blockquote type="cite">
<pre wrap="">version
</pre>
</blockquote>
<pre wrap=""><!---->
</pre>
<blockquote type="cite">
<pre wrap="">and updated the version number in the corresponding .mk file. I also
</pre>
</blockquote>
<pre wrap=""><!---->
</pre>
<blockquote type="cite">
<pre wrap="">updated
</pre>
</blockquote>
<pre wrap=""><!---->
</pre>
<blockquote type="cite">
<pre wrap="">zaptel (I had to remove existing patch files and put the one I found
</pre>
</blockquote>
<pre wrap=""><!---->
</pre>
<blockquote type="cite">
<pre wrap="">on
</pre>
</blockquote>
<pre wrap=""><!---->
</pre>
<blockquote type="cite">
<pre wrap="">Digium server). I had to change paths in asterisk.mk file so that
</pre>
</blockquote>
<pre wrap=""><!---->
</pre>
<blockquote type="cite">
<pre wrap="">configure
</pre>
</blockquote>
<pre wrap=""><!---->
</pre>
<blockquote type="cite">
<pre wrap="">script would look for zaptel and libpri in correct
</pre>
</blockquote>
<pre wrap=""><!---->
</pre>
<blockquote type="cite">
<pre wrap="">places
</pre>
</blockquote>
<pre wrap=""><!---->
</pre>
<blockquote type="cite">
<pre wrap="">(--with-pri=$(BUILD_DIR)/libpri-1.4.0
</pre>
</blockquote>
<pre wrap=""><!---->--with-zaptel=$(BUILD_DIR)/zaptel
--with-tonezone=$(BUILD_DIR)/zaptel).
</pre>
<blockquote type="cite">
<pre wrap="">Also, there was some code in asterisk.mk that would always execute, even
</pre>
</blockquote>
<pre wrap=""><!---->if
</pre>
<blockquote type="cite">
<pre wrap="">asterisk had already been built. For a lack of a better solution, I
</pre>
</blockquote>
<pre wrap=""><!---->
</pre>
<blockquote type="cite">
<pre wrap="">just
</pre>
</blockquote>
<pre wrap=""><!---->
</pre>
<blockquote type="cite">
<pre wrap="">removed it temporarily.
</pre>
</blockquote>
<pre wrap=""><!---->
If there was anything else, I can't remember
</pre>
<blockquote type="cite">
<pre wrap="">it now. Anyway, this is
</pre>
</blockquote>
<pre wrap=""><!---->
</pre>
<blockquote type="cite">
<pre wrap="">obviously a work in progress, things like chan_misdn
</pre>
</blockquote>
<pre wrap=""><!---->
</pre>
<blockquote type="cite">
<pre wrap="">and spandsp are broken,
</pre>
</blockquote>
<pre wrap=""><!---->
</pre>
<blockquote type="cite">
<pre wrap="">and who knows what else. I am sure Kristian and
</pre>
</blockquote>
<pre wrap=""><!---->
</pre>
<blockquote type="cite">
<pre wrap="">Darrick are rather busy, so
</pre>
</blockquote>
<pre wrap=""><!---->
</pre>
<blockquote type="cite">
<pre wrap="">I wanted to work on this myself, I was just
</pre>
</blockquote>
<pre wrap=""><!---->
</pre>
<blockquote type="cite">
<pre wrap="">wandering what is the best way
</pre>
</blockquote>
<pre wrap=""><!---->
</pre>
<blockquote type="cite">
<pre wrap="">to proceed.
</pre>
</blockquote>
<pre wrap=""><!----> Niksa Baldun
</pre>
<blockquote type="cite">
<pre wrap="">Niksa,
</pre>
</blockquote>
<pre wrap=""><!---->
</pre>
<blockquote type="cite">
<pre wrap=""> I'd hate to see you do work that you don't have to do...
</pre>
</blockquote>
<pre wrap=""><!---->
The
</pre>
<blockquote type="cite">
<pre wrap="">asterisk-beta branch should be well synced with trunk for
</pre>
</blockquote>
<pre wrap=""><!---->
</pre>
<blockquote type="cite">
<pre wrap="">packages OTHER
</pre>
</blockquote>
<pre wrap=""><!---->
</pre>
<blockquote type="cite">
<pre wrap="">than libpri, zaptel, and asterisk. I just merged the
</pre>
</blockquote>
<pre wrap=""><!---->
</pre>
<blockquote type="cite">
<pre wrap="">latest stuff from trunk
</pre>
</blockquote>
<pre wrap=""><!---->
</pre>
<blockquote type="cite">
<pre wrap="">into it. There weren't any significant
</pre>
</blockquote>
<pre wrap=""><!---->
</pre>
<blockquote type="cite">
<pre wrap="">package updates.
</pre>
</blockquote>
<pre wrap=""><!---->
I build
</pre>
<blockquote type="cite">
<pre wrap="">asterisk-beta about as often as I build trunk on the same
</pre>
</blockquote>
<pre wrap=""><!---->
</pre>
<blockquote type="cite">
<pre wrap="">systems using the
</pre>
</blockquote>
<pre wrap=""><!---->
</pre>
<blockquote type="cite">
<pre wrap="">same methods. There aren't any more quirks than
</pre>
</blockquote>
<pre wrap=""><!---->
</pre>
<blockquote type="cite">
<pre wrap="">there are in trunk -
</pre>
</blockquote>
<pre wrap=""><!---->
</pre>
<blockquote type="cite">
<pre wrap="">everything is identical EXCEPT for the asterisk,
</pre>
</blockquote>
<pre wrap=""><!---->
</pre>
<blockquote type="cite">
<pre wrap="">zaptel, and libpri
</pre>
</blockquote>
<pre wrap=""><!---->
</pre>
<blockquote type="cite">
<pre wrap="">packages. Even so all of those build fine on my
</pre>
</blockquote>
<pre wrap=""><!---->
</pre>
<blockquote type="cite">
<pre wrap="">systems...
</pre>
</blockquote>
<pre wrap=""><!---->
The latest
</pre>
<blockquote type="cite">
<pre wrap="">zaptel does not build but I am working on that.
</pre>
</blockquote>
<pre wrap=""><!---->
</pre>
<blockquote type="cite">
<pre wrap=""> Using --with-* and
</pre>
</blockquote>
<pre wrap=""><!---->
</pre>
<blockquote type="cite">
<pre wrap="">referencing ($BUILD_DIR) is not correct. The
</pre>
</blockquote>
<pre wrap=""><!---->
</pre>
<blockquote type="cite">
<pre wrap="">necessary libraries and headers
</pre>
</blockquote>
<pre wrap=""><!---->
</pre>
<blockquote type="cite">
<pre wrap="">are copied to the proper locations in
</pre>
</blockquote>
<pre wrap=""><!---->
</pre>
<blockquote type="cite">
<pre wrap="">$(STAGING_DIR) for Asterisk to find
</pre>
</blockquote>
<pre wrap=""><!---->
</pre>
<blockquote type="cite">
<pre wrap="">them. It might work for you, but
</pre>
</blockquote>
<pre wrap=""><!---->
</pre>
<blockquote type="cite">
<pre wrap="">what is there now should work and is more
</pre>
</blockquote>
<pre wrap=""><!---->
</pre>
<blockquote type="cite">
<pre wrap="">correct. If you have to
</pre>
</blockquote>
<pre wrap=""><!---->
</pre>
<blockquote type="cite">
<pre wrap="">hack this (or anything else), we should find out why
</pre>
</blockquote>
<pre wrap=""><!---->
</pre>
<blockquote type="cite">
<pre wrap="">and fix the real
</pre>
</blockquote>
<pre wrap=""><!---->
</pre>
<blockquote type="cite">
<pre wrap="">problem.
</pre>
</blockquote>
<pre wrap=""><!---->
As far as add on packages like spandsp,
</pre>
<blockquote type="cite">
<pre wrap="">chan_misdn, etc... They
</pre>
</blockquote>
<pre wrap=""><!---->
</pre>
<blockquote type="cite">
<pre wrap="">will be supported:
</pre>
</blockquote>
<pre wrap=""><!---->
a) Once Asterisk 1.4 itself has
</pre>
<blockquote type="cite">
<pre wrap="">had enough testing
</pre>
</blockquote>
<pre wrap=""><!---->
</pre>
<blockquote type="cite">
<pre wrap="">b) Once the packages themselves support Asterisk 1.4 we
</pre>
</blockquote>
<pre wrap=""><!---->
</pre>
<blockquote type="cite">
<pre wrap="">can update
</pre>
</blockquote>
<pre wrap=""><!---->
</pre>
<blockquote type="cite">
<pre wrap="">our packages to use versions that might actually have a chance
</pre>
</blockquote>
<pre wrap=""><!---->
</pre>
<blockquote type="cite">
<pre wrap="">of
</pre>
</blockquote>
<pre wrap=""><!---->
</pre>
<blockquote type="cite">
<pre wrap="">working
</pre>
</blockquote>
<pre wrap=""><!---->c) In some cases, they might not even be needed with Asterisk
</pre>
<blockquote type="cite">
<pre wrap="">1.4
</pre>
</blockquote>
<pre wrap=""><!---->
</pre>
<blockquote type="cite">
<pre wrap="">(like app_conference)
</pre>
</blockquote>
<pre wrap=""><!---->
</pre>
<blockquote type="cite">
<pre wrap="">-------------------------------------------------------------------------
</pre>
</blockquote>
<pre wrap=""><!---->This
</pre>
<blockquote type="cite">
<pre wrap="">SF.net email is sponsored by DB2 Express
</pre>
</blockquote>
<pre wrap=""><!---->Download DB2 Express C - the FREE
</pre>
<blockquote type="cite">
<pre wrap="">version of DB2 express and take
</pre>
</blockquote>
<pre wrap=""><!---->control of your XML. No limits. Just data.
</pre>
<blockquote type="cite">
<pre wrap="">Click to get it
now.
</pre>
</blockquote>
<pre wrap=""><!----><a class="moz-txt-link-freetext" href="http://sourceforge.net/powerbar/db2/">http://sourceforge.net/powerbar/db2/</a>
_______________________________________________
Astlinux-users
</pre>
<blockquote type="cite">
<pre wrap="">mailing
list
</pre>
</blockquote>
<pre wrap=""><!----><a class="moz-txt-link-abbreviated" href="mailto:Ast...@li...">Ast...@li...</a>
<a class="moz-txt-link-freetext" href="https://lists.sourceforge.net/lists/listinfo/astlinux-users">https://lists.sourceforge.net/lists/listinfo/astlinux-users</a>
Donations
</pre>
<blockquote type="cite">
<pre wrap="">to support AstLinux are graciously accepted via PayPal
to
</pre>
</blockquote>
<pre wrap=""><!----><a class="moz-txt-link-abbreviated" href="mailto:pa...@kr...">pa...@kr...</a>.
</pre>
<pre wrap=""><!---->
</pre>
<blockquote type="cite">
<pre wrap="">-------------------------------------------------------------------------
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.
<a class="moz-txt-link-freetext" href="http://sourceforge.net/powerbar/db2/">http://sourceforge.net/powerbar/db2/</a>
_______________________________________________
Astlinux-users mailing list
<a class="moz-txt-link-abbreviated" href="mailto:Ast...@li...">Ast...@li...</a>
<a class="moz-txt-link-freetext" href="https://lists.sourceforge.net/lists/listinfo/astlinux-users">https://lists.sourceforge.net/lists/listinfo/astlinux-users</a>
Donations to support AstLinux are graciously accepted via PayPal to
<a class="moz-txt-link-abbreviated" href="mailto:pa...@kr...">pa...@kr...</a>.
</pre>
</blockquote>
<pre wrap=""><!---->
</pre>
</blockquote>
</body>
</html>
|
×
Want the latest updates on software, tech news, and AI?
Get latest updates about software, tech news, and AI from SourceForge directly in your inbox once a month.
Thanks for helping keep SourceForge clean.
X