>> 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
Hi,
Please see below.
May the source be with you,
Best regards,
Jess Portnoy
jvlad wrote:
"Jess Portnoy" wrote in message
news:4b127c03.1080...@zend.com...
Apple ships their MAC OS with GCC that is capable of building universal
binaries.
Most MAC users expect packages to be built univer
"Jess Portnoy" wrote in message
news:4b127c03.1080...@zend.com...
> 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 ex
>
>> just displaying the gathered arch info I can see no harm in though...
>
> that's what we do.
>
hmm, 32bit php binary v5.3.1 under W7-64bit displays
Windows NT MyHostName 6.1 build 7600 ((null)) i586
If I needed to know current system, I'd prefer to see
SYSTEMNAME,VERSION,HOST,CPU
for example:
BTW, Macports also support building PHP in universal mode.
May the source be with you,
Best regards,
Jess Portnoy
Jess Portnoy wrote:
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
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 under
"Jess Portnoy" wrote in message
news:4b125d15.4040...@zend.com...
> Hello,
>
> Have you considered cases such as universal MAC/Darwin builds? The
> universal build method [used only by Apple but still, many PHP developers
> do run MAC] means you have several archs bundled together in the same
"Jess Portnoy" wrote in message
news:4b1266e0.7010...@zend.com...
> Perhaps it would be wise to display both the build arch and the current
> arch on which its running?
> I used the Darwin/MAC universal build example before but even on Windows
> and *nix as well when you think about it, one ca
On Sun, Nov 29, 2009 at 1:19 PM, Jess Portnoy wrote:
> just displaying the gathered arch info I can see no harm in though...
that's what we do.
Cheers,
--
Pierre
http://blog.thepimp.net | http://www.libgd.org
--
PHP Internals - PHP Runtime Development Mailing List
To unsubscribe, visit: htt
Perhaps it would be wise to display both the build arch and the current
arch on which its running?
I used the Darwin/MAC universal build example before but even on Windows
and *nix as well when you think about it, one can run a 32bit binary on
a 64bit OS, usually provided the stack below [Apache
hi,
This info is available in phpinfo on windows and I would like to add
it in the "php -v" output as well. I'm not sure how we can safely rely
on this info on other platforms but that's definitively something we
should try to do.
Cheers,
On Sun, Nov 29, 2009 at 11:29 AM, jvlad wrote:
> Hi all,
And, though I'm sure everyone on the list is capable of finding this URL
on their own, a short explanation:
http://en.wikipedia.org/wiki/Universal_binary
May the source be with you,
Best regards,
Jess Portnoy
Jess Portnoy wrote:
Hello,
Have you considered cases such as universal MAC/Darwin
Hello,
Have you considered cases such as universal MAC/Darwin builds? The
universal build method [used only by Apple but still, many PHP
developers do run MAC] means you have several archs bundled together in
the same binary, and, a binary built 2 ways [i386 and PPC or i386 and
x86_64 or even
13 matches
Mail list logo
