Re: newest PHP port upgrade broke php5-mbstring-5.0.1 ?
Really fishy. I can't see anything wrong. Did you cvsup your ports tree with ports-all? If not then I would recommend to do so and then try the upgrade. And do not forget to do a make clean without s before starting to build. If that also fails then try to run portupgrade -a on the updated ports tree and then try to rebuild php. Regards S. On Sat, 28 Aug 2004 21:44:27 -0700, Miles Keaton [EMAIL PROTECTED] wrote: p.s. Sorry I meant to say My portupgrade just took PHP from 5.0 to 5.0.1 - (PHP not FreeBSD) ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED] -- Subhro Sankha Kar School of Information Technology Block AQ-13/1 Sector V ZIP 700091 India ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: newest PHP port upgrade broke php5-mbstring-5.0.1 ?
PS: by build I meant manually cd to the directory and make clean all install without the s. Regards S. On Sun, 29 Aug 2004 14:24:20 +0530, Subhro [EMAIL PROTECTED] wrote: Really fishy. I can't see anything wrong. Did you cvsup your ports tree with ports-all? If not then I would recommend to do so and then try the upgrade. And do not forget to do a make clean without s before starting to build. If that also fails then try to run portupgrade -a on the updated ports tree and then try to rebuild php. Regards S. On Sat, 28 Aug 2004 21:44:27 -0700, Miles Keaton [EMAIL PROTECTED] wrote: p.s. Sorry I meant to say My portupgrade just took PHP from 5.0 to 5.0.1 - (PHP not FreeBSD) ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED] -- Subhro Sankha Kar School of Information Technology Block AQ-13/1 Sector V ZIP 700091 India -- Subhro Sankha Kar School of Information Technology Block AQ-13/1 Sector V ZIP 700091 India ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: newest PHP port upgrade broke php5-mbstring-5.0.1 ?
On Sun, 29 Aug 2004 14:24:20 +0530, Subhro [EMAIL PROTECTED] wrote: Really fishy. I can't see anything wrong. Did you cvsup your ports tree with ports-all? If not then I would recommend to do so and then try the upgrade. And do not forget to do a make clean without s before starting to build. If that also fails then try to run portupgrade -a on the updated ports tree and then try to rebuild php. Yeah that's what started this. I'm using the exact same setup I always do, but the most recent cvsup of all ports, and then portupgrade of my ports-tree is what brought PHP and all of its extensions from PHP 5.0.0 to PHP 5.0.1 Doing so seems to have broken the mbstring regex component. I did, after posting here, go back and rebuild php5-mbstring WITHOUT the regex option and it PHP works without error again -- but without mbstring regex. Since FreeBSD is all I have to test with, I don't know if this is a FreeBSD error or a PHP error. ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
newest PHP port upgrade broke php5-mbstring-5.0.1 ?
My portupgrade just took FreeBSD from 5.0 to 5.0.1 But unfortunately it seemed to break php5-mbstring-5.0.1 At startup and every time I try to run PHP I get this: PHP Warning: PHP Startup: Unable to load dynamic library '/usr/local/lib/php/20040412/mbstring.so' - /usr/local/lib/php/20040412/mbstring.so: Undefined symbol quot;zif_mb_regex_encodingquot; in Unknown on line 0 Anyone heard of this problem or suggest a solution? ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: newest PHP port upgrade broke php5-mbstring-5.0.1 ?
cat /etc/make.conf uname -a Regards S. On Sat, 28 Aug 2004 21:08:44 -0700, Miles Keaton [EMAIL PROTECTED] wrote: My portupgrade just took FreeBSD from 5.0 to 5.0.1 But unfortunately it seemed to break php5-mbstring-5.0.1 At startup and every time I try to run PHP I get this: PHP Warning: PHP Startup: Unable to load dynamic library '/usr/local/lib/php/20040412/mbstring.so' - /usr/local/lib/php/20040412/mbstring.so: Undefined symbol quot;zif_mb_regex_encodingquot; in Unknown on line 0 Anyone heard of this problem or suggest a solution? ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED] -- Subhro Sankha Kar School of Information Technology Block AQ-13/1 Sector V ZIP 700091 India ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: newest PHP port upgrade broke php5-mbstring-5.0.1 ?
bash-2.05b$ uname -a
FreeBSD me.my.com 4.10-STABLE FreeBSD 4.10-STABLE #7: Fri Jul 23
15:03:16 PDT 2004 [EMAIL PROTECTED]:/usr/obj/usr/src/sys/GENERIC
i386
bash-2.05b$ cat /etc/make.conf
# $FreeBSD: src/etc/defaults/make.conf,v 1.97.2.81 2003/07/12 23:22:51
gshapiro Exp $
#
# NOTE: Please would any committer updating this file also update the
# make.conf(5) manual page, if necessary, which is located in
# src/share/man/man5/make.conf.5.
#
# This file, if present, will be read by make (see /usr/share/mk/sys.mk).
# It allows you to override macro definitions to make without changing
# your source tree, or anything the source tree installs.
#
# This file must be in valid Makefile syntax.
#
# You have to find the things you can put here in the Makefiles and
# documentation of the source tree.
#
#
# The CPUTYPE variable controls which processor should be targeted for
# generated code. This controls processor-specific optimizations in
# certain code (currently only OpenSSL) as well as modifying the value
# of CFLAGS to contain the appropriate optimization directive to gcc.
# The automatic setting of CFLAGS may be overridden using the
# NO_CPU_CFLAGS variable below.
# Currently the following CPU types are recognized:
# Intel x86 architecture:
# (AMD CPUs) k7 k6-2 k6 k5
# (Intel CPUs)p4 p3 p2 i686 i586/mmx i586 i486 i386
# Alpha/AXP architecture: ev6 pca56 ev56 ev5 ev45 ev4
#
# If you experience any problems after setting this flag, please unset
# it again before submitting a bug report or attempting to modify code.
# It may be that certain types of software will become unstable after being
# compiled with processor-specific (or higher - see below) optimization flags.
# If in doubt, do not set CPUTYPE or CFLAGS to non-default values.
#
#CPUTYPE=i686
#NO_CPU_CFLAGS= true# Don't add -march=cpu to CFLAGS automatically
#NO_CPU_COPTFLAGS=true # Don't add -march=cpu to COPTFLAGS automatically
#
# CFLAGS controls the compiler settings used when compiling C code.
# Note that optimization settings above -O (-O2, ...) are not recommended
# or supported for compiling the world or the kernel - please revert any
# nonstandard optimization settings to -O before submitting bug reports
# to the developers.
# Note also that at this time the -O2 setting is known to produce BROKEN
# CODE on the Alpha platform.
#
#CFLAGS= -O -pipe
#
# CXXFLAGS controls the compiler settings used when compiling C++ code.
# Note that CXXFLAGS is initially set to the value of CFLAGS. If you wish
# to add to CXXFLAGS value, += must be used rather than =. Using =
# alone will remove the often needed contents of CFLAGS from CXXFLAGS.
#
#CXXFLAGS+= -fmemoize-lookups -fsave-memoized
#
# BDECFLAGS are a set of gcc warning settings that Bruce Evans has suggested
# for use in developing FreeBSD and testing changes. They can be used by
# putting CFLAGS+=${BDECFLAGS} in /etc/make.conf. -Wconversion is not
# included here due to compiler bugs, e.g., mkdir()'s mode_t argument.
#
BDECFLAGS= -W -Wall -ansi -pedantic -Wbad-function-cast -Wcast-align \
-Wcast-qual -Wchar-subscripts -Winline \
-Wmissing-prototypes -Wnested-externs -Wpointer-arith \
-Wredundant-decls -Wshadow -Wstrict-prototypes -Wwrite-strings
#
# WARNS_WERROR causes -Werror to be added when WARNS is in effect.
#
#WARNS_WERROR= yes
#
# To compile just the kernel with special optimizations, you should use
# this instead of CFLAGS (which is not applicable to kernel builds anyway).
# There is very little to gain by using higher optimization levels, and doing
# so can cause problems.
#
#COPTFLAGS= -O -pipe
#
# Compare before install
#INSTALL=install -C
#
# To enable installing suidperl with the setuid bit turned on
#ENABLE_SUIDPERL= true
#
# To build ppp with normal permissions
#PPP_NOSUID=true
#
# To enable installing ssh(1) with the setuid bit turned on
#ENABLE_SUID_SSH= true
#
# To avoid building various parts of the base system:
#NO_CVS=true# do not build CVS
#NO_BIND= true# do not build BIND
#NO_FORTRAN=true# do not build g77 and related libraries
#NO_I4B=true# do not build isdn4bsd package
#NO_IPFILTER= true# do not build IP Filter package
#NO_LPR=true# do not build lpr and related programs
#NO_MAILWRAPPER=true# do not build the mailwrapper(8) MTA selector
#NO_MODULES=true# do not build modules with the kernel
#NO_OBJC= true# do not build Objective C support
#NO_OPENSSH=true# do not build OpenSSH
#NO_OPENSSL=true# do not build OpenSSL (implies NO_OPENSSH)
#NO_SENDMAIL= true# do not build sendmail and related programs
#NO_SHAREDOCS= true# do not build the 4.4BSD legacy docs
#NO_TCSH= true# do not build and install /bin/csh (which is tcsh)
#NO_X= true# do not compile in XWindows support (e.g. doscmd)
#NOCRYPT= true# do not build any crypto code
Re: newest PHP port upgrade broke php5-mbstring-5.0.1 ?
p.s. Sorry I meant to say My portupgrade just took PHP from 5.0 to 5.0.1 - (PHP not FreeBSD) ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
