Re: PHP 5.2.1 and the hard time with vbulletin 3.6.4 (solved)
Hi Abdullah! On Mon, 12 Mar 2007, Abdullah Ibn Hamad Al-Marri wrote: On 2/27/07, Abdullah Ibn Hamad Al-Marri [EMAIL PROTECTED] wrote: On 2/26/07, Joe Auty [EMAIL PROTECTED] wrote: -BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Have you recompiled all PHP extensions too? I believe the php5-pcre extension might handle perl regular expressions (preg_replace) in PHP. Yes I did portupgrade -f php* There is a thread about it in vbulletin http://www.vbulletin.com/forum/showthread.php?p=1312516#post1312516 -- Regards, -Abdullah Ibn Hamad Al-Marri Arab Portal http://www.WeArab.Net/ This how I got it fixed. portupgrade -frR pcre-utf8-7.0 portupgrade -frR php5-pcre-5.2.1_3 Could someone tell me please why did I need to do this to get it fixed? No idea here, but I believe I encountered the same issue under Gallery2 (http://gallery.menalto.com), and a similar solution fixed it. I'm just replying here in case anybody does a search... Cheers, Justin ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Can't upgrade misc/shared-mime-info
Hi all, I'm not sure if this should go to -ports, so I thought I'd start here. As part of a portupgrade, shared-mime-info-0.19 is supposed to be upgraded to -0.20. This is failing w/ a linker error, apparently like this: cc -O -pipe -march=athlon-xp -Wall -Wstrict-prototypes -Wmissing-prototypes -Wwrite-strings -L/usr/local/lib -o update-mime-database update_mime_database- update-mime-database.o -L/usr/local/lib -lxml2 -lglib-2.0 -liconv /usr/local/lib/libxml2.so: undefined reference to `pthread_equal' gmake[1]: *** [update-mime-database] Error 1 gmake[1]: Leaving directory `/usr/ports/misc/shared-mime-info/work/shared-mime-info-0.20' gmake: *** [check-recursive] Error 1 *** Error code 2 Stop in /usr/ports/misc/shared-mime-info. What's bugging me here is that libxml2.so is *not* linked against pthread: # ldd /usr/local/lib/libxml2.so /usr/local/lib/libxml2.so: libz.so.3 = /lib/libz.so.3 (0x282bf000) libiconv.so.3 = /usr/local/lib/libiconv.so.3 (0x282d) libm.so.4 = /lib/libm.so.4 (0x283c) ... although strings shows me that there are nonetheless at least references to pthread_* functions in there: # strings /usr/local/lib/libxml2.so.5 |grep pthread_ pthread_mutex_init pthread_mutex_destroy pthread_mutex_lock pthread_mutex_unlock pthread_cond_init pthread_cond_destroy pthread_self pthread_equal ... I made a point of forcing a recompile of libxml2, making sure that I wasn't defining WITH_THREADS. Still no dice, so what gives? Can anyone tell me: 1) what's going on, and how to fix it? Or 2) what more info could I usefully provide about my system? or 3) that this should definitely go to -ports? :) Thanks! Justin ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Unable to locate Net-SMTP-SSL-1.01 perl module in ports
Hi Gerard! On Mon, 05 Feb 2007, Gerard Seibert wrote: I am looking for the Net-SMTP-SSL perl module in the ports system. So far I have not been able to locate it.. If I cannot locate it, I will have to use CPAN to install it; which is something I would rather not do. Does anyone know if it exists under a different name perhaps? Is this what you were looking for? ttyp1 [EMAIL PROTECTED]:/usr/ports 0 09:30:21 545 # make search name=p5-net-smtp ... Port: p5-Net-SMTP-TLS-0.12 Path: /usr/ports/mail/p5-Net-SMTP-TLS Info: An SMTP client supporting TLS and AUTH Maint: [EMAIL PROTECTED] B-deps: p5-Digest-HMAC-1.01 p5-Digest-SHA1-2.11 p5-IO-Socket-SSL-1.02 p5-MIME-Base64-3.07 p5-Net-SSLeay-1.30_1 perl-5.8.8 R-deps: perl-5.8.8 WWW:http://search.cpan.org/dist/Net-SMTP-TLS/ TLS = SSLv3, IIRC. Justin ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
PHP junk pointer error with imagick.so
Hi All, I recently noticed running a phpinfo() page that the page would not completely render. When I looked in /var/log/httpd-errors.log, I found the following error every time I hit that page: [Fri Jan 20 10:53:08 2006] [notice] child pid 88217 exit signal Abort trap (6) httpd in free(): error: junk pointer, too high to make sense After successively commenting and uncommenting each extension I have for php, I finally found the culprit extension to be imagick.so. I found the commit message for ImageMagick 6.2.5.5 at http://www.freshports.org/graphics/ImageMagick/ suggesting that there were segfaults with earlier versions, and so on a hunch I did a portupgrade -rf ImageMagick. No dice; I still can't load the imagick.so extension to php without running into these junk pointer errors. FYI, here's the (I think) relevant ports I have installed: apache+mod_ssl-1.3.34+2.8.25_2 ImageMagick-6.2.5.5 php4-4.4.2 php4-extensions-1.0 pecl-imagick-0.9.11_3 Has anyone else encountered this issue? Does anyone have any suggestions as to how I might resolve it? Thanks! -- Justin ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: PHP junk pointer error with imagick.so
Hi Uwe! On Fri, 20 Jan 2006, Uwe Laverenz wrote: On Fri, Jan 20, 2006 at 11:11:22AM -0800, Justin Meyer wrote: Has anyone else encountered this issue? Does anyone have any suggestions as to how I might resolve it? I have similar problems with imagick and also with xslt. These two modules make php segfault e.g. when installing pear-ports. The problem seems to exist only on machines with ldap-setup (nss_ldap, pam_ldap). Do you run your machine with nss_ldap? Oh hell no; I'm not into that kind of pain :) Just plain ol' /etc/passwd here, thanks! Solutions? I have mailed the php-maintainer about the problem but got no response. I don't think it would help to additionally make a PR, so for me there are 2 possible ways to solve this: 1) don't use imagick or xslt Well, in truth I don't *need* this module, just thought it'd be useful, but still, this bugs the shit out of me... 2) don't use FreeBSD for PHP-development .. b-b-but I *like* FreeBSD! Nope, not gonna abandon this platform. If I don't hear from anyone else anytime soon, I'll take this to -ports and see what they say. Thanks, Uwe; at least I know I'm not alone :) -- Justin ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
portsnap: corrupt snapshot?
Hi all, I'm doing a portsnap fetch here, and getting the following error: Fetching 130 new ports or files... /usr/sbin/portsnap: cannot open 7a8a3197e659d87ca60f358e3ff663b12d3d33d33b4f607741b2847a4a35e2f1.gz: No such file or directory snapshot is corrupt. .. and indeed, /var/db/portsnap/files/7a8a3197e659d87ca60f358e3ff663b12d3d33d33b4f607741b2847a4a35e2f1.gz just plain doesn't exist. Can anybody tell me what's going on here, or how to fix it? Thanks! -- Justin ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: portsnap: corrupt snapshot?
Hi Colin! On Thu, 05 Jan 2006, Colin Percival wrote: Justin Meyer wrote: I'm doing a portsnap fetch here, and getting the following error: [snip] Can anybody tell me what's going on here, or how to fix it? Some files didn't get uploaded from the machine which performs the portsnap builds to the mirrors due to a network outage (note to self: I need to handle problems like this better!) I've manually copied the missing files into the appropriate places and everything should be working again now. Indeed, portsnap fetch just completed successfully for me. Thank you, Colin, and especially thank you for the fast answer! -- Justin ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Should I have 2 copies of OpenSSL?
Hi Russell! On Fri, 18 Nov 2005, Russell E. Meek wrote: Justin Meyer wrote: What gives? Is the way things should be? Or did I foul something up somewhere along the way through my upgrades? If I did mess something up, what should I do to fix it? Justin, How about trying this, you have the most recent version of openssl installed in base due to the upgrade to 6.0 - release. If you have the OpenSSL port installed why don't you uninstall the port and place the following in your /etc/make.conf file WITH_OPENSSL_BASE=yes This will force all ports you install going foward to use the base install of OpenSSL and not to install OpenSSL as a dependency from ports. You could then make deinstall, make install clean make distclean any port that requires OpenSSL, Ruby for instance. This should make it build with the base install, eliminating the version conflict. That seems to have done the trick, Russell; the script works again! Thank you very much for the suggestions :) -- Justin ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Should I have 2 copies of OpenSSL?
Hi Folks, I've got a 6.0-STABLE box here that I've upgraded from sources serveral times, from all the way back from 5.0 (and maybe from 4.x; I honestly can't remember at this point...) I'm fairly sure I followed directions properly along the way, because I always got everything working again after each upgrade. Except this time, a Ruby script using Ruby's 'http-access2' module started throwing odd OpenSSL exceptions. After poking a bit, I found the following: ttyp3 [EMAIL PROTECTED]:~/code/ruby $ /usr/bin/openssl version OpenSSL 0.9.7e-p1 25 Oct 2004 ttyp3 [EMAIL PROTECTED]:~/code/ruby $ /usr/local/bin/openssl version OpenSSL 0.9.8a 11 Oct 2005 I guess the one in /usr/bin came with the system, and the one in /usr/local/bin came from ports: ttyp3 [EMAIL PROTECTED]:~/code/ruby $ pkg_info|grep openssl openssl-0.9.8a SSL and crypto library What gives? Is the way things should be? Or did I foul something up somewhere along the way through my upgrades? If I did mess something up, what should I do to fix it? Thank you! -- Justin ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
