mailing list of musl libc
 help / color / mirror / code / Atom feed
From: Pirmin Walthert <pirmin.walthert@wwcom.ch>
To: musl@lists.openwall.com
Subject: Re: musl libc dlopen does not return in asterisk.
Date: Wed, 30 Aug 2017 11:54:15 +0200	[thread overview]
Message-ID: <1504086855.17499.68.camel@wwcom.ch> (raw)
In-Reply-To: <7a54ad1d-edcd-1dea-9a19-5d01f4c89d02@rvq.fr>

Hi harvé

I  had a similar problem (did not yet have time to have a closer look)
when using musl-git with Asterisk 13.17. The following commit seemed to
have broken compatibility (at least for me): http://git.musl-libc.org/c
git/musl/commit/?id=6476b8135760659b25c93ff9308425ca98a9e777

Using the latest version of dynlink.c BEFORE this commit worked for me,
maybe it's worth a try? (1.1.16 had a different module loading issue
with my Asterisk installation that was fixed with
27b3fd68f67b674440d21ea7ca5cf918d2e1559f).

Best regards,

Pirmin

Am Mittwoch, den 30.08.2017, 11:45 +0200 schrieb Hervé Quillévéré at
Home:
> Hi all
> 
> musl libc dlopen does not return in asterisk.
> 
> Void linux musl libc arm (cubieboard2) on banana pi.
> linux-4.12.8  sunxi_defconfig
> 
> asterisk-14.6.0
> ./configure
> make
> sudo make install
> sudo make basic-pbx
> 
> run as root
> asterisk -vvvc
> 
> This command should return with a prompt and
> blocks in load_dynamic_module() in main/loader.c when calling
> dlopen().
> 
> As work has been done recently on dlopen, I tried with musl libc
> dowloaded
> and compiled from git with the same result.
> 
> Replacing Void Linux musl with Void Linux glibc works.
> 
> Running Void Linux x86_64 musl and asterisk does not work and produce
> the same effect.
> 
> Best Regards
> 
> hervé
> 
> 


      reply	other threads:[~2017-08-30  9:54 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-08-30  9:45 Hervé Quillévéré at Home
2017-08-30  9:54 ` Pirmin Walthert [this message]

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=1504086855.17499.68.camel@wwcom.ch \
    --to=pirmin.walthert@wwcom.ch \
    --cc=musl@lists.openwall.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
Code repositories for project(s) associated with this public inbox

	https://git.vuxu.org/mirror/musl/

This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).