On 23.06.2009, at 08:15, jvlad wrote:
1. you're wrong, PHP does not depend on system-wide installed
pear, it
will simply use it if present
2. nothing is missing. see http://pear.php.net/PHP_Archive
If installed, phar.phar will function (partially) without the phar
extension being
1. you're wrong, PHP does not depend on system-wide installed pear, it
will simply use it if present
2. nothing is missing. see http://pear.php.net/PHP_Archive
If installed, phar.phar will function (partially) without the phar
extension being present.
In other words, not a
In other words, I see two bugs there:
1. PHP depends on the system-wide installed pear and tries to run it.
2. One or many files are missed in the package producing the Archive.php
class file not found error.
1. you're wrong, PHP does not depend on system-wide installed pear, it
will simply
Did you hear about crashes under Solaris and MacOSX, and compiler
failures
under all *BSD systems?
They were posted against RC3 and the problems are still the same in RC4.
We fixed several compile failures recently (both FreeBSD related and
GCC2), it probably didn't make it into RC4
jvlad wrote:
Did you hear about crashes under Solaris and MacOSX, and compiler
failures
under all *BSD systems?
They were posted against RC3 and the problems are still the same in RC4.
We fixed several compile failures recently (both FreeBSD related and
GCC2), it probably didn't make it
As of php5.3-200906221030, the problem under *BSD platforms that I'm
talking
about is still the same.
I see no compile failure bug reports against FreeBSD in the bugtracker...
I successfully built a snapshot on 4.11-STABLE FreeBSD (gcc 2.95.4)
3hours ago, you'll have to be slightly more
2009/6/23 jvlad d...@yandex.ru:
As of php5.3-200906221030, the problem under *BSD platforms that I'm
talking
about is still the same.
I see no compile failure bug reports against FreeBSD in the bugtracker...
I successfully built a snapshot on 4.11-STABLE FreeBSD (gcc 2.95.4)
3hours ago,
Generating phar.php
*** Error code 138
make: Fatal error: Command failed for target `ext/phar/phar.php'
next run of make install produces:
$ make install
Generating phar.phar
make: *** [ext/phar/phar.phar] Bus Error (core dumped)
System information, compiler, and trace would be a plus
Further investigation shown that compiler takes about 1GB(!) of memory
when
it compiles php5.3-200906221030/ext/fileinfo/libmagic/apprentice.c
On some systems this amount of memory is not available and may lead to
errors such as hangs or crashes.
Is it a known problem?
Is this requirement
jvlad wrote:
Further investigation shown that compiler takes about 1GB(!) of memory
when
it compiles php5.3-200906221030/ext/fileinfo/libmagic/apprentice.c
On some systems this amount of memory is not available and may lead to
errors such as hangs or crashes.
Is it a known problem?
Is
Further investigation shown that compiler takes about 1GB(!) of memory
when
it compiles php5.3-200906221030/ext/fileinfo/libmagic/apprentice.c
On some systems this amount of memory is not available and may lead to
errors such as hangs or crashes.
Is it a known problem?
Is this requirement
Hi
2009/6/23 jvlad d...@yandex.ru:
Now the problem is:
/bin/sh
/home/jvlad/php/php5.3-200906221030/libtool --silent --preserve-dup-deps
--mode=compile
gcc -Iext/phar/ -I/home/jvlad/php/php5.3-200906221030/ext/phar/
-DPHP_ATOM_INC
-I/home/jvlad/php/php5.3-200906221030/include
Or it could be possibly fixed by including stdint.h, like
win32/php_stdin.h is included on Windows thrus no compilation error
here. Let me know if the following patch fixes your problem:
Index: php_spl.h
===
RCS file:
jvlad wrote:
Generating phar.php
*** Error code 138
make: Fatal error: Command failed for target `ext/phar/phar.php'
next run of make install produces:
$ make install
Generating phar.phar
make: *** [ext/phar/phar.phar] Bus Error (core dumped)
System information, compiler, and trace would
Hi,
I just ran a make install of PHP 5.3 on Solaris 32-bit:
cel...@t2000-010131:~/php5$ gcc -v
Reading specs from /usr/sfw/lib/gcc/sparc-sun-solaris2.11/3.4.3/specs
Configured with:
/gates/sfwnv/builds/sfwnv-gate/usr/src/cmd/gcc/gcc-3.4.3/configure
--prefix=/usr/sfw
jvlad wrote:
Hi,
I just ran a make install of PHP 5.3 on Solaris 32-bit:
cel...@t2000-010131:~/php5$ gcc -v
Reading specs from /usr/sfw/lib/gcc/sparc-sun-solaris2.11/3.4.3/specs
Configured with:
/gates/sfwnv/builds/sfwnv-gate/usr/src/cmd/gcc/gcc-3.4.3/configure
--prefix=/usr/sfw
can you run the custom gdb dumpbt so we can see which line of
install-pear-nozlib.phar is triggering the error?
(gdb) dump_bt executor_globals.current_execute_data
[0x00861cc0] ???
/export/home/jvlad/php/php5.3-200906221030/ext/phar/phar.php:10
--
PHP Internals - PHP Runtime Development
jvlad wrote:
can you run the custom gdb dumpbt so we can see which line of
install-pear-nozlib.phar is triggering the error?
(gdb) dump_bt executor_globals.current_execute_data
[0x00861cc0] ???
/export/home/jvlad/php/php5.3-200906221030/ext/phar/phar.php:10
Hi,
Thanks. The line in
Hi,
Thanks. The line in question is the first line of the generated
(non-phar) phar.php script which is the foreach line in:
?php
foreach (array(SPL, Reflection, Phar) as $ext) {
if (!extension_loaded($ext)) {
echo $argv[0] requires PHP extension $ext.\n
exit(1);
}
}
?
Could you
jvlad wrote:
Hi,
Thanks. The line in question is the first line of the generated
(non-phar) phar.php script which is the foreach line in:
?php
foreach (array(SPL, Reflection, Phar) as $ext) {
if (!extension_loaded($ext)) {
echo $argv[0] requires PHP extension $ext.\n
exit(1);
}
}
?
On Mon, Jun 22, 2009 at 07:53, jvladd...@yandex.ru wrote:
Did you hear about crashes under Solaris and MacOSX, and compiler failures
under all *BSD systems?
They were posted against RC3 and the problems are still the same in RC4.
We fixed several compile failures recently (both FreeBSD related
Did you hear about crashes under Solaris and MacOSX, and compiler
failures
under all *BSD systems?
They were posted against RC3 and the problems are still the same in RC4.
We fixed several compile failures recently (both FreeBSD related and
GCC2), it probably didn't make it into RC4
On Mon, Jun 22, 2009 at 13:40, jvladd...@yandex.ru wrote:
Did you hear about crashes under Solaris and MacOSX, and compiler
failures
under all *BSD systems?
They were posted against RC3 and the problems are still the same in RC4.
We fixed several compile failures recently (both FreeBSD
jvlad d...@yandex.ru wrote in message
news:38.7a.20019.c9d6f...@pb1.pair.com...
Did you hear about crashes under Solaris and MacOSX, and compiler
failures
under all *BSD systems?
They were posted against RC3 and the problems are still the same in RC4.
We fixed several compile failures
Did you hear about crashes under Solaris and MacOSX, and compiler
failures
under all *BSD systems?
They were posted against RC3 and the problems are still the same in
RC4.
We fixed several compile failures recently (both FreeBSD related and
GCC2), it probably didn't make it into RC4
Did you hear about crashes under Solaris and MacOSX, and compiler
failures
under all *BSD systems?
They were posted against RC3 and the problems are still the same in
RC4.
We fixed several compile failures recently (both FreeBSD related and
GCC2), it probably didn't make it into RC4
Did you hear about crashes under Solaris and MacOSX, and compiler
failures
under all *BSD systems?
They were posted against RC3 and the problems are still the same in
RC4.
We fixed several compile failures recently (both FreeBSD related and
GCC2), it probably didn't make it into RC4
Did you hear about crashes under Solaris and MacOSX, and compiler
failures
under all *BSD systems?
They were posted against RC3 and the problems are still the same in
RC4.
We fixed several compile failures recently (both FreeBSD related and
GCC2), it probably didn't make it into RC4
jvlad wrote:
Did you hear about crashes under Solaris and MacOSX, and compiler
failures
under all *BSD systems?
They were posted against RC3 and the problems are still the same in
RC4.
We fixed several compile failures recently (both FreeBSD related and
GCC2), it probably didn't make it
php5.3-200906221030 make produces suspecious output under FreeBSD
6/amd64:
Generating phar.php
Generating phar.phar
pear: not found
Pear package PHP_Archive or Archive.php class file not found.
This is not suspicious. It is
jvlad wrote:
php5.3-200906221030 make produces suspecious output under FreeBSD
6/amd64:
Generating phar.php
Generating phar.phar
pear: not found
Pear package PHP_Archive or Archive.php class file not found.
This is not
Greg Beaver wrote:
jvlad wrote:
php5.3-200906221030 make produces suspecious output under FreeBSD
6/amd64:
Generating phar.php
Generating phar.phar
pear: not found
Pear package PHP_Archive or Archive.php class file not found.
On Tue, Jun 23, 2009 at 12:39 AM, Christopher
Joneschristopher.jo...@oracle.com wrote:
Can the messages be enhanced e.g. explaining what will happen in these
cases? For example pear: not found. Using XXX instead would help
users for #1.
Agreed, I answered questions from many users already,
Hi,
It looks like nothing critical has popped up since RC4.
So it looks like we will be sending the final stable release to the
mirrors next Wednesday and announce the release on Thursday barring any
critical issues emerging in the next days. In the mean time test test
test. If issues
34 matches
Mail list logo
