[asterisk-dev] libasteriskssl.so.1

Paul Belanger paul.belanger at polybeacon.com
Wed Aug 29 16:21:45 CDT 2012


On 12-08-29 05:04 PM, Matthew Jordan wrote:
>
>
> ----- Original Message -----
>> From: "Paul Belanger" <paul.belanger at polybeacon.com>
>> To: asterisk-dev at lists.digium.com
>> Sent: Wednesday, August 29, 2012 3:50:04 PM
>> Subject: Re: [asterisk-dev] libasteriskssl.so.1
>>
>> On 12-08-29 01:59 PM, Russell Bryant wrote:
>>> On Wed, Aug 29, 2012 at 1:46 PM, Giuseppe Longo
>>>
>>> I've seen another cause for this failure, as well.  If you're
>>> running
>>> on 64-bit Fedora or RHEL 6 (and maybe others, but at least those),
>>> libasteriskssl should be installed into /usr/lib64.  If you're
>>> installing from source, Asterisk will install it to /usr/lib/ by
>>> default, which is wrong.  To fix it, you must add an option when
>>> running configure:
>>>
>>> $ ./configure --libdir=/usr/lib64
>>>
>> Do we not have the ability to detect 64-bit with our configure script
>> and attempt to choose the right directory?
>>
>> Otherwise I'm sure we will have to explain this 100 time on the
>> asterisk-users mailing list.
>>
>
> Except that not every 64-bit distro puts its shared object libraries
> in /usr/lib64.
>
> We ran into this problem with libpri as well.  Can you modify the configure
> script sufficiently that you can solve it for every distro?  Maybe.  Not to
> generalize too far here, but there have been a lot of corner cases reported
> in JIRA against configure options that failed to account for interesting
> deployment scenarios.  It has started to feel as if attempting to solve every
> configure scenario for end users hasn't worked out well.
>
> Of course, Fedora isn't exactly a corner case.
>
Agreed. Tilghman's comment is spot on.

-- 
Paul Belanger | PolyBeacon, Inc.
Jabber: paul.belanger at polybeacon.com | IRC: pabelanger (Freenode)
Github: https://github.com/pabelanger | Twitter: 
https://twitter.com/pabelanger



More information about the asterisk-dev mailing list