Hi,

Please see below.

May the source be with you,
Best regards,
Jess Portnoy



jvlad wrote:
"Jess Portnoy" <[email protected]> wrote in message news:[email protected]...
Apple ships their MAC OS with GCC that is capable of building universal binaries. Most MAC users expect packages to be built universal. Trust me, I also hate it but its true... If what you want is just to ensure the extensions are built for the same architecture as the PHP core, this I can understand, I'm just saying you need to take multiple archs bundled together under consideration. Also, I don't know if deciding for the dynamic loader if something can be loaded is so wise, if it can great, if not, it will yell at you anyhow..

May the source be with you,
Best regards,
Jess Portnoy

Jess,
Honestly, I see no problem with universal binaries. After all
they are not that "universal" at all.
Perhaps you missed another reply where I asked - if you have
4 binaries in one file, why don't you have 4 id strings for them?
The problem I see [and it can certainly be that we just don't understand each other's intentions :)], is this: If the PHP Core [the Apache module, CLI/CGI binary, etc] is built for instance as a 4 way universal binary [32bit and 64bit, Intel and PPC], the machine itself is, lets say, a 64bit Intel machine and the extension being examined is built 2 ways, say, 32bit and 64bit, how do you suggest we compare them? I mean, the extension should be able to load fine even though its just 2 way because we are NOT running PPC here..
and yes, many companies that provide their php extensions in pre-compiled form like Zend, ionCube, and many others are interested in a clear way on how to detect whether installed php is supported and what module among hunderd others to pick and install. So, you usee it's not a way to dictate
the loader what to load. It's  a way for installer to be wise enough.
The installer really has nothing to do here the way I see it, a person may later take an extension built by some other party, this extension which technically could load just fine, will be rejected due the Engine test, as is the situation today when compiling the extension with a VC version different than core was compiled with. If you're just talking about warning [not the case these days with the compiler ID check, then perhaps].
-jvlad



--
PHP Internals - PHP Runtime Development Mailing List
To unsubscribe, visit: http://www.php.net/unsub.php

Reply via email to