Newsgroups: php.internals
Path: news.php.net
Xref: news.php.net php.internals:4135
Return-Path: <jay@php.net>
Mailing-List: contact internals-help@lists.php.net; run by ezmlm
Delivered-To: mailing list internals@lists.php.net
Received: (qmail 96114 invoked by uid 1010); 22 Aug 2003 20:37:00 -0000
Received: (qmail 96088 invoked by uid 1007); 22 Aug 2003 20:37:00 -0000
Message-ID: <20030822203700.96087.qmail@pb1.pair.com>
To: internals@lists.php.net
Reply-To: jay@php.net
Mail-Copies-To: jay@php.net
Date: Fri, 22 Aug 2003 16:36:59 -0400
References: <4719.192.168.1.103.1061332762.squirrel@192.168.1.2> <20030820145716.2919.qmail@pb1.pair.com> <4043.192.168.1.253.1061584115.squirrel@192.168.1.2>
Lines: 18
User-Agent: KNode/0.7.2
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7Bit
X-Posted-By: 216.94.11.234
Subject: Re: [PHP-DEV] Re: Support for C++ extension in UNIX builds
From: jay@php.net (Jay Smith)

Mark Spruiell wrote:
> 
> Unlike GCC, Sun's C and C++ compilers are independent entities, therefore
> you can't link a C++ program or shared library when the C compiler is
> driving the linker. It's also not possible to compile PHP's C code with
> Sun's C++ compiler.
> 
> I guess we're a little spoiled by GCC. :)
> 
> - Mark
> 

I suppose so. I rarely use Sun's compiler so I won't hazard a guess as to
what's going on here. I guess you don't have access to gcc on that machine,
eh?

J