Newsgroups: php.internals Path: news.php.net Xref: news.php.net php.internals:98401 Return-Path: Mailing-List: contact internals-help@lists.php.net; run by ezmlm Delivered-To: mailing list internals@lists.php.net Received: (qmail 96853 invoked from network); 4 Mar 2017 10:23:39 -0000 Received: from unknown (HELO lists.php.net) (127.0.0.1) by localhost with SMTP; 4 Mar 2017 10:23:39 -0000 Authentication-Results: pb1.pair.com header.from=derick@php.net; sender-id=unknown Authentication-Results: pb1.pair.com smtp.mail=derick@php.net; spf=unknown; sender-id=unknown Received-SPF: unknown (pb1.pair.com: domain php.net does not designate 82.113.146.227 as permitted sender) X-PHP-List-Original-Sender: derick@php.net X-Host-Fingerprint: 82.113.146.227 xdebug.org Received: from [82.113.146.227] ([82.113.146.227:60190] helo=xdebug.org) by pb1.pair.com (ecelerity 2.1.1.9-wez r(12769M)) with ESMTP id 1A/D0-10274-9A59AB85 for ; Sat, 04 Mar 2017 05:23:38 -0500 Received: from localhost (localhost [IPv6:::1]) by xdebug.org (Postfix) with ESMTPS id 31F9A10C0F6; Sat, 4 Mar 2017 10:23:34 +0000 (GMT) Date: Sat, 4 Mar 2017 10:23:33 +0000 (GMT) X-X-Sender: derick@singlemalt.home.derickrethans.nl To: Sara Golemon cc: PHP internals In-Reply-To: Message-ID: References: User-Agent: Alpine 2.20 (DEB 67 2015-01-07) MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Subject: Re: [PHP-DEV] [Request for Comment] Loading dynamic libraries with cross dependencies. From: derick@php.net (Derick Rethans) On Fri, 3 Mar 2017, Sara Golemon wrote: > On Fri, Mar 3, 2017 at 5:47 AM, Derick Rethans wrote: > >> The average PHP extension is dependent only on the PHP runtime it was > >> built for and probably one or more 3rd party libraries. However, a > >> special class of extensions (such as PDO drivers and much of the XML > >> family) have dependencies on other PHP extensions which may (or may > >> not) be preset at the time they are loaded in via ini settings and/or > >> dl(). > > > > See also: > > https://derickrethans.nl/undefined-symbol.html > > > Exactly! The same underlying issue at work. > > Would I be correct in assuming there's a desire to resolve this issue? > Or are we considering "know your dependencies and configure for them" > to be enough? Getting this addressed would certainly be great. For the MongoDB extension we've worked around it so that we can at least show a reasonable error message though. cheers, Derick