Newsgroups: php.internals
Path: news.php.net
Xref: news.php.net php.internals:84957
Mailing-List: contact internals-help@lists.php.net; run by ezmlm
Received-SPF: pass (pb1.pair.com: domain gmail.com designates 209.85.192.41 as permitted sender)
MIME-Version: 1.0
In-Reply-To: <5F85ABDD-40BB-4C72-88C1-9F5599A78069@php.net>
References: <55059866.8030607@php.net>
	<5505A6E4.4080707@php.net>
	<5F85ABDD-40BB-4C72-88C1-9F5599A78069@php.net>
Date: Mon, 16 Mar 2015 11:07:59 +1100
Message-ID: <CAEZPtU4Gr5JxQHnMomZ+d6b0FCw8M=DV66Y9u1AVE0hhWTwkwA@mail.gmail.com>
To: Michael Wallner <mike@php.net>
Cc: PHP internals <internals@lists.php.net>
Content-Type: multipart/alternative; boundary=001a1140054297d5bc05115ca45a
Subject: Re: [PHP-DEV] Minimum version of GCC required to build PHP
From: pierre.php@gmail.com (Pierre Joye)

--001a1140054297d5bc05115ca45a
Content-Type: text/plain; charset=UTF-8

On Mar 16, 2015 2:41 AM, "Michael Wallner" <mike@php.net> wrote:
>
>
> > On 15 03 2015, at 16:36, Sebastian Bergmann <sebastian@php.net> wrote:
> >
> > Am 15.03.2015 um 15:34 schrieb Sebastian Bergmann:
> >> I am asking because using GCC 2.95.3 and GCC 3.4.0 I get errors related
> >> to the usage of intptr_t (see http://pastebin.com/9Gn0AAXA).
> >
> > Over in Room 11, Michael just pointed out that this could be related
> > to php_stdint.h.
>
> Yes, we could probably just add a check whether intptr_t is defined and
if not do so according to the bit width of the platform.

I remember some bugs affecting php with 2.95.x, I would be careful before
using it. We may as well ask for 3.x with 7+, we may have discussed that
for 5.5 or 5.6, if I am not mistaken.

--001a1140054297d5bc05115ca45a--