|Summary:||ASTERISK-12078: Configure function considers openh323 invalid while version 1.6 considers it valid|
|Reporter:||Private Name (falves11)||Labels:|
|Date Opened:||2008-05-24 02:32:03||Date Closed:||2011-06-07 14:03:05|
|Environment:||Attachments:||( 0) conf16.log|
( 1) configtrunk.log
|Description:||I installed pwlib 1.12 and openh323 19.1, both the latest. I installed in one directory asterisk-1.6.0-beta9 and in other the latest Trunk. Then I did a ./configure in both and capture the results to a file. Then I did a diff on both files, and the result is this:|
(files are at /tmp/conf.txt and /usr/src/conf.txt) diff /tmp/conf.txt /usr/src/conf.txt
> checking for compiler 'attribute sentinel' support... yes
< checking for pri_new_bri in -lpri... yes < checking libpri.h usability... yes < checking libpri.h presence... yes < checking for libpri.h... yes
> checking for pri_get_version in -lpri... no
< checking OpenH323 installation validity... yes
> checking OpenH323 installation validity... no
< config.status: include/asterisk/autoconfig.h is unchanged
The result: Asterisk 1.6 compiles h323 while Trunk does not.
****** ADDITIONAL INFORMATION ******
As you can see, the Trunk version shows this:
"checking OpenH323 installation validity... no"
while the 1.6 version says "yes". I think that there is some bug in the Trunk's ./configure because Trunk should allow the same version or higher of pwlib and openh323 as Asterisk 1.6. I need the latest version of both. H323 is a very important part of the business.
|Comments:||By: Joshua C. Colp (jcolp) 2008-05-27 08:36:34|
Can you please attach the output of:
ls -al /usr/local/lib64/libh323*
By: Private Name (falves11) 2008-05-27 09:13:11
ls -al /usr/local/lib64/libh323*
ls: /usr/local/lib64/libh323*: No such file or directory
By: Private Name (falves11) 2008-05-27 09:48:24
The bug system is buggy. I am trying to upload a "configure" file and it blows up with application error 401. This is using Firefox in Linux. The key point is: Maxim Sobolev actually had to change the configure file in Asterisk 1.6 Beta 9 to make it work. So it was patched and I did not know. Maybe somebody should ask him for the changes so Asterisk Trunk would be able to use the latest verson of pwlib and openh323. He is active in the developers list. Many people often ask me why do I use Trunk in production and not something else. Because of the ODBC enhancements. I use func_odbc and cdr_odbc, so having only one network call versus three is vital, when you have 20-30 calls per second. The only carrier-strength version of Asterisk is Trunk. If I am wrong please somebody clarify it.
By: Joshua C. Colp (jcolp) 2008-05-27 10:46:58
It does not allow you to attach large files such as a generated configure script, and we would not be able to use it anyway. We can only accept configure.ac changes.
By: Sergey Tamkovich (sergee) 2008-05-29 02:34:27
falves11, It doesn't seems like a bug. More likely it is a problem with your build env.
Please, answer the following questions:
1. Are you trying to build asterisk trunk and 1.6.0 on the same server?
2. Are you using the same build of openh323 each time?
3. Please, show us the output of `find / -name "libh323_linux*" -ls`
Thanks in advance.
By: Private Name (falves11) 2008-05-29 05:22:00
The answer is yes. Same server, same version of pwlib and openh323. I hired Maxim Sobolev to do this. He toldme that he modified the configure script for 1.6 beta to make it work, and in fact Asterisk Trunk does not compile H323 while 1.6 does. That is why I open the case. I am now traveling in the former USSR and I am working off my Blackberry. So I cannot do more than this and answer emails, which is easier. My email is firstname.lastname@example.org.Maxim should be able to tell the story better than I. He is on the developers list
By: Sergey Tamkovich (sergee) 2008-05-29 06:09:45
In fact, configure script from trunk and 1.6.0 doesn't differ in h323 part.
By: Private Name (falves11) 2008-06-08 12:29:42
Please close the case. I figure it out. The problem is on installing pwlib and openh323, after that works, we need to do this:
ln -s /usr/src/openh323/lib/libh323_r.so /usr/local/lib/libh323_linux_x86_64_r.so
unless this step is taken, Asterisk will not compile chan_h323.so. Unfortunately, the make for openh323 does not export the sybmoling link or copy the library.