Hey list !
exist some trouble with php and amd64 ? (last php from ports)
[root@gringo] ~# pkg_info | grep php5-5
php5-5.3.6_1PHP Scripting Language
[root@gringo] ~# php -v
Segmentation fault
[root@gringo] ~# php-fpm -h
Segmentation fault
[root@gringo] ~# which php-fpm
Hello,
Just upgraded to php5-5.3.6_1 and the SQLITE 3 extensions
(php5-pdo_sqlite-5.3.6_1 and php5-sqlite3-5.3.6_1) are causing PHP to core
dump.
I commented them from /usr/local/etc/php/extensions.ini and the segmentation
faults disappear.
Thanks.
--
Attos Janus
I found that the SQLite 3 extensions are causing some issues.
Comment out the SQLite 3 extensions in /usr/loca/etc/php/extensions.ini if
you can live without them.
That did the trick for me.
Re-installing SQLite or the extensions did not fix anything.
On Tue, Jun 28, 2011 at 12:53 PM, Luiz
On 2011-06-28 18:53, Luiz Gustavo S. Costa wrote:
Hey list !
exist some trouble with php and amd64 ? (last php from ports)
[root@gringo] ~# pkg_info | grep php5-5
php5-5.3.6_1PHP Scripting Language
[root@gringo] ~# php -v
Segmentation fault
[root@gringo] ~# php-fpm -h
not working ...
[root@gringo] ~# cd /tmp/
[root@gringo] /tmp# fetch
http://people.freebsd.org/~ohauer/scripts/fixphpextorder.sh
fixphpextorder.sh 100% of 2661 B 15 MBps
[root@gringo] /tmp# sh fixphpextorder.sh
==
New INI is saved as
Hi,
On Sun, Jun 26, 2011 at 10:47 PM, Robert Huff roberth...@rcn.com wrote:
There was a problem with the latest update - maintainer missed
a patch file.
It has been corrected; please update and try again. If failure
persists, please talk to the maintainer.
It seems the
On 28.06.11 19:49, Olli Hauer wrote:
On 2011-06-28 18:53, Luiz Gustavo S. Costa wrote:
Hey list !
exist some trouble with php and amd64 ? (last php from ports)
[root@gringo] ~# pkg_info | grep php5-5
php5-5.3.6_1PHP Scripting Language
[root@gringo] ~# php -v
Segmentation fault
From: Attos attos.ja...@gmail.com
Hello,
Just upgraded to php5-5.3.6_1 and the SQLITE 3 extensions
(php5-pdo_sqlite-5.3.6_1 and php5-sqlite3-5.3.6_1) are causing PHP to core
dump.
I commented them from /usr/local/etc/php/extensions.ini and the segmentation
faults disappear.
I've always
I ran the script to recreate the extensions.ini but after adding the
following extension:
extension=sqlite3.so
php seg faults again
On Tue, Jun 28, 2011 at 2:10 PM, Florian Smeets f...@freebsd.org wrote:
On 28.06.11 19:49, Olli Hauer wrote:
On 2011-06-28 18:53, Luiz Gustavo S. Costa wrote:
On 2011-06-28 20:10, Florian Smeets wrote:
On 28.06.11 19:49, Olli Hauer wrote:
On 2011-06-28 18:53, Luiz Gustavo S. Costa wrote:
Hey list !
exist some trouble with php and amd64 ? (last php from ports)
[root@gringo] ~# pkg_info | grep php5-5
php5-5.3.6_1PHP Scripting Language
Not an empty php.ini, but an empty /usr/local/etc/php/extensions.ini
That's how I found about SQLite. Commented out all the extensions and the
un-commented one-by-one.
On Tue, Jun 28, 2011 at 2:29 PM, Olli Hauer oha...@freebsd.org wrote:
On 2011-06-28 20:10, Florian Smeets wrote:
On 28.06.11
Sorry for hijacking this thread, and cross posting.
On 2011-06-26 03:07, Gabor PALI wrote:
With Clang, an error occurs in one of the configure scripts, because
Clang warns about unused command-line arguments, and the configure
script assumes that to be a compiler error. You can deal with
On 2011-06-28 20:46, Niclas Zeising wrote:
Sorry for hijacking this thread, and cross posting.
On 2011-06-26 03:07, Gabor PALI wrote:
With Clang, an error occurs in one of the configure scripts, because
Clang warns about unused command-line arguments, and the configure
script assumes that
It seems the problem is still there:
tingo@kg-v2$ uname -a
FreeBSD kg-v2.kg4.no 8.1-STABLE FreeBSD 8.1-STABLE #3: Thu Sep 16
22:18:48 CEST 2010 r...@kg-v2.kg4.no:/usr/obj/usr/src/sys/GENERIC
amd64
Last part of build output:
CClibavcodec/vp5.o
CClibavcodec/vp56.o
{standard
Rebuild with threads enabled, will likely fix all your problems.
Why the default is off I don't know but it conflicts with a
number of the main libs used e.g. libxml hence causing segvs
just as you described.
Regards
Steve
- Original Message -
From: Luiz Gustavo S. Costa
Niclas Zeising zeis...@daemonic.se writes:
Sorry for hijacking this thread, and cross posting.
On 2011-06-26 03:07, Gabor PALI wrote:
With Clang, an error occurs in one of the configure scripts, because
Clang warns about unused command-line arguments, and the configure
script assumes
On 2011-06-28 21:19, Pan Tsu wrote:
Niclas Zeising zeis...@daemonic.se writes:
Sorry for hijacking this thread, and cross posting.
On 2011-06-26 03:07, Gabor PALI wrote:
With Clang, an error occurs in one of the configure scripts, because
Clang warns about unused command-line arguments,
On 6/28/11 4:06 PM, Niclas Zeising wrote:
On 2011-06-28 21:19, Pan Tsu wrote:
Niclas Zeisingzeis...@daemonic.se writes:
Sorry for hijacking this thread, and cross posting.
On 2011-06-26 03:07, Gabor PALI wrote:
With Clang, an error occurs in one of the configure scripts, because
Clang
Hi maybe someone has a hint for an issue with autotools.
On a amd64 system I run into the following issue on a port.
5 times $ make clean configure
= 3 times fail
= 2 times success
The interesting part between fail and success on the system self
and in tinderbox.
---
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 06/28/11 19:55, Olli Hauer wrote:
Hi Steve,
from my perspective everything is fine for the change.
Maybe Philip has some additional tasks/time plannings?
If not I will request an exp-run.
I've placed a small overview of the last issues
Am 29.06.2011 00:17, schrieb Olli Hauer:
Hi maybe someone has a hint for an issue with autotools.
On a amd64 system I run into the following issue on a port.
5 times $ make clean configure
= 3 times fail
= 2 times success
The interesting part between fail and success on the system
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 2011-06-28 03:40, Steve Wills wrote:
On 03/17/11 22:35, Philip M. Gollucci wrote:
All,
apache@ has been working diligently for the last 2yrs to realize
www/apache22 as the default. Now, we are at last nearing completion. We
look to pull the
On 29/06/2011 02:13, Steve Wills wrote:
FWIW, www/p5-RTx-Statistics port can probably be removed, similar
functionality is included in RT itself now and has been for a while:
http://lists.bestpractical.com/pipermail/rt-users/2007-October/048538.html
and I recall reading somewhere else
23 matches
Mail list logo
