Date: Mon, 8 May 2006 19:05:08 +0200 (CEST) From: "Julien Gabel" <jpeg@thilelli.net> To: "Zimmerman, Eric" <zimmerman.eric@con-way.com> Cc: Dave <dmehler26@woh.rr.com>, freebsd-questions@freebsd.org Subject: Re: php4 port upgrade Message-ID: <60956.192.168.1.101.1147107908.squirrel@webmail.thilelli.net> In-Reply-To: <20060508153209.GA54676@bento.thilelli.net> References: <12AAD6CC50A25841834F43955F39B66E04390A59@qgaes001.conway.prod.con-way.com> <20060508153209.GA54676@bento.thilelli.net>
next in thread | previous in thread | raw e-mail | index | archive | help
>>> Is there any known issues or things to watch out for when doing the >>> latest php4 upgrade? The notes in the UPDATING file indicated a change >>> in the status of the .cli binary. If one has mod_php4 and the >>> php4-extensions already installed is the upgrade a smooth one? >> Mine seemed to go fine via portmanager after doing a make config in the >> php4 directory as UPDATING indicates to do. No issues so far that I have >> seen > Using portupgrade, i had to recompile all php4-* found in /var/db/pkg and > the dependancies. All went well, except for the SSL support i use throuth > squirrelmail. I use different knobs in the past in order to be able to > access imaps via squirrelmail, the last one was "WITH_OPENSSL_BASE". But > according to the current ports/Mk/bsd.openssl.mk makefile, it seems > deprecated in favor of "WITH_OPENSSL_BASE=yes". So i tried: > # portupgrade -rRf -m 'WITH_OPENSSL_BASE=yes' squirrelmail > instead of: > # portupgrade -rRf -m '-DWITH_OPENSSL_BASE' squirrelmail > without much success for the moment... ... but switching-on the "Build static OpenSSL extension" knob using `make config' in the ports/lang/php4 directory do the trick. So, the upgrade went relatively well. -- Julien Gabel.
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?60956.192.168.1.101.1147107908.squirrel>