Newsgroups: php.internals
Path: news.php.net
Xref: news.php.net php.internals:99048
Mailing-List: contact internals-help@lists.php.net; run by ezmlm
Received-SPF: softfail (pb1.pair.com: domain golemon.com does not designate 74.125.82.46 as permitted sender)
MIME-Version: 1.0
Sender: php@golemon.com
In-Reply-To: <46d32889-2068-9ccb-85b2-e4cffc7db322@rhsoft.net>
References: <MWHPR02MB247716356A3E07DB102DE761BFE10@MWHPR02MB2477.namprd02.prod.outlook.com>
 <46d32889-2068-9ccb-85b2-e4cffc7db322@rhsoft.net>
Date: Mon, 15 May 2017 10:30:01 -0500
Message-ID: <CAESVnVp5iesYE7__ZS7xoHnVW0y5WEEeY0iwdZTVSiGtH+35xg@mail.gmail.com>
To: "lists@rhsoft.net" <lists@rhsoft.net>
Cc: PHP internals <internals@lists.php.net>
Content-Type: text/plain; charset="UTF-8"
Subject: Re: [PHP-DEV] HYBRID VM
From: pollita@php.net (Sara Golemon)

On Mon, May 15, 2017 at 9:51 AM, lists@rhsoft.net <lists@rhsoft.net> wrote:
> Am 15.05.2017 um 16:43 schrieb Dmitry Stogov:
>>
>> php zend_vm_gen.php --with-vm-kind=HYBRID
>>
> shouldn't that be a ./configure option?
> calls like "php zend_vm_gen.php" are not self contained in a rpmbuild
>
atm, no.  The VM gen is (and has been since 5.0) a development time
generator which is checked into GIT (because it requires PHP to be
built to run, and must run before PHP is built).  rpmbuilders
(probably) never need worry about selecting alternate VMs, but if they
do there must be a means to patch codebases before building (distros
do this routinely), hooking into that should be a possibility.

That said, the only argument against adding it as a ./configure option
is that it's a bootstrap step (as mentioned above).  I suppose we
could use the checked in version of the VM when the option isn't
specified, and error if one tried to specify the option without having
a PHP version already around.

That's orthogonal to this thread, however.

Dmitry; You've got my thumbs up. No need for an RFC for something
purely internal like this.

-Sara