[asterisk-dev] H323 64 bit Nightmare

Venefax venefax at gmail.com
Sat May 24 02:22:15 CDT 2008

Dear Maxim
This is what happens. The asterisk 1.6 considers the openh323 installation
validity ok, while the Asterisk trunk does not. I did a ./configure in both
and captured the outcome to files, and made a diff. I got 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

Do you have any idea what is happening? I need to compile Trunk. There must
be a way to make the version that you installed work with Trunk. I want to
use it in production.
-----Original Message-----
From: asterisk-dev-bounces at lists.digium.com
[mailto:asterisk-dev-bounces at lists.digium.com] On Behalf Of Maxim Sobolev
Sent: Friday, May 23, 2008 5:48 PM
To: Asterisk Developers Mailing List
Subject: Re: [asterisk-dev] H323 64 bit Nightmare

Patrick wrote:
> On Thu, 2008-05-22 at 12:55 -0400, Venefax wrote:
>> I downloaded the latest version as instructed and I get this error after
>> issue a 
>> ./configure
>> make clean opt
>> o  /usr/src/ptlib_v1_12_0/lib/obj_linux_x86_64_r/collect.o
>> /usr/src/ptlib_v1_12_0/lib/obj_linux_x86_64_r/contain.o
>> /usr/src/ptlib_v1_12_0/lib/obj_linux_x86_64_r/object.o  -lldap -llber
>> -lldap_r  -lpthread -lsasl2 -lssl -lcrypto -lexpat -lodbc -lresolv
>> /usr/bin/ld:
>> .a(res_comp.o): relocation R_X86_64_32 against `a local symbol' can not
>> used when making a shared object; recompile with -fPIC
>                                     ^^^^^^^^^^^^^^^^^^^^
> Did you add -fPIC to the CFLAGS in the Makefile as suggested?

In this particular case the issue had nothing to do with 64-bitness or 
with -fPIC. It is just that for some unknown to me reason the links to 
some shared libraries in /usr/lib64 were pointing to the wrong places, 
so that linker had no choice but to pick up static library instead.

Maksym Sobolyev
Sippy Software, Inc.
Internet Telephony (VoIP) Experts
T/F: +1-646-651-1110
Web: http://www.sippysoft.com

--Bandwidth and Colocation Provided by http://www.api-digital.com--

asterisk-dev mailing list
To UNSUBSCRIBE or update options visit:

More information about the asterisk-dev mailing list