Newsgroups: php.internals Path: news.php.net Xref: news.php.net php.internals:4125 Return-Path: Mailing-List: contact internals-help@lists.php.net; run by ezmlm Delivered-To: mailing list internals@lists.php.net Received: (qmail 48758 invoked by uid 1010); 22 Aug 2003 10:08:06 -0000 Received: (qmail 48730 invoked from network); 22 Aug 2003 10:08:05 -0000 Received: from unknown (HELO codetop) (195.74.122.222) by pb1.pair.com with SMTP; 22 Aug 2003 10:08:05 -0000 Received: from gaz by codetop with local (Exim 3.36 #1 (Debian)) id 19q8nE-0000Oh-00 for ; Fri, 22 Aug 2003 11:05:16 +0100 To: internals@lists.php.net Date: Fri, 22 Aug 2003 11:05:15 +0100 User-Agent: KMail/1.5.3 MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Content-Disposition: inline Message-ID: <200308221105.16365.gareth@fission.org.uk> Sender: gareth ardron Subject: extensions in 4.3.x From: gareth@fission.org.uk (Gareth Ardron) I've got an extension which was written for 4.1/4.2, and everything worked great. I've just (by accident of me not paying attention to an apt-get dist-upgrade) upgraded to 4.3.2 and I can't get the extension to compile now. I keep getting bitching about unresolved symbols. Does anybody have any docs kicking around as to how the build process changed between 4.2.x and 4.3.x so that I can fix this extension up please? Also, as an interesting sidenote... The .so file that was compiled under 4.2.2 is fully useable under 4.3.2 as well for some reason. Not quite sure why though, I'd have assumed it'd need to be recompiled. Cheers, -- Gareth Ardron