FreeBSD Port: php5-mhash-5.2.11_1
Hey, I just updated ports on a few machines and the CLI version of php dumps its core rather than end nicely. The mhash module appears to be the trigger (an extensions.ini with only mhash causes failure, all others minus mhash: no failure). Same outcome on various machines, running 7.1 and 7.2, i386 and amd64. # php -v PHP 5.2.11 with Suhosin-Patch 0.9.7 (cli) (built: Oct 17 2009 11:08:05) Copyright (c) 1997-2009 The PHP Group Zend Engine v2.2.0, Copyright (c) 1998-2009 Zend Technologies with eAccelerator v0.9.5.3, Copyright (c) 2004-2006 eAccelerator, by eAccelerator Segmentation fault (core dumped) Note: the scripts seem to run, just dump rather than end nicely. I did not test the mhash function. -Simon Shapiro ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"
Re: FreeBSD Port: cfengine-2.2.7
On Jul 22, 2008, at 10:16 PM, Boris Samorodov wrote: On Tue, 22 Jul 2008 21:03:22 -0700 Simon Shapiro wrote: Hello there, it appears that an old(ish) bug has come back in the cfengine port? Its compiling with the oldest existing BDB version found on the system. Tested on both 7.0 and 6.3 with the same result. Configure says: ===> cfengine-2.2.7 depends on shared library: db-4.6.0 - found but then 4.0 is linked. I have found this to be perfectly repeatable, and reversable (if old versions are removed, it works with 4.6). let me know if i can be of further assistance, and thank you for your time, Current maintainer is rather unresponsive and Jo Rhett (CCed) is very active and responsive about this port. Jo, can you help here? Thanks! WBR -- Boris Samorodov (bsam) Research Engineer, http://www.ipt.ru Telephone & Internet SP FreeBSD committer, http://www.FreeBSD.org The Power To Serve Thank you Boris. Some more info from my digging... forgive my complete unfamiliarity, this is deeper than I usually venture into the workings of the ports tree. As far as I can tell, the ports tree makefile (ports/sysutils/ cfengine/Makefile) gets it right, it appears that environment variables passed to the cfengine configure script (ports/sysutils/ cfengine/work/cfengine-2.2.7/configure) are ignored. That is, cfengine seems to want the command line argument --with- berkleydb= and we seem to be passing the information as an environment variable, which quickly gets overwritten with the string 'default' The evidence being that the first place i see any reference to the *old* bdb, is when the cfengine package's configure script says "checking for BerkeleyDB location in default... Found header in /usr/ local/include/db4" -Simon Shapiro ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to "[EMAIL PROTECTED]"
FreeBSD Port: cfengine-2.2.7
Hello there, it appears that an old(ish) bug has come back in the cfengine port? Its compiling with the oldest existing BDB version found on the system. Tested on both 7.0 and 6.3 with the same result. Configure says: ===> cfengine-2.2.7 depends on shared library: db-4.6.0 - found but then 4.0 is linked. I have found this to be perfectly repeatable, and reversable (if old versions are removed, it works with 4.6). let me know if i can be of further assistance, and thank you for your time, Simon Shapiro ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to "[EMAIL PROTECTED]"
www/ismail port breaking make index
www/ismail fails during make index on FreeBSD 6.2, not 7.0 from what i can tell. Generating INDEX-6 - please wait.."Makefile", line 32: Could not find bsd.port.options.mk make: fatal errors encountered -- cannot continue ===> www/ismail failed *** Error code 1 Ports tree just updated from CVS, this appears to be a new bug introduced with the recent update of said port. -Simon Shapiro ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to "[EMAIL PROTECTED]"
