go to bug id or search bugs for
expect does not build with php-5.3.0RC2
as done usually
libtool: compile: cc -I. -I/home/oden/RPM/BUILD/expect-0.2.5 -DPHP_ATOM_INC -I/home/oden/RPM/BUILD/expect-0.2.5/include -I/home/oden/RPM/BUILD/expect-0.2.5/main -I/home/oden/RPM/BUILD/expect-0.2.5 -I/usr/include/php -I/usr/include/php/main -I/usr/include/php/TSRM -I/usr/include/php/Zend -I/usr/include/php/ext -I/usr/include/php/ext/date/lib -I/usr/include/php -DHAVE_CONFIG_H -O2 -g -pipe -Wformat -Werror=format-security -Wp,-D_FORTIFY_SOURCE=2 -fexceptions -fstack-protector --param=ssp-buffer-size=4 -fstack-protector-all -fomit-frame-pointer -march=i586 -mtune=generic -fasynchronous-unwind-tables -c /home/oden/RPM/BUILD/expect-0.2.5/expect_fopen_wrapper.c -fPIC -DPIC -o .libs/expect_fopen_wrapper.o
/home/oden/RPM/BUILD/expect-0.2.5/expect.c:28: error: 'third_arg_force_ref' undeclared here (not in a function)
Add a Patch
Add a Pull Request
This bug has been fixed in CVS.
In case this was a documentation problem, the fix will show up at the
end of next Sunday (CET) on pecl.php.net.
In case this was a pecl.php.net website problem, the change will show
up on the website in short time.
Thank you for the report, and for helping us make PECL better.
What do you mean by "fixed" exactly?
If you think it's fixed just because you fixed it in cvs you must be mistaking. The term "fixed" to me means fixed in a new public release/version.
Thank you for your bug report. This issue has been fixed
in the latest released version of the package, which you can download at
There are two types of fix:
1. Fixed in CVS (you'll have to wait for the next release)
2. Fixed in release (there's a new package version that
already has the fix)
I'm "fixing" it in release (0.2.6) now (just for you).
"Fixed in CVS" means it is fixed in CVS. Imagine if every
closed bug in the world required a new release... this sounds
like a lot of work.
It's just that it's frustrating that bugs are closed with the resolution "fixed in cvs" with no referance to the actual fix or what have you.
Does this mean you must use the latest cvs snapshot because the last released official version is never supported and is obsolete at any given time?
Ahh, never mind...